[PebblesHD]

This isn't necessarily a problem as more sites become responsive and make a proper effort to accomodate mobile browsers. Where this will be a problem is poorly written desktop only sites that just make the change to get faster mobile interactions. I hope this encourages more of the former and less of the latter.

EDIT: If you don't agree why not explain your point instead of randomly downvoting. I believe this change is overall a good thing as it means designers and developers can stop using nasty hacks to get around the delay as they have been doing. Hopefully it will also mean more developers make the effort to make their sites work on mobile instead of the half efforts that seem to be common now.

[glesica]

I didn't downvote you, but I also don't agree with your assumptions. First, I don't think that desktop sites are such a big problem on mobile (though some are, admittedly, unusable). At least with a desktop site I can zoom and figure out a way to get to the content I want (in fact iOS does, or used to, to let you double-tap on the content and it would intelligently zoom to fit). Most mobile sites with which I interact, on the other hand, are terrible. Either the text is too small and the page has disabled zooming, or content overflows and doesn't allow me to pan to see it, or some other terribleness. "Responsive" sites are actually some of the worst to interact with on mobile (for me).

I really don't believe that most developers of "desktop sites" care about mobile or do anything to optimize for it, and therefore wouldn't care about a 350ms delay, or even be aware of it. The people who are going to foul this up, it seems to me, are the "mobile web" developers who try to make their sites act like apps instead of just presenting content in a flexible manner.

[Flow]

This has been my experience too. I surf in landscape mode on an iPhone 5, and far too often there's a fat social-sharing-bar at the bottom, and a fancy site-header-bar at the top, leaving about 1cm of readable and scrollable content. Wtf are they smoking?

A tip: Hold down your finger on the reload circle-arrow to load the desktop version of the page.

[dredmorbius]

Reader mode FTFW.

Fuck fixed headers / footers. Fuck social. And fuck fixed social header/footer bars specifically.

[jedrek]

I hate fixed bars on desktop as well - I still scroll with my keyboard and it chops content off willy nilly.

[dredmorbius]

Yep. I've been creating my own local stylesheets under Stylish, including a default which pretty effectively nukes social elements and fixed headers, with some collateral damage I _may_ fix selectively on specific sites.

If you're naming your primary elements, or ascribing them values of "share" or "social" (wildcard search), they're likely to get nuked.

[evook]

Best answer so far. Print mode is also not bad.

[dredmorbius]

Print mode (offered by websites) so often 1) launches the actual browser print dialog and 2) closes the fucking page when the dialog's closed that I've largely abandoned use of it.

I'll sooner copy/paste text into a vim buffer.

[fanf2]

Oh man, this makes GitHub usable on my phone! Their mobile site is so shit.

[jakobegger]

Thanks for that tip!

[Tepix]

Install a content blocker...

[PebblesHD]

And thats a perfectly reasonable complaint to make, my argument is simply that developers of 'desktop sites' should in fact care about mobile browsers as they make up over 50% of page views on most large properties. If they can't make the effort to accomodate a smaller browser to the point where loss of the zoom function breaks their functionality then I feel that this kick might get them to work out these issues.

[Natsu]

To be fair, people on mobile might have downvoted you by hitting the wrong button. That's very, very easy to accidentally do when reading HN on a phone, as well as being somewhat ironically on-topic here.

[mattlutze]

The trouble is really with poor or improper application of responsive features to desktop-first sites and applications. The more people try to build responsive sites, the more they'll get it wrong and introduce all sorts of experience errors that can't easily be circumvented on your mobile device.

Same thing happened through the development of desktop browsing though, and it's more or less gotten better (weird fixed scroll elements in nested tables isn't a thing anymore, mostly).

Enough frameworks and abstractions and hosted services will show up and it'll get better. But, it's going to be a problem (if not a growing one) for a while still. Or, convert-to-Reader mode on mobile browsers will get a ton better and people will just get used to wiping out all the uniqueness of the sites they're browsing.

And, as a browser I still want to be able to zoom in on the 70% column the site has or override the weird 10pt font they thought looked modern in order to read it.

[jeffehobbs]

