Live data from Hacker News

Why Responsive Design Is Not Worth It

managewp.com

21–30 of 139 posts

Re: Why Responsive Design Is Not Worth It

#21
Like the author says, I would argue that it depends on the experience. The first thing to determine is: what is the core experience you're going after. For example, if you're an e-commerce website and your visitors expect to be able to find things, follow things, and then buy things, a mobile website that leaves out key functionality is frustrating.

There have been many a time that I've searched desperately for the "desktop version" of the site because I need to do something that the mobile version doesn't allow me to.

Re: Why Responsive Design Is Not Worth It

#22

This article lost me the moment he quoted wikipedia to explain responsive design. This is not 8th grade, come up with your own definition if you're such an expert. The rest of article was downhill too. Claiming the full site looks fine on your iPhone is akin to saying "It works on my machine!". It's pretty much a waste of time from top to bottom.

Yea that annoyed me too. What if I can't afford and iPhone with Retina display?

Re: Why Responsive Design Is Not Worth It

#23

Personally, I do not want to see a sidebar, taking up a third of the screen, on my smartphone. I find the example that he considers fine quite unusable and would not read that on a smartphone.

Wouldn't that make you think that we should revisit the sidebar to find a more effective way to navigate rather than simply telling the user that you shouldn't have any options?

Re: Why Responsive Design Is Not Worth It

#25

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 desk…

> '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

#29

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 desk…

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

#30

Personally, I do not want to see a sidebar, taking up a third of the screen, on my smartphone. I find the example that he considers fine quite unusable and would not read that on a smartphone.

Wouldn't that make you think that we should revisit the sidebar to find a more effective way to navigate rather than simply telling the user that you shouldn't have any options?

> Wouldn't that make you think that we should revisit the sidebar

No.

The sidebar works and is effective when there's significant horizontal space, such as on a desktop screen with ample horizontal space. It just does not work when horizontal space is a premium, as is the case on smartphones (which generally barely fit a standard typographic line length at readable size in portrait)

Post reply on HN