2 ms·

I disagree, and side with the sibling comments consensus: having switched from Android to iOS this summer, this was the largest friction for me – this and the b

I disagree, and side with the sibling comments consensus: having switched from Android to iOS this summer, this was the largest friction for me – this and the bad onscreen keyboard, and the buggy text selection (editing URLs is a chore, holding the spacebar to move the cursor is broken when you move too far...) Also this has always bothered me before switching whenever I used a friend's iPhone for a moment. The trouble alread begins when some link in Safari opens a 3rd party app. Sounds weird, but Apple could really learn a lot about UX from Google regarding this "go back" interaction. It really was a joy how reliable it works even for inception-level nested app interactions. On iPhone, half of app switches (at least) require me to swipe up or go to the home screen. And positioning the unreliable sometimes-available back button at the top left has made me drop my phone at least once. For all that's to like about iOS, "navigation patterns" are not one of them for me.

matchbok 3y ago
You can swipe left/right on the very bottom of the screen to switch "back" to apps. The back swipe gesture is for "in app" navigation and is much better than what Android has. The Android back button can do like a million things: dismiss keyboard, go back a page, switch apps, go home, etc. It's a mess.
- moritzwarhier 3y ago
  Thanks, didn't use this before. I'm not a big fan of so many similar gestures though. I already sometimes accidentally switch tabs in Safari by swiping. Using this app-switch gesture from safari seems like a nightmare when first trying. And generally pretty fiddly. Maybe it needs getting used to. The swipe area is very small on the vertical axis and there's also some risk of hitting in-app buttons, especially if apps place buttons at the bottom — although I guess this is discouraged. It's especially annoying when using a phone cover. And I like mine - iPhone would be unusable for me without it because it's also much more fragile than all my previous budget Android phones. Will try getting used to it though. Re your "It's a mess" comment: I've never had a problem with the android back button, it always did exactly what I expected and it was easy to build an intuition for it. The context-dependand behavior always seemed very well thought-out to me, because I never ever had to think about it.
  - matchbok 3y ago
    I agree. The discoverability of gestures is tough and something that nobody has really cracked yet.
cassianoleal 3y ago
I don't know what you find bad about the iOS keyboard. I don't think it's brilliant either but I find it much better than Android's. > the buggy text selection (editing URLs is a chore, holding the spacebar to move the cursor is broken when you move too far...) I'm right there with you on these. > positioning the unreliable sometimes-available back button at the top left has made me drop my phone at least once. As a person with small hands, I hear you. I miss the days of the original iPhone which was probably >90% usable with a single hand. Even the discontinued iPhone Mini was too large - which I suspect has been most of the reason of its "failure". Comparing with larger phones, the smaller screen is a downside, and it came without the upside of actually being a single-hand device so it's more or less lose-lose.

matchbok 3y ago

You can swipe left/right on the very bottom of the screen to switch "back" to apps. The back swipe gesture is for "in app" navigation and is much better than what Android has. The Android back button can do like a million things: dismiss keyboard, go back a page, switch apps, go home, etc. It's a mess.

moritzwarhier 3y ago
Thanks, didn't use this before. I'm not a big fan of so many similar gestures though. I already sometimes accidentally switch tabs in Safari by swiping. Using this app-switch gesture from safari seems like a nightmare when first trying. And generally pretty fiddly. Maybe it needs getting used to. The swipe area is very small on the vertical axis and there's also some risk of hitting in-app buttons, especially if apps place buttons at the bottom — although I guess this is discouraged. It's especially annoying when using a phone cover. And I like mine - iPhone would be unusable for me without it because it's also much more fragile than all my previous budget Android phones. Will try getting used to it though. Re your "It's a mess" comment: I've never had a problem with the android back button, it always did exactly what I expected and it was easy to build an intuition for it. The context-dependand behavior always seemed very well thought-out to me, because I never ever had to think about it.
- matchbok 3y ago
  I agree. The discoverability of gestures is tough and something that nobody has really cracked yet.

cassianoleal 3y ago

I don't know what you find bad about the iOS keyboard. I don't think it's brilliant either but I find it much better than Android's. > the buggy text selection (editing URLs is a chore, holding the spacebar to move the cursor is broken when you move too far...) I'm right there with you on these. > positioning the unreliable sometimes-available back button at the top left has made me drop my phone at least once. As a person with small hands, I hear you. I miss the days of the original iPhone which was probably >90% usable with a single hand. Even the discontinued iPhone Mini was too large - which I suspect has been most of the reason of its "failure". Comparing with larger phones, the smaller screen is a downside, and it came without the upside of actually being a single-hand device so it's more or less lose-lose.