I’m just really disappointed that in iPhone, when you’re designing an app you can do whatever you want with swipe left/right, and it’s only bottom/top swipes that are reserved for system menus/escape hatches.
It’s very difficult to get app-like parity when users are used to horizontal swipes opening menus. Android browsers are able to achieve this gesture parity and feel more native app-like because the browser’s “back” function is a button, rather than a gesture. Left/right swipes are free to be used by the webapp, just like an installed app here.
It’s something to work around certainly since iPhone users have gotten used to side-swipe to back/forward in a browser, but I hope you can understand my reasoning for being miffed about it.
Sort of, I’d argue that taking away swipe left to go back (in terms of web browsing, anyway) is quite user hostile as well. I don’t think anyone is “right” here, there’s just different behaviors that people may prefer… or not prefer…
I do feel very confident that those classic (and awful) dedicated Android screen buttons are going to die a painful death over the next few years. So any behavior that requires those “mandatory” buttons present is cruisin’ for a bruisin’
Well, that’s the deal: you’re the consumer, Apple is the designer. There’s no way around it. They. Know. Better. Proof? They are Number One. People die for them. Literally.
No, I’m not an iPhone user, and yes I do want what @featheredtoast has been cooking on my Android device
One inconsistency I noticed was that if I view the user menu by pressing my avatar - as we usually do, I can no longer press the avatar again to dismiss the user menu I have to swipe.
So if I’m not a swiper and I press the user avatar I seem to have to swipe to remove it. A function of the lovely full height menu I guess.
It feels like I should be presented with either a swipe to view, swipe to hide OR press to view press to hide interface - not a mixture.