Mobile compatible, mobile optimized, responsive web design and adaptive web design are all terms that have been used interchangeably, and often incorrectly, to describe websites displayed, and used, on mobile devices.
If you're a business or organization interested in making your website look and behave just as spiffy on a mini-tablet as on your widescreen monitor, there are a few routes you could take to this destination.
The two we discuss here are: (1) adaptive web design and (2) responsive web design.

Yahoo's homepage in Australia is a great example of adaptive web design. The site detects what the user is using to access the site and switches to the "em-dot" m.yahoo.com.au mobile-optimized version of the site.
With adaptive web design a separate, mobile-optimized, version of your website is served up once access by a mobile device (phone, tablet or mini-tablet) is detected.

The website App, designed partially by a Web company called Neem Tree, is an example of responsive web design. Neem Tree applied responsive web design techniques to ensure the site responsively adjusted to a layout best suited to whichever device the user was viewing the site on: desk/laptop, tablet in both landscape and portrait modes and also smartphone in both landscape and portrait modes. For example, in the image above observe how the layout has compressed the full-view's horizontal navigation menu into a drop-down for the mobile-view.
With responsive web design, a separate/dedicated mobile or tablet version of the site isn't necessary. Instead, the site uses HTML5's new features to present multiple layouts of the same site, depending on the width of the viewing device.
When deciding whether to take a an adaptive or responsive (or hybrid adaptive-hybrid) web design approach:
While there is some debate to whether responsive web design is suitable for every business case, there is widespread agreement that the trend in 2013 is in responsive web design's favor. Increasingly, web design companies and site owners see responsive web design as the preferred approach even when mobile apps are also on the decision table.
Editor's Note: This article first appeared on the website for Neem Tree and has been used and slightly modified here with permission. Neem Tree is a Web development and Drupal consulting company.
CMS Report's mission is to bring CMS enthusiasts like yourself together while informing readers of the latest happenings in the world of content management systems. Through the CMS Report avatar we provide CMS related news via aggregated news feeds as well as submitted links to CMS related articles suggested by our readers.
Add A Comment
Thank you for your comment. It will be posted to the site shortly.
Sorry! There was a problem with your comment submission. Please try again.
Comment
Allowed HTML: <b>, <i>, <u>
Post Using Facebook
Click the button below to continue
Post Using Twitter
Click the button below to continue
Comments
Thank you for your comment. It will be posted to the site shortly.
Sorry! There was a problem with your comment submission. Please try again.