This article needs to be updated.(September 2018)
Adaptive web design (AWD) promotes the creation of multiple versions of a web page to better fit the user's device, as opposed to a single static page which loads (and looks) the same on all devices or a single page which reorders and resizes content responsively based on the device/screen size/browser of the user.
This most often describes the use of a mobile and a desktop version of a page (or in most cases, the entire website), either of which is retrieved based on the user-agent defined in the HTTP GET request, which is known as dynamic serving. Adaptive web design was one of the first strategies for optimizing a site for mobile readability, the most common practice involved using a completely separate website for mobile and desktop, with mobile devices often redirected to the mobile version of the site served on a subdomain (often the third level subdomain, denoted "m"; e.g. http://m.website.com/; and/or URL parameters like
&app=m&persist_app=1 used on YouTube). Today the use of two separate static sites for mobile and desktop viewing is being largely phased out, with Server-side scripting instead utilized to serve dynamically generated pages or to dynamically decide which version of a static page to serve, although the use of independent sites for mobile and desktop can still be frequently observed. While many websites employ either responsive or adaptive web design techniques, the two are not mutually exclusive, and best practices for the most universally readable designed content employ a combination of the two techniques to support a complete spectrum of hardware and software.
The existence of separate front ends allows clients who experience technical issues with either to fall back to another, with the chance that the issue does not occur.
Adaptive web design is a process of server-side detection that chooses a design layout and size to display. All types of web design layouts can be used, including responsive layout. The adaptive design will serve different versions of the page to different devices based on common screen sizes and resolutions. The term was first coined by Aaron Gustafson in his 2011 book Adaptive Web Design: Crafting Rich Experiences with Progressive Enhancement.
Terminology of techniques
Technology advances leading to necessity
This section needs additional citations for verification. (February 2024)
History, adaptation and evolution
Adaptive web design works to detect the screen size during the HTTP GET request, prior to the page being served and load the appropriately designed page specific to the user-agent. With adaptive standard layout, "generally you would design an adaptive site for six common screen widths: 320, 480, 760, 960, 1200, and 1600". This was not only common practice for mobile optimization, but the transition period between 4:3 low resolution CRT monitors and high resolution 16:9 LCD monitors. Standard adaptive web design was necessary to create fluid layouts for the various monitors available.
In the very early days of smartphones, screen dimensions varied greatly and mobile web browsers lacked the advanced functionality and plugins used to create rich environments in desktop browsers. Additionally, mobile internet use was expensive and very slow, so it was necessary to design "stripped-down" mobile pages, with fewer or lower quality images and sharp text-wrapping for easy readability. The next major change to adaptive standard web design came with the rise of the iPhone and widespread 3G availability, with 3G dramatically increasing connection speeds and available bandwidth. It became common for sites to have two versions: a mobile layout optimized for iPhone (usually with the subdomain prefix "m") and a desktop layout. The mobile versions were still usually "scaled-down" with lower quality images and sometimes lacked content such as videos in order to decrease loading time. Designs were also influenced by the spread of touchscreen devices, with websites using larger links and buttons that make navigating using a finger as a pointer easier. Later, the widespread implementation of 4G LTE's fast mobile broadband meant it was no longer necessary to downgrade mobile media quality or trim content to deal with slow connection speeds. As Google's Android OS rose to popularity and introduced more variation in the smartphone market, the multi-page paradigm of standard dynamic web design became less common, though it still sees some use to completely separate touchscreen content design from desktop design. When integrating with material design or device specific layout and color schemes, some developers find it simpler to create three page templates (Android, iPhone/iOS, desktop), changing the icons and colors between each, while using media queries to determine layout. The practice results in much simpler page design and code, but updating requires editing all three templates.
Responsive web design vs. adaptive web design
There is no consensus on naming, and both adaptive and responsive are used to refer to the same behavior, but what is commonly called responsive design uses fewer page layouts than standard adaptive design, typically only one. Adaptive design is considered less future-proof and less efficient than responsive design because the screen sizes of common devices are constantly changing and highly variable. A hybrid adaptive/responsive design model involves multiple versions of pages with responsive layouts.
Standard adaptive layouts can also use viewport responsive scaling of the page (as in responsive web design), but the approach of creating different layouts for different devices or resolutions is now rare and typically seen where the site wishes to target users of non-smart internet-capable mobile devices and obsolete smartphones which can't use the technologies new responsive designs require.
There are variations on these concepts that blur the lines between adaptive and responsive web design, like Django's "views" and some aspected of AJAX, which serve different versions of pages, including for the purpose of fluidity on different devices, however pages are generated dynamically, not statically.
- AJAX – Group of interrelated Web development techniques
- Backwards compatibility – Technological ability to interact with older technologies
- Content negotiation – Serving multiple documents at the same URI
- CSS – Style sheet language
- Media Queries – CSS3 module allowing content rendering to adapt to conditions such as screen resolution
- Mobile first – Approach to web design for making web pages render well on a variety of devices
- Polyfill (programming) – Code to implement features in web browsers that do not support them
- Responsive Web Design – Approach to web design for making web pages render well on a variety of devices
- User interfaces – Means by which a user interacts with and controls a machine
- Viewport – Polygon viewing region in computer graphics
- "Legacy Twitter Shutdown Means You Can't Tweet From The 3DS Anymore". ScreenRant. 2020-11-28.
- Gustafson, Aaron. Adaptive Web Design: Crafting Rich Experiences with Progressive Enhancement. Easy Readers, LLC; 1st edition, 2011.
- "Graceful degradation versus progressive enhancement". February 3, 2009. Archived from the original on 2014-11-13. Retrieved 2016-12-21.
- Parker, Todd; Wachs, Maggie Costello; Jehl, Scott (February 2010). Designing with Progressive Enhancement. p. 456. ISBN 978-0-321-65888-3. Retrieved March 1, 2010.
- "Desktop vs Mobile Market Share Worldwide". StatCounter Global Stats. Retrieved 19 February 2024.
- Adiseshiah, Emily Grace (Mar 1, 2016). "Choosing a web design: Responsive Vs Adaptive".
- VenturePact, VenturePact. "Designing for 10000 screens 4 layout tips for responsive web design".
- Firtman, Maximiliano (July 30, 2010). Programming the Mobile Web. pp. 512. ISBN 978-0-596-80778-8.