Why Responsive Design is a Waste of Time
Join the DZone community and get the full member experience.Join For Free
(update: my view is starting to change from when i first wrote this article. thanks to numerous people who have pointed out many things i overlooked and have helped me to understand what responsive design really is and what goals it is trying to achieve, i am getting a better understanding of why it may indeed not be a waste of time. there are still some valid points that i brought up in this article, but i don’t stand by my original blanket statement that it is a waste of time. it especially seems like responsive design may be worth the “trouble” for ecommerce sites where you are more much likely to make the sale if someone can easily purchase and browse your products from a mobile device. thanks everyone who has been giving me great advice and resources for better understanding responsive design and for mostly doing it in a “nice” way.)
responsive design seems like a good idea.
at first glance, it makes sense. why wouldn’t you want your same website to scale down to a mobile device and display differently?
for example, there are many wordpress themes now that offer responsive design baked right in. if you are using one of those themes, you might as well take advantage of the hard work someone else has put into making the design responsive.
but, if you are creating a new website or you are considering converting your existing website to a responsive design, i’d suggest you think twice before making the plunge.
the extra work of responsive design
the biggest problem with responsive design is the extra work involved. sure, there are frameworks and tools to make responsive design easier, but no matter how good those frameworks and tools get, to make a site adapt from the desktop to a mobile device, it is still going to require significant work.
if you have a really simple site with just a few pages or pages that pretty much all use the same layout, but just differ in content (like a blog for example,) then the work might not be that much, so go ahead, make it responsive.
but, if you have a website of any considerable size, you’ll probably find that responsive design is going to add a non-trivial amount of extra work to your project.
it actually turns out the adding responsive design to a web site can add more work than creating a separate desktop and mobile site, because you are creating a user interface that morphs or adapts to the mobile form factor–which, by the way, is ever-changing.
the problem with one-size-fits-all
consider this. which is more difficult to create: a car that turns into a motorcycle, or a car and a motorcycle?
here is another one. which is more difficult to create: a multi-function printer, or a printer and a scanner?
when you try to make a product that can do multiple things, the complexity of creating that product increases exponentially. it is almost always easier to create two separate products that do two different functions or have different form factors, than it is to create an all-in-one product that is able to do many things.
besides the increased difficulty, trying to create products that do more than one thing usually results in them not doing either function that great.
i’m not saying you can’t design a great responsive website that serves desktop clients and mobile clients wonderfully and makes their eyes light up with joy every time they see your beautiful site. i’m just saying you won’t.
i’d also rather not be handcuffed to my original design because changing anything will incur the cost of making changes to the reactive layout as well, that scales down to mobile.
the reuse fallacy
what are you really trying to do by creating a reactive design, instead of just creating a desktop version and mobile version of the site? reuse some html and css?
when you think about it, it doesn’t make much sense. i’m all for code reuse, but responsive design is like putting ifdefs all over your code base. are you really saving much time and effort by reusing your front end code for both platforms?
it seems to me, that if you have to have your site display differently on a mobile device you are better off just forgetting about trying to reuse the html markup and css, and instead focus on reusing the backend code for both the mobile and desktop versions of your site; that is where you’ll actually get the biggest bang for your buck.
again, i don’t know about you, but i’d much rather maintain two front end codebases that are simple than one monstrous complicated front end codebase .
it is good enough already?
most desktop websites actually look fine on a mobile device without any reactive design. to me it makes much more sense, in most cases, to focus on just creating a desktop design that looks good on mobile or even a mobile design the looks good on the desktop as well.
sure, responsive design is pretty cool, but do you really need it?
it is the browser’s responsibility anyway
aside from the practical reasons i’ve talked about so far, there is another major reason why responsive design might just be a waste of time anyway: this should all be the browser’s responsibility, not the web developer’s.
this is even already starting to take place. consider the special input types in html5, like the number input type. on a mobile device it brings up the numerical keyboard in mobile browsers.
i predict as more and more websites are viewed from mobile devices, the types of things that web designers are doing to make desktop sites responsive right now will be incorporated directly into the html markup and the browser itself. so, creating a responsive design manually might end up being a big waste of time.
i’ll leave you with one final point, then i’ll get off my responsive design soapbox.
we are in a time of constant flux right now
things are changing rapidly. mobile devices are getting bigger screens and higher resolutions and becoming much more powerful. while two years ago it was a pain to visit a desktop site from a mobile browser, it is much less painful now. with my new galaxy s4 , i hardly feel the difference at all, and i even find myself specifically requesting the desktop version of a mobile site from time to time.
the trend says that mobile browsing will eventually take over desktop browsing as the main source of visitors to websites. if this becomes reality—which i see no reason to doubt—responsive design won’t make much sense at all. in that case, it will make much more sense to build websites optimized for mobile and not really worry so much about desktop.
if you are going to do responsive design, at least get a good book on the subject. there are many subpar books floating around, because responsive design is so hot right now.
what do you think? am i off my rocker? if you have a convincing argument as to why responsive design is worth the effort or why it isn’t as much extra effort as i have painted it to be, i’d love to hear it. let me know in the comments below.
Published at DZone with permission of John Sonmez. See the original article here.
Opinions expressed by DZone contributors are their own.