Your mobile page blows on iOS. You and all the sites like you need to stop hijacking the bottom touch event preventing me from bringing up the interface to press back. As far as I am concerned, this action is the new pop-up window or the web because it forces me to perform a different action than I expect to go back.
Noted, thanks for the headsup - I'll look into that and fix it. I've not spent much time yet making it responsive, so haven't done much iOS testing, but I will.
Thanks, really. I know it's HN and I'm not trying to pick on you, but it's seriously starting to drive me insane. I can't remember where else I saw it, but in the last week I think I've ran into this several times (I think Salon or TNW or somebody else started doing it too). It makes me think my phone is broken or something.
On the flip side (and I haven't used this site on iOS, so can't weigh in) the fact that Apple decided to turn over 50px of usable space at the bottom of the page to their UI and effectively make it unusable for touch events is really, utterly infuriating.
Hold on, you have to think about the users, not just of your site, but all the sites out there. It's utterly infuriating as a user to have your UI hijacked, by which I mean actions which are normally consistent across the system stopping working. And it's utterly certain that if UI can be hijacked some people will do so.
Maybe there is some perfect-world solution where, if something totally wonderful can happen if the UI would get out of the way, and the user is happy with it, it could be made to happen. But in practical terms when dealing with the Web as the messy place it is, the only realistic way to limit the damage web designers can wreak, is to strictly limit the capacity to override system interfaces.
Comments
Dear Submarine,
Your mobile page blows on iOS. You and all the sites like you need to stop hijacking the bottom touch event preventing me from bringing up the interface to press back. As far as I am concerned, this action is the new pop-up window or the web because it forces me to perform a different action than I expect to go back.
Noted, thanks for the headsup - I'll look into that and fix it. I've not spent much time yet making it responsive, so haven't done much iOS testing, but I will.
Thanks, really. I know it's HN and I'm not trying to pick on you, but it's seriously starting to drive me insane. I can't remember where else I saw it, but in the last week I think I've ran into this several times (I think Salon or TNW or somebody else started doing it too). It makes me think my phone is broken or something.
In any case, it was a great article.
On the flip side (and I haven't used this site on iOS, so can't weigh in) the fact that Apple decided to turn over 50px of usable space at the bottom of the page to their UI and effectively make it unusable for touch events is really, utterly infuriating.
Hold on, you have to think about the users, not just of your site, but all the sites out there. It's utterly infuriating as a user to have your UI hijacked, by which I mean actions which are normally consistent across the system stopping working. And it's utterly certain that if UI can be hijacked some people will do so.
Maybe there is some perfect-world solution where, if something totally wonderful can happen if the UI would get out of the way, and the user is happy with it, it could be made to happen. But in practical terms when dealing with the Web as the messy place it is, the only realistic way to limit the damage web designers can wreak, is to strictly limit the capacity to override system interfaces.
What's a bottom touch event?