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.
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.
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.
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.
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".
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.
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).
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".
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.
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).
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.
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.
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.
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).
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).
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?
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.
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.
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.
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.