If there was a word I’d use to describe the response to Responsive Web Design it’s ‘hysteria’.
I see meaningless polls asking “Will your next project be responsive” and tweets boasting that “my client understands the value of a responsive design.”
Andy Clark went one step further recently tweeted that you weren’t a real web designer if you weren’t building responsive sites. Or something to that effect; I think he deleted the tweet.
The brilliant Ethan Marcotte has a lot to answer for.
(Illustration by Kevin Cornell taken from http://www.alistapart.com/articles/responsive-web-design/)
But why the hysteria?
Responsive web design is one possible solution – there are many more.
You may choose a fully responsive site or you might choose a static site. At the moment I’m developing a responsive site down to tablet, whilst a colleague builds a mobile site with a separate codebase. Why? Because it makes perfect sense from a business perspective and a coding perspective.
It’s impossible for anyone to make a judgement about how you should build a site unless they know all the facts about your business and your codebase (particularly a codebase that has evolved over many years).
I was beginning to think I was the only person who thought like this, but a couple of high profile people have made a similar point.
At a recent event Paul Irish was asked, “You currently have two boilerplates, mobile and the desktop. Should we build mobile first or desktop first?”
Paul replied,
Mobile boilerplate is specifically for mobile web apps. We do have a bunch of responsive stuff, responsive CSS, in the HTML5 Boilerplate that allows you to scale things – so you can do mobile first, you can do desktop first.
I think there’s a continuum: You have blogs, and you have web apps and most sites aren’t either of those two things; you have to figure out where you are on that [continuum]. Blogs can be responsive. Web apps? Well you’re probably going to have a different web app for desktop Chrome versus mobile Safari. And so you have to figure out where you are. In many cases you can make it responsive and use the same codebase, but in some cases you have to split it and have two different code bases. Right now it’s a hard question to answer.
You might have also noticed an interesting footnote about responsive design in Bootstrap 2, which was recently released by Twitter:
Truth be told, not everything needs to be responsive. Instead of encouraging developers to remove [media queries], we figure it best to enable it.
If your business will benefit from a responsive design, I think it’s an excellent solution. If, like our business, you need to provide a separate mobile codebase then that’s fine too.
Use the right tools for the right job. We never assume a one design fits all policy, so why are we now doing so for development?
Go make awesome things :)












