News for hackers. Stuff that matters.
Re:Why Responsive Design Is Not Worth It by cleverjake on Tuesday September 25, 2012 @10:00AM (#4570336)
Wrong.

wrong. wrong. wrong. wrong. wrong.

A rebuttal -

1. It Defeats User Expectation

This only holds true if A: your user has never seen a mobile site before (and if they are on a phone thats true for about ~0.5s), or B: if your responsive design is poorly implemented. A well designed site will be intuitive.

2 - It Costs More and Takes Longer

Let's assume that you have customers that will use your site on a non desktop device. If that is the case - you are making users use the wrong tool for the job. A site that takes advantage of the desktop experience will not work as well on mobile. Creating a tailored experience for them will absolutely increase conversion (if your site converts anyone to anything), and at the very least, reduce frustration and eye strain. I can't speak for everyone, but the month or two of part time work it took one of my jobs to add a mobile site was paid for by the increase in sales not too much long after. Not only that, but its now built in. When the kindle fire was released, we saw great numbers on that device. Why? because the responsive design was well done and fit that device's screen great. Saying that it 'costs more' is incredibly short sighted.

3.Non-Responsive Designs Usually Work

'working' doesn't mean it can't work better. all text websites work, too. But we use images because they enhance the experience.

4. There is Often No Load Time Benefit All this is saying is that a lot of sites are done badly. This has nothing to do with the style of responsive design in general. Tools like Modernizr allow you to optionally load a number of resources that would otherwise not load.

5. It’s a Compromise Of course? All design is compromise. The goal is to make the compromise in the favor of the customer.

Responsive design is not a silver bullet, and not always a good idea, depending on the site - but this article is /really / weak.

Re:Why Responsive Design Is Not Worth It by kellishaver on Tuesday September 25, 2012 @10:17AM (#4570426)
So many people talk about responsive design taking longer and being not worth the effort.... That's true if you start with the desktop and try and work your way backwards to the small screen, which is how a lot of designers look at it, I think.

If you take a progressive enhancement approach and work your way up from low-end mobile to full-featured desktop, the process is 100x easier and the end result is, in my experience, an overall cleaner and more stable code base that makes for better performance across all devices/platforms.

Re:Why Responsive Design Is Not Worth It by lucisferre on Tuesday September 25, 2012 @10:48AM (#4570611)
Untrue in my experience, but if you're experience has been positive that's great. I've done the mobile first approach and found that for anything with interactions that are more complex than a simple blog or other content driven service it does add significant time and effort and the quality of the desktop experience typically also suffers as most of the focus is on polishing the look and feel of the mobile browser experience in addition to addressing each and every browser quirk between Android and iOS.

I'm a fan of responsive/adaptive designs but based on experience just dont' feel I can always recommend the "mobile first" approach to startups. Perhaps for more established businesses that can afford the extra design effort, it's fine. I still have a lot of reservations though.

Re:Why Responsive Design Is Not Worth It by kellishaver on Tuesday September 25, 2012 @10:58AM (#4570669)
There are a lot of cases where responsive design just isn't a good fit, and something with complex user interactions (like a lot of web apps) is often one of them. Responsive design is great for things like content sites, galleries, informational sites... most forms of content publishing. Anything that requires the user to actually create and/or manage large amounts of data or has a lot of interactive media, however, would probably benefit more from a dedicated mobile site and/or app.
Re:Why Responsive Design Is Not Worth It by tzumby on Tuesday September 25, 2012 @11:35AM (#4570888)
You are absolutely right about the complex user interactions. In that case the responsive design could just be informational only (hiding all the complex features that would otherwise be very hard to use on a mobile screen).
Re:Why Responsive Design Is Not Worth It by ilyay on Tuesday September 25, 2012 @12:22PM (#4571162)
This is a terrible suggestion. The age of crippled, stripped down mobile sites is long gone, and smartphone users expect full functionality on their phones. If that functionality can be provided with a responsive design, that's great. If they have to use the regular website and do some zooming and panning, that's a nuisance, but one with which users are familiar. It's certainly better than not having the feature available at all, or having to hunt for a link to disable the mobile layout.
Re:Why Responsive Design Is Not Worth It by lucisferre on Tuesday September 25, 2012 @02:01PM (#4571717)
I'm really tired of everyone talking in absolutes (also the overuse of the word terrible). The right answer is (almost) always "it depends".

It depends how critical that functionality is to the core value the site provides. It depends how appropriate it is to a mobile platform experience.

As a contrived example I'd probably be perfectly happy if I could only browse, read, and maybe vote on HN if the mobile experience of reading was significantly improved. I never want to write a comment from my phone, I hate typing on it. Not a great example since a textarea isn't complex and it's easy to add to a mobile layout, I just want to get across the point that not all interaction is appropriate or important on every platform.

This is why responsive design is hard, because doing it well means far more than just changing the layout, size and visibility of elements. It is a different interaction paradigm and generally will need to be treated as such to maintain a quality experience.

Re:Why Responsive Design Is Not Worth It by lmm on Tuesday September 25, 2012 @03:27PM (#4572185)
>As a contrived example I'd probably be perfectly happy if I could only browse, read, and maybe vote on HN if the mobile experience of reading was significantly improved. I never want to write a comment from my phone, I hate typing on it. Not a great example since a textarea isn't complex and it's easy to add to a mobile layout, I just want to get across the point that not all interaction is appropriate or important on every platform.

But you didn't get across the point, because your example isn't true. I want to post on HN from my phone; heck, I've posted on HN from my kindle before. I wouldn't give that up for all the optimized mobile design in the world.

Grandparent is right, an absolute is appropriate here. Provide all the functionality of your desktop site, or I won't use your mobile site.

Re:Why Responsive Design Is Not Worth It by ChrisNorstrom on Tuesday September 25, 2012 @06:44PM (#4573116)
That's exactly how I started, with the low-end mobile and worked my way up. Check out a little project I made using css media queries. http://www.TimeForZen.com (resize the window width to mimic tablet and smart phone widths)

It didn't defeat user expectation, it didn't cost more and take longer, it works better than a non responsive design would, it doesn't really save any bandwidth but it does make code maintenance easy, and it's NOT a compromise.

I can see some of his points when applied to more complicated non-blog sites with ads and sidebars. Rather than say "responsive design isn't worth it" he should have written it from the perspective of "responsive design isn't always enough".

Re:Why Responsive Design Is Not Worth It by jasomill on Wednesday September 26, 2012 @12:51AM (#4574206)
When I tap-zoom the text in your "about" page on my (retina, iOS 6) iPad, the text box moves off the screen to the left, and when I scroll down on the same page, the top of the text box moves down with the viewport. Sadly, I have come to "expect" these sorts of strange behaviors on responsive sites...
Re:Why Responsive Design Is Not Worth It by AJ007 on Tuesday September 25, 2012 @12:54PM (#4571343)
I decided to try converting some of my site designs to bootstrap recently, instead of having one of our developers do it. I haven't actually coded the HTML/CSS design on an entire page in 3 or 4 years now (not counting simple stuff) and this was light years easier than I ever remember. If responsive design is hard, your doing it wrong.
Re:Why Responsive Design Is Not Worth It by lucisferre on Tuesday September 25, 2012 @02:05PM (#4571733)
You built one very basic bootstrap site and despite not having done HTML/CSS in 3/4 years you've now got the expertise to tell everyone else they are doing responsive design wrong?

I've built responsive sites in Bootstrap, Foundation and "without a net" and I wouldn't presume to tell anyone what's hard or not about responsive design or even if I'm doing it right or wrong. Look if out-of-the-box Bootstrap is good enough for your needs (and more importantly your user's) awesome. That's called an anecdote.

Re:Why Responsive Design Is Not Worth It by ceworthington on Tuesday September 25, 2012 @03:02PM (#4572055)
I totally agree with this.

When I shifted my design thinking to use this approach to building UX, I found not only were my sites/apps easier to bring to mobile but the desktop versions were usually better as well. Mobile first designs often lead to better designs on desktop, at least in my experience so far (with content-heavy apps).

Re:Why Responsive Design Is Not Worth It by TazeTSchnitzel on Tuesday September 25, 2012 @04:43PM (#4572553)
>That's true if you start with the desktop and try and work your way backwards to the small screen

I resize my browser window to be less wide. If it looks too big, I add some CSS to fix that. I resize it to be even thinner. If it now looks too big again, I'll add some CSS to fix it. And then I'm done.

Granted, I'm a programmer, not a designer, but this is the way I do "responsive design".

Re:Why Responsive Design Is Not Worth It by lixon on Tuesday September 25, 2012 @10:43AM (#4570575)
i second that :)
Re:Why Responsive Design Is Not Worth It by nhangen on Tuesday September 25, 2012 @10:28AM (#4570493)
I'm going to take exception to your 2nd point.

To start, regardless of whether the experiment pays off long-term, that does not negate the fact that it does require extra design and development time. There is much more code to handle, regardless of whether you use a framework or build it bespoke. Additionally, whether you design for mobile first, or last, there is more design time required. Period.

Second, both the author and OP have lumped 100% of all websites together, and generalized the argument. Sure, responsive may be worthwhile in some cases (as the post misses), but there are many cases where it isn't worthwhile.

My argument for using responsive is that yes, it's worthwhile, if and when the return is there. As a freelancer, this means I must be getting paid for the extra work. As a company owner, this means that we must see value from the resource spend, which could be in the form of better UX, more eyeballs, or more profits.

Re:Why Responsive Design Is Not Worth It by davedx on Tuesday September 25, 2012 @10:32AM (#4570514)
Indeed. I consider myself fairly well informed compared to most of my peers, but the sheer choice of technologies for building modern web apps (responsiveness, other front-end UX considerations) is daunting. I'm trying to build up a list of modern web design/development links for myself, but I'm already lost. The parent comment about "modernizr" made me sigh with frustration: yet another tool/tech I don't know about or have time to learn.
Re:Why Responsive Design Is Not Worth It by wonderyak on Tuesday September 25, 2012 @01:09PM (#4571418)
I don't meant to be rude but if you are not familiar with Modernizr and you work with markup; you are probably nowhere near as well informed as you think you are.
Re:Why Responsive Design Is Not Worth It by tokenizer on Tuesday September 25, 2012 @10:45AM (#4570592)
I'm confused. Is this argument for responsive versus standalone desktop or mobile, or responsive versus two sites, one for each.

Because I'd like to say that managing two projects, be it two code bases that both have to be created and configured, takes just as long if not longer, than simply building the edge cases needed for an intuitive responsive site.

But there's points for both methods in my books. I just think not accounting for mobile either way is ridiculous (unless a client is unwilling to pay for it).

Re:Why Responsive Design Is Not Worth It by nhangen on Tuesday September 25, 2012 @10:57AM (#4570660)
I'm saying that in many cases, you don't have two projects, you have just one, which is that of the website built for desktop/laptop screens. Could be a cheap client, or a short-term project that doesn't require a mobile site, etc.
Re:Why Responsive Design Is Not Worth It by cleverjake on Tuesday September 25, 2012 @10:44AM (#4570584)
And I, to yours.

No one is saying that it takes extra time and money. Everything that is done in your life takes time and energy. But if you can do x amount of work and get y amount of gain, where x < y, I don't see the fact that x exists as a negative.

To your second point, please see my conclusion. I agree with you.

Re:Why Responsive Design Is Not Worth It by bicknergseng on Tuesday September 25, 2012 @01:18PM (#4571475)
I would argue 1 even in the case of users that have seen mobile sites before. Unless the desktop version of the site is completely unusable on a mobile device (which to me points to bad design anyway), I've hated mobile site experiences... the reality is that good mobile site design is the exception rather than the rule. Take eBay for example. The mobile site makes me feel like I'm on WAP and not a device with more power than the Space Shuttle.

On that note, I'm really curious what "continue to full site" clickthroughs are across the internet. I could be the only one thinking this way.

Re:Why Responsive Design Is Not Worth It by nico on Tuesday September 25, 2012 @01:32PM (#4571547)
I totally agree. It's happened to me many many times that some functionality is missing on the mobile website, and they usually make it impossible to get to it (eg. LinkedIn (and many other sites, including a lot of Google-made things) even though it has an option to go to the desktop site, it will automatically send you to the mobile site on some parts of the site, completely defeating the option of going to the desktop site).
Re:Why Responsive Design Is Not Worth It by cleverjake on Tuesday September 25, 2012 @01:30PM (#4571532)
That is mostly because eBay is a generally badly designed site. They have one of the most averse-to-change user bases on top of it, so bad decisions stick for a longtime.

Check out amazon, or google for wonderful mobile versions of sites.

I don't understand your question - are you saying how to full site click throughs work? Most of the time it sets a cookie or a query string that overrides the session 'isMobile' value. If you meant something else - please elaborate.

Re:Why Responsive Design Is Not Worth It by bicknergseng on Tuesday September 25, 2012 @02:42PM (#4571938)
No disagreements on eBay's terrible design. If you go to 5 different pages on their desktop site you'll get 5 fully different designs.

OK, let's take Amazon (I was going to complain about Google's image search for mobile but I just checked it and it addressed the issues I had with it... still no pinch to zoom, though). On the desktop site, I get a home page filled with images of products that I'm probably interested in based on my previous Amazon habits. On the mobile site, I mostly get text with a small image advertising the Kindle Fire. If I browse to books, I get ~5 list items on the screen at one time, vs the desktop version (on my mobile) that gives me a landing page of bestsellers and books tailored to my interests. There's a whole layer of functionality missing on the mobile version for the sake of formatting that I don't honestly need. The reason why the original iPhone's web browser was so amazing was that it made it comfortable and efficient to browse full desktop web pages on a small screen via the whole pinch to zoom action. On a text heavy page, if I double tap it reflows the whole page to fit text on my screen.

Now, I'm not totally against mobile sites. I've seen some truly wonderfully designed mobile sites like Google's main page and some from design centric companies who don't rely heavily on long lists or grids of items. But I would generally agree with the OP that dedicated mobile sites are largely unnecessary at best and a design nightmare most of the time that actually serves to degrade the expected user experience. Users want to pinch to zoom and drag and double tap.

No I'm asking about click through rates to full sites. As in, what percentage of users choose to stay on the mobile version and what percentage click through to the full desktop site? What percentage of users know how to change their user agent on their mobile browser to only get desktop sites (probably minuscule).

Re:Why Responsive Design Is Not Worth It by nico on Tuesday September 25, 2012 @01:36PM (#4571563)
If by google sites you mean google.com and the search results, I would agree, but anything else is usually a disaster, including pretty much all of google apps.

As the article says, the good sites are not the rule, but the exception.

And I think the question in the above comment was simply about wondering how many people, out of all mobile visitors to a website, click on the desktop version link (what percentage of users prefer the desktop version on their mobile devices).

Re:Why Responsive Design Is Not Worth It by Xurinos on Tuesday September 25, 2012 @04:43PM (#4572555)
I agreed with your first post. I am also holding out for the thought that there are exceptions. Interestingly, this comment stood out to me: "That is mostly because eBay is a generally badly designed site. They have one of the most averse-to-change user bases on top of it, so bad decisions stick for a longtime." But they have a huge userbase. Transactions are happening. This is where my confusion kicks in... People claim a site has bad design, but a ton of users actively use the service. I would venture to guess that a large percentage of those users are not tech-savvy.

So what is the measure by which we are able to claim that some site's design is "bad"? I provide the counter: large, active userbase and a lot of money moving through ebay. Perhaps not enough money goes there? Do we think someone could create a competitor to ebay with a "better" site design and steal ebay's crowd? What role does site design actually play here?

Re:Why Responsive Design Is Not Worth It by bicknergseng on Tuesday September 25, 2012 @08:24PM (#4573543)
I think you bring up some interesting points, but I just want to address the "Do we think someone could create a competitor to ebay with a "better" site design and steal ebay's crowd?" line.

eBay isn't successful because of design or lack of design. It's successful because it's where people go to sell or buy in an online auction format. Same thing for Craigslist.

Yet look at Apple, specifically the iPhone and iPod. The smartphone and mp3 player were not new innovations, but Apple's design and marketing built the world's richest company on them.

TL;DR: Design makes all the difference. Design makes none of the difference.

Re:Why Responsive Design Is Not Worth It by blago on Tuesday September 25, 2012 @03:38PM (#4572246)
My personal experience is that more often than not I end up searching for the "Desktop version" link. Especially on websites I'm familiar with. It would appear that "poorly implemented" is the norm. Bottom line: I suffer.
Re:Why Responsive Design Is Not Worth It by dubcanada on Tuesday September 25, 2012 @10:20AM (#4570440)
Yup, can't agree more. This article is a joke.
Re:Why Responsive Design Is Not Worth It by masklinn on Tuesday September 25, 2012 @10:25AM (#4570473)
> 'working' doesn't mean it can't work better.

And while modern phones have become rather good at zooming on the content (which does not mean the text gets big enough, far from it, I regularly encounter blogs I can't read without using readability other other equivalent tools, because the font is too small even zoomed in) scrolling is still rather fiddly, especially one-handed: it's not rare that the scrolling "starts wrong" and I end up decentered from the column I want to read, and now I have to fiddle with positioning and zooming to get back to reading.

Re:Why Responsive Design Is Not Worth It by cleverjake on Tuesday September 25, 2012 @04:49PM (#4572589)
Re:Why Responsive Design Is Not Worth It by lwhi on Tuesday September 25, 2012 @10:14AM (#4570408)
Thank you for writing this so I didn't have to.
Re:Why Responsive Design Is Not Worth It by calinet6 on Tuesday September 25, 2012 @11:32AM (#4570873)
It seems the whole brunt of the article is, "Eh, it's good enough the way it is." It's just lazy and useless.
Re:Why Responsive Design Is Not Worth It by nhangen on Tuesday September 25, 2012 @12:34PM (#4571227)
Actually, I think he's suggestion that we should let the hardware manufacturers and OS providers worry about scaling content to their screens/OS, rather than doing it all client side.
Re:Why Responsive Design Is Not Worth It by snogglethorpe on Wednesday September 26, 2012 @04:33AM (#4574696)
The hardware/OS-providers will almost always do a far worse job though, because they simply don't have enough information. Just using smaller pixels or hardware scaling/filtering to linearly scale down a "big browser" site typically results in an unreadable page at typical mobile screen-sizes.

Useful size-adaptability is all about knowing what's important and what's not, and what constraints need to be maintained for usability. The site author knows these things very well, but the hardware / OS / browser do not.