Unscalable != Responsive. One does not preclude the other.

[PebblesHD]

I didn't say it precluded the other, Just that as more sites have a proper mobile view scaling becomes less necessary.

[tedunangst]

The more sites attempt "proper mobile views" the worse it gets. In 2011, mobile safari was practically perfect. Now half the sites I visit have found some way to dick things up because they hired some nitwit designer to "mobile first" things to shit.

[UIZealot]

This has been my experience as well. I'm sure there're sensible things to tweak on a "regular" web site to make it more mobile friendly. The web development community just went to the extreme with gimmickry and the web suffers for it, desktop or mobile.

[coldtea]

Amen brother! We could browse the web as it was intended to be on our iPhones in 2007-11, and then this responsive fad comes along and we're back to "mobile special" designs again...(remember WAP?)

Those "mobile special" layouts are annoying enough on their own on a phone (with their dumbing down of the UI), but they are doubly annoying when you're used to the web version of a website, and have to hunt for things in the "responsive" mobile version.

[Sophistifunk]

And we're saying that's not your decision to make. The user should always be able to scale and zoom.

[achairapart]

So let's add pinch to zoom to native apps and the whole OS UI by default.

[UIZealot]

iOS supports zooming the entire screen as part of its accessibility feature set. Though you have to turn it on, and the gesture is three-finger-tap and drag instead of pinch.

[tracker1]

That would be problematic for apps like maps (which I think the street name fonts are too small, and don't scale), or photo/picture programs.

[smcl]

I have bumped into this countless times - street names too small, I subconsciously pinch to zoom, street names get scaled accordingly and are still too small for me. The solution is simple - just move the i<Device> closer to my face - but it's thrown me a couple times. Not sure if this is a UX error or just me being daft.

[dredmorbius]

Working with a visually disabled colleague recently iI'm becoming all to painfully aware of how much this is the exception. For Web, apps, OS, devices, and more.

[stormbeta]

I couldn't disagree more. There should always be a way to make the content I'm looking at bigger in order to see it more clearly, especially for users with poor eyesight.

"responsive design" does not magically eliminate this need, and I agree with the posters saying that disabling of user-scrolling should never have even been allowed in the first place.

And that's not even touching on the fact that most "responsive" sites I've seen get it horribly wrong.

[lexicality]

You can't zoom in normal apps.

[gorena]

In apps properly coded against the UIFont APIs, you can: https://developer.apple.com/library/prerelease/ios//document...:

[silon7]

That's why web is/was better for many things, especially when you could increate fonts only (unfortunately, many sites have bad css that breaks this).

[pjc50]

That's a deficiency in native apps, not something to be taken away when it does exist for web apps.

[tracker1]

Not at all true... I am far sighted, since most of what I look at, including my monitors are more than a few feet away, I tend to see them fine.. my phone is the only device I really have a lot of trouble with. I run in "extra large" font mode, and set my browser zoom to 125%... even then many sites, I have trouble seeing stuff... if there's an image that isn't full width, then I likely can't make out the detail....

Not being able to zoom in to at least 2x, is a pain... if your content doesn't overflow, then sure set the minimum zoom to 1x, and the max to 2 or 3.. but disabling it altogether is just painful to experience... and many of the "suggestions" to fix mobile scaling include disabling zoom. I'm not even that old (40), but I imagine the problem is worse for people well into their 60's.

If you're using a font-size less than 12pt, you should emphatically NOT be disabling scaling... Unfortunately many sites/apps do just that, and often don't respect the usability settings in the OS (facebook on android was particularly bad, as in too small, before I uninstalled it).

[zelos]

Define 'proper' mobile view. How can the designer know how the user is viewing their site? On a cheap device with low contrast? At an awkward angle at arm's length while trying to keep the baby asleep? Trying to read something quickly when you don't have your reading glasses on you?

[jakobegger]

The problem is that some designer whips up a mobile theme, disables scaling, and then an content editor posts some unexpected content that breaks the design, and the readers can't do anything about it.

It gets even worse when designers sell those themes to non-technical people, who have no way to fix the mess the designer caused by disabling scaling/scrolling.