FANDOM


File:Boston Globe responsive website.jpg

Responsive web design (often abbreviated to RWD) is an approach to web design in which a site is crafted to provide an optimal viewing experience—easy reading and navigation with a minimum of resizing, panning, and scrolling—across a wide range of devices (from desktop computer monitors to mobile phones).[1][2][3]

Elements of responsive web design (RWD)

A site designed with RWD[1][4] uses CSS3 media queries,[3][5][6] an extension of the @media rule,[7] to adapt the layout to the viewing environment—along with fluid proportion-based grids[8] and flexible images:.[9][10][11][12]

  • Media queries allow the page to use different CSS style rules based on characteristics of the device the site is being displayed on, most commonly the width of the browser.
  • The fluid grid concept calls for page element sizing to be in relative units like percentages or EMs, rather than absolute units like pixels or points.[8]
  • Flexible images are also sized in relative units (up to 100%), so as to prevent them from displaying outside their containing element.[9]

Testing Tool To Test Responsive web design

RUIT(Responsive UI Testing Tool) is designed to test responsive websites on different device resolutions such as iphone,android,ipad and kindle.

Related concepts

Mobile first, unobtrusive JavaScript, and progressive enhancement

"Mobile First" and "Unobtrusive JavaScript"/"Progressive Enhancement" (strategies for when a new site design is being considered) are related concepts that predated RWD: browsers of basic mobile phones do not understand Javascript or media queries, so the recommended practice is to create a basic web site then enhance it for smart phones and PCs—rather than try "graceful degradation" to make a complex, image-heavy site work on the most basic mobile phones.[13][14][15][16]

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[14][17] 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.

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 with older browsers: some may report that a feature is available, when it is either missing or so poorly implemented that it is effectively nonfunctional.[18][19]

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.[20][21][22] 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.[23][24][25] Server-side "dynamic CSS" implementation of stylesheet languages like Sass can be part of such an approach.

One problem for RWD is that banner advertisements and videos are not fluid.[26] 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,[27] or AJAX can be used to display different ad variants on a page.[21][28][17]

History

Ethan Marcotte coined the term Responsive Web Design (RWD) in his article in A List Apart.[1] He describes the theory and practice of responsive web design in his brief 2011 book on the subject.[29] Responsive Design was listed as #2 in Top Web Design Trends for 2012 by .net magazine[30] (Progressive Enhancement was #1). They also listed 20 of Ethan Marcotte's favorite responsive sites.[2]

External links

References

  1. 1.0 1.1 1.2 Marcotte, Ethan (May 25, 2010). Responsive Web Design. A List Apart.
  2. 2.0 2.1 Ethan Marcotte's 20 favourite responsive sites. .net magazine (October 11, 2011).
  3. 3.0 3.1 Gillenwater, Zoe Mickley (Dec. 15, 2010). Examples of flexible layouts with CSS3 media queries 320.
  4. Pettit, Zoe Nick (Aug. 8, 2012). Beginner’s Guide to Responsive Web Design. TeamTreehouse.com blog.
  5. Gillenwater, Zoe Mickley (Oct. 21, 2011). Crafting quality media queries.
  6. Responsive design—harnessing the power of media queries. Google Webmaster Central (Apr. 30, 2012).
  7. W3C @media rule
  8. 8.0 8.1 Marcotte, Ethan (March 3, 2009). Fluid Grids. A List Apart.
  9. 9.0 9.1 Marcotte, Ethan (June 7, 2011). Fluid images. A List Apart.
  10. Adaptive Images.
  11. Hannemann, Anselm (Sept. 7, 2012). The road to responsive images. net Magazine.
  12. Jacobs, Denise (August 23, 2011). 21 top tools for responsive web design. .net Magazine.
  13. Wroblewski, Luke (November 3, 2009). Mobile First.
  14. 14.0 14.1 Firtman, Maximiliano (July 30, 2010). Programming the Mobile Web. pp. 512. ISBN 978-0-596-80778-8. http://www.mobilexweb.com/book. 
  15. Graceful degradation versus progressive enhancement (February 3, 2009).
  16. Designing with Progressive Enhancement. March 1, 2010. pp. 456. ISBN 978-0-321-65888-3. http://filamentgroup.com/dwpe/. 
  17. 17.0 17.1 Server-Side Device Detection: History, Benefits And How-To. Smashing magazine (September 24, 2012).
  18. BlackBerry Torch: The HTML5 Developer Scorecard | Blog. Sencha (2010-08-18). Retrieved on 2012-09-11.
  19. Motorola Xoom: The HTML5 Developer Scorecard | Blog. Sencha (2011-02-24). Retrieved on 2012-09-11.
  20. Wroblewski, Luke (May 17, 2011). Mobilism: jQuery Mobile.
  21. 21.0 21.1 Wroblewski, Luke (February 6, 2012). Rolling Up Our Responsive Sleeves.
  22. Wroblewski, Luke (March 14, 2012). Multi-Device Layout Patterns.
  23. Wroblewski, Luke (February 29, 2012). Responsive Design ... or RESS.
  24. Wroblewski, Luke (September 12, 2011). RESS: Responsive Design + Server Side Components.
  25. Andersen, Anders (May 9, 2012). Getting Started with RESS.
  26. The state of responsive advertising: the publishers' perspective. .net Magazine (Apr. 30, 2012).
  27. Google AdWords Targeting (Device Platform Targeting)
  28. JavaScript and Responsive Web Design Google Developers
  29. Marcotte, Ethan (2011). Responsive Web Design. pp. 143. ISBN 978-0-9844425-7-7. http://www.abookapart.com/products/responsive-web-design. 
  30. 15 top web design and development trends for 2012. .net magazine (January 9, 2012).
ca:Disseny web adaptatiu

cs:Responzivní web design de:Responsive Design es:Diseño web adaptativo fr:Responsive Web Design it:Responsive Web Design ru:Адаптивный веб-дизайн sv:Responsive web design zh:响应式网页设计

This article uses material from the Wikipedia article Responsive web design, that was deleted or is being discussed for deletion, which is released under the Creative Commons Attribution-ShareAlike 3.0 Unported License.
Author(s): Hell in a Bucket Search for "Responsive web design" on Google
View Wikipedia's deletion log of "Responsive web design"
Wikipedia-logo-v2

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.