Responsive web design

Content is like water, a saying that illustrates the principles of RWD.

Responsive web design (RWD) is an approach to web design aimed at allowing desktop webpages to be viewed in response to the size of the screen or web browser one is viewing with. [1][2][3]

A site designed with RWD[1][4] adapts the layout to the viewing environment by using fluid, proportion-based grids,[5][6] flexible images,[7][8][9] and CSS3 media queries,[3][10][11] an extension of the @media rule, in the following ways:[12]

Responsive web design has become more important as the amount of mobile traffic now accounts for more than half of total internet traffic.[13] Therefore, Google announced Mobilegeddon (April 21, 2015) and started to boost the ratings of sites that are mobile friendly if the search was made from a mobile device.[14] Responsive web design is an example of user interface plasticity.[15]

Related concepts

Mobile first, unobtrusive JavaScript, and progressive enhancement

"Mobile first", unobtrusive JavaScript, and progressive enhancement are related concepts that predate RWD.[16] Browsers of basic mobile phones do not understand JavaScript or media queries, so a recommended practice is to create a basic web site and enhance it for smart phones and PCs, rather than rely on graceful degradation to make a complex, image-heavy site work on mobile phones.[17][18][19][20]

Progressive enhancement based on browser, device, or feature detection

Where a web site must support basic mobile devices that lack JavaScript, browser ("user agent") detection (also called "browser sniffing") and mobile device detection[18][21] are two ways of deducing if certain HTML and CSS features are supported (as a basis for progressive enhancement)—however, these methods are not completely reliable unless used in conjunction with a device capabilities database.

For more capable mobile phones and PCs, JavaScript frameworks like Modernizr, jQuery, and jQuery Mobile that can directly test browser support for HTML/CSS features (or identify the device or user agent) are popular. Polyfills can be used to add support for features—e.g. to support media queries (required for RWD), and enhance HTML5 support, on Internet Explorer. Feature detection also might not be completely reliable; some may report that a feature is available, when it is either missing or so poorly implemented that it is effectively nonfunctional.[22][23]

Challenges, and other approaches

Luke Wroblewski has summarized some of the RWD and mobile design challenges, and created a catalog of multi-device layout patterns.[24][25][26] He suggests that, compared with a simple RWD approach, device experience or RESS (responsive web design with server-side components) approaches can provide a user experience that is better optimized for mobile devices.[27][28][29] Server-side "dynamic CSS" implementation of stylesheet languages like Sass or Incentivated's MML can be part of such an approach by accessing a server based API which handles the device (typically mobile handset) differences in conjunction with a device capabilities database in order to improve usability.[30] RESS is more expensive to develop, requiring more than just client-side logic, and so tends to be reserved for organizations with larger budgets. Google recommends responsive design for smartphone websites over other approaches.[31]

Although many publishers are starting to implement responsive designs, one ongoing challenge for RWD is that some banner advertisements and videos are not fluid.[32] However, search advertising and (banner) display advertising support specific device platform targeting and different advertisement size formats for desktop, smartphone, and basic mobile devices. Different landing page URLs can be used for different platforms,[33] or Ajax can be used to display different advertisement variants on a page.[21][25][34] CSS tables permit hybrid fixed+fluid layouts.[35]

There are now many ways of validating and testing RWD designs,[36] ranging from mobile site validators and mobile emulators[37] to simultaneous testing tools like Adobe Edge Inspect.[38] The Chrome, Firefox and Safari browsers and the Chrome console offer responsive design viewport resizing tools, as do third parties.[39][40]

History

The first site to feature a layout that adapts to browser viewport width was Audi.com launched in late 2001,[41] created by a team at razorfish consisting of Jürgen Spangl and Jim Kalbach (information architecture), Ken Olling (design), and Jan Hoffmann (interface development). Limited browser capabilities meant that for Internet Explorer, the layout could adapt dynamically in the browser whereas for Netscape, the page had to be reloaded from the server when resized.

Cameron Adams created a demonstration in 2004 that is still online.[42] By 2008, a number of related terms such as "flexible", "liquid",[43] "fluid", and "elastic" were being used to describe layouts. CSS3 media queries were almost ready for prime time in late 2008/early 2009.[44] Ethan Marcotte coined the term responsive web design[45] (RWD)—and defined it to mean fluid grid/ flexible images/ media queries—in a May 2010 article in A List Apart.[1] He described the theory and practice of responsive web design in his brief 2011 book titled Responsive Web Design. Responsive design was listed as #2 in Top Web Design Trends for 2012 by .net magazine[46] after progressive enhancement at #1.

Mashable called 2013 the Year of Responsive Web Design.[47] Many other sources have recommended responsive design as a cost-effective alternative to mobile applications.

See also

References

  1. 1 2 3 Marcotte, Ethan (May 25, 2010). "Responsive Web design". A List Apart.
  2. ↑ "Ethan Marcotte's 20 favourite responsive sites". .net magazine. October 11, 2011.
  3. 1 2 Gillenwater, Zoe Mickley (December 15, 2010). "Examples of flexible layouts with CSS3 media queries". Stunning CSS3. p. 320. ISBN 978-0-321-722133.
  4. ↑ Pettit, Nick (August 8, 2012). "Beginner's Guide to Responsive Web Design". TeamTreehouse.com blog.
  5. ↑ "Core concepts of Responsive Web design". September 8, 2014.
  6. 1 2 Marcotte, Ethan (March 3, 2009). "Fluid Grids". A List Apart.
  7. 1 2 Marcotte, Ethan (June 7, 2011). "Fluid images". A List Apart.
  8. ↑ Hannemann, Anselm (September 7, 2012). "The road to responsive images". net Magazine.
  9. ↑ Jacobs, Denise (April 24, 2012). "50 fantastic tools for responsive web design". .net Magazine.
  10. ↑ Gillenwater, Zoe Mickley (October 21, 2011). "Crafting quality media queries".
  11. ↑ "Responsive design—harnessing the power of media queries". Google Webmaster Central. April 30, 2012.
  12. ↑ W3C @media rule
  13. ↑ "Cisco Visual Networking Index: Global Mobile Data Traffic Forecast Update 2014–2019 White Paper". Cisco. January 30, 2015. Retrieved August 4, 2015.
  14. ↑ "Official Google Webmaster Central Blog: Rolling out the mobile-friendly update". Official Google Webmaster Central Blog. Retrieved August 4, 2015.
  15. ↑ Thevenin, D.; Coutaz, J. (2002). "Plasticity of User Interfaces: Framework and Research Agenda". Proc. Interact'99, A. Sasse & C. Johnson Eds, IFIP IOS Press. Edinburgh. pp. 110–117.
  16. ↑ "What is Responsive Web Design". July 23, 2012.
  17. ↑ Wroblewski, Luke (November 3, 2009). "Mobile First".
  18. 1 2 Firtman, Maximiliano (July 30, 2010). Programming the Mobile Web. p. 512. ISBN 978-0-596-80778-8.
  19. ↑ "Graceful degradation versus progressive enhancement". February 3, 2009.
  20. ↑ Designing with Progressive Enhancement. February 2010. p. 456. ISBN 978-0-321-65888-3. Retrieved March 1, 2010.
  21. 1 2 "Server-Side Device Detection: History, Benefits And How-To". Smashing magazine. September 24, 2012.
  22. ↑ "BlackBerry Torch: The HTML5 Developer Scorecard | Blog". Sencha. August 18, 2010. Retrieved September 11, 2012.
  23. ↑ "Motorola Xoom: The HTML5 Developer Scorecard | Blog". Sencha. February 24, 2011. Retrieved September 11, 2012.
  24. ↑ Wroblewski, Luke (May 17, 2011). "Mobilism: jQuery Mobile".
  25. 1 2 Wroblewski, Luke (February 6, 2012). "Rolling Up Our Responsive Sleeves".
  26. ↑ Wroblewski, Luke (March 14, 2012). "Multi-Device Layout Patterns".
  27. ↑ Wroblewski, Luke (February 29, 2012). "Responsive Design ... or RESS".
  28. ↑ Wroblewski, Luke (September 12, 2011). "RESS: Responsive Design + Server Side Components".
  29. ↑ Andersen, Anders (May 9, 2012). "Getting Started with RESS".
  30. ↑ "Responsive but not completely mobile optimised | Blog". Incentivated.
  31. ↑ "Building Smartphone-Optimized Websites". Google.
  32. ↑ Snyder, Matthew; Koren, Etai (April 30, 2012). "The state of responsive advertising: the publishers' perspective". .net Magazine.
  33. ↑ "Google Partners Help". google.com. Retrieved May 21, 2015.
  34. ↑ JavaScript and Responsive Web Design Google Developers
  35. ↑ "The Role of Table Layouts in Responsive Web Design". Web Design Tuts+. Retrieved May 21, 2015.
  36. ↑ Young, James (August 13, 2012). "Top responsive web design problems... testing". .net Magazine.
  37. ↑ "Best mobile emulators and RWD testing tools". The Mobile Web Design Blog. November 26, 2011.
  38. ↑ Rinaldi, Brian (September 26, 2012). "Browser testing... with Adobe Edge Inspect".
  39. ↑ "Responsive Design View". Mozilla Developer Network. Retrieved May 21, 2015.
  40. ↑ Malte Wassermann. "Responsive design testing tool – Viewport Resizer – Emulate various screen resolutions - Best developer device testing toolbar". maltewassermann.com. Retrieved May 21, 2015.
  41. ↑ Kalbach, Jim (July 22, 2012). "The First Responsive Design Website: Audi (circa 2002)."
  42. ↑ Adams, Cameron (September 21, 2004). "Resolution dependent layout: Varying layout according to browser width". The Man in Blue.
  43. ↑ "G146: Using liquid layout". w3.org. Retrieved May 21, 2015.
  44. ↑ "Media Queries". w3.org. Retrieved May 21, 2015.
  45. ↑ "OutSeller Group - Organize, Optimize, Maximize". outseller.net. Retrieved May 21, 2015.
  46. ↑ "15 top web design and development trends for 2012". .net magazine. January 9, 2012.
  47. ↑ Cashmore, Pete (December 11, 2012). "Why 2013 Is the Year of Responsive Web Design".
This article is issued from Wikipedia - version of the 12/1/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.