7 ms·

Fixed bars are annoying and should rarely be used. But what's even worse is when the mobile version helpfully removes the content or feature that you'd like to

Fixed bars are annoying and should rarely be used. But what's even worse is when the mobile version helpfully removes the content or feature that you'd like to see. Please just have one site, make it efficient, and be done with it.

mercer 12y ago
I'm so happy that google is not officially recommending this. More than once that's been the one argument that worked with clients.
- hiphopyo 12y ago
  I really hope they'll bring up this issue at this year's IO.
nostromo 12y ago
It's so much easier to fuck up mobile than it is to do it right. And if you're not doing it exactly right, don't do it at all. Here's what the EC2 console looks like on mobile: http://i.imgur.com/MfbCdhU.png http://i.imgur.com/MfbCdhU.png It appears that Amazon is doing this on purpose... <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"> Yes... user-scalable=no
- MattHeard 12y ago
  > Disabling user-scalable (namely, the ability to double tap to zoom) allows the browser to reduce the click delay. In touch-enable browsers, when the user expects the double tap to zoom, the browser generally waits 300ms before firing the click event, waiting to see if the user will double tap. Disabling user-scalable allows for the Chrome browser to fire the click event immediately, allowing for a better user experience. > From Google IO 2013 session https://www.youtube.com/watch?feature=player_embedded&v=DujfpXOKUp8#t=1435s https://www.youtube.com/watch?feature=player_embedded&v=Dujf... Source: http://stackoverflow.com/a/16910559 http://stackoverflow.com/a/16910559
  - ehsanu1 12y ago
    I doubt that's why. In this case, as the site doesn't appear to render well at all on mobile in the first place, that meta tag was probably just blindly copy pasted from somewhere else that did have a responsive page.
  - deleted 12y ago
    [deleted]
- keeperofdakeys 12y ago
  There was/is an iOS bug where changing orientation after zooming would cut-off some of the page, most websites simply disable all zooming to "fix" it. http://blog.pgrady.com/post/29511322784/fixing-the-ios-orientation-bug-in-three-steps http://blog.pgrady.com/post/29511322784/fixing-the-ios-orien...
  - hiphopyo 12y ago
    Why would anybody want to enable zoom in the first place? Properly designed mobile web apps should already have decent sized text and graphics. In addition to the iOS orientation bug you mention, there's also that annoying click delay. A lot of people at StackExchange seem to recommend zooming though: http://ux.stackexchange.com/questions/19464/should-mobile-optimized-sites-allow-zooming http://ux.stackexchange.com/questions/19464/should-mobile-op...
    - judk 12y ago
      Because on a small screen the size vs data density tradeoff has a sweet spot that varies from one pair of eyeballs to the next.
      - hiphopyo 12y ago
        Yeah, that's true. But are we talking eyeballs within the same age group, or like teens vs. old people?
        chronomex 12y ago
        In my experience, it varies both within age groups and between age groups.
    - keeperofdakeys 12y ago
      I may want to zoom to see an image up close, or just to change text size. Outside apple, phone screens vary widely, and so do text sizes. You can't hope to find one that works on all phones for everyone.
hiphopyo 12y ago
How do scroll up bars perform vs. bars that disappear / reappear on click (ie. http://demos.jquerymobile.com/1.4.0/toolbar-fixed/ http://demos.jquerymobile.com/1.4.0/toolbar-fixed/), anybody know? http://ux.stackexchange.com/questions/57990/how-usable-are-bars-that-disappear-reappear-on-scroll http://ux.stackexchange.com/questions/57990/how-usable-are-b...

mercer 12y ago

I'm so happy that google is not officially recommending this. More than once that's been the one argument that worked with clients.

hiphopyo 12y ago
I really hope they'll bring up this issue at this year's IO.

nostromo 12y ago

It's so much easier to fuck up mobile than it is to do it right. And if you're not doing it exactly right, don't do it at all. Here's what the EC2 console looks like on mobile: http://i.imgur.com/MfbCdhU.png http://i.imgur.com/MfbCdhU.png It appears that Amazon is doing this on purpose... <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"> Yes... user-scalable=no

MattHeard 12y ago
> Disabling user-scalable (namely, the ability to double tap to zoom) allows the browser to reduce the click delay. In touch-enable browsers, when the user expects the double tap to zoom, the browser generally waits 300ms before firing the click event, waiting to see if the user will double tap. Disabling user-scalable allows for the Chrome browser to fire the click event immediately, allowing for a better user experience. > From Google IO 2013 session https://www.youtube.com/watch?feature=player_embedded&v=DujfpXOKUp8#t=1435s https://www.youtube.com/watch?feature=player_embedded&v=Dujf... Source: http://stackoverflow.com/a/16910559 http://stackoverflow.com/a/16910559
- ehsanu1 12y ago
  I doubt that's why. In this case, as the site doesn't appear to render well at all on mobile in the first place, that meta tag was probably just blindly copy pasted from somewhere else that did have a responsive page.
- deleted 12y ago
  [deleted]
keeperofdakeys 12y ago
There was/is an iOS bug where changing orientation after zooming would cut-off some of the page, most websites simply disable all zooming to "fix" it. http://blog.pgrady.com/post/29511322784/fixing-the-ios-orientation-bug-in-three-steps http://blog.pgrady.com/post/29511322784/fixing-the-ios-orien...
- hiphopyo 12y ago
  Why would anybody want to enable zoom in the first place? Properly designed mobile web apps should already have decent sized text and graphics. In addition to the iOS orientation bug you mention, there's also that annoying click delay. A lot of people at StackExchange seem to recommend zooming though: http://ux.stackexchange.com/questions/19464/should-mobile-optimized-sites-allow-zooming http://ux.stackexchange.com/questions/19464/should-mobile-op...
  - judk 12y ago
    Because on a small screen the size vs data density tradeoff has a sweet spot that varies from one pair of eyeballs to the next.
    - hiphopyo 12y ago
      Yeah, that's true. But are we talking eyeballs within the same age group, or like teens vs. old people?
      - chronomex 12y ago
        In my experience, it varies both within age groups and between age groups.
  - keeperofdakeys 12y ago
    I may want to zoom to see an image up close, or just to change text size. Outside apple, phone screens vary widely, and so do text sizes. You can't hope to find one that works on all phones for everyone.

hiphopyo 12y ago

How do scroll up bars perform vs. bars that disappear / reappear on click (ie. http://demos.jquerymobile.com/1.4.0/toolbar-fixed/ http://demos.jquerymobile.com/1.4.0/toolbar-fixed/), anybody know? http://ux.stackexchange.com/questions/57990/how-usable-are-bars-that-disappear-reappear-on-scroll http://ux.stackexchange.com/questions/57990/how-usable-are-b...