thinking a lot about how the guy who convinced Steve Jobs not to put a back button on the iPhone because it'd be inconsistent and confusing is also the same guy who scammed millions of dollars from people with his Humane AI pin that never worked and that they're just going to straight up brick brick soon
talk about a hero to villain arc 
and YES, my fellow Android peeps, the back button is, in fact, inconsistent and terrible. 
#Humane #HumaneAI #ImranChaudhri #Apple #iOS #iPhone #Android
@Rusty exactly.
You have 2, sometimes 3 different ways to navigate backwards (the swipe from the left), and there's no guarantee as to which you will need on a universal basis.
The previous app indicator is a nice design, I will admit. But it doesn't cover every use case.
And what I hate most, is that those controls are all towards the top of the device, especially on the giant iPhones Apple makes now.
On Android, the situation is improving (14 through 16 are finalizing the predictive back button which will show you where a back action goes), yet imperfect. But I do know one thing: the button is going to be in the same place no matter what, and I'll end up back where I started, or at least at Home if I keep pressing it.
@LiquidParasyte You don't usually have to tap on the top of the screen to go back in iOS. Whenever there's a back button on iOS, provided they're using the SDK and not some awful web wrapper (heck you React Native 
) or provided they haven't switched off the gesture recognizer, then there's a swipe from the left edge of the screen to go back a level. Plus it's a 1-to-1 gesture so it feels a lot more satisfying than the button trigger that the Android gesture does.
The UINavigationController is a stack, so every view you tap into adds a view to the stack and swiping back on it slides it off of the stack. Instead of obfuscating that stack like Android does, it literally makes it a part of the navigational structure. It's intuitive to swipe things off to go back to views you were already on. Plus, breaking it out so going up a level within an app and going back to your previous app are two entirely different buttons/gestures fixes the ambiguity that makes Android so insufferable.
The predictive back button feels like a Band-Aid on something that never should have been a problem in the first place, although I'll admit I don't use it because I don't use the system back gesture. The system back gesture interferes with any application that swipes from the edges of the screen (ie apps that have a hamburger menu or apps that have crop handles like the Photos app), so I have the system back gesture disabled and instead use FNG to cram one down into the bottom third of my phone so it doesn't interfere with apps.
Rusty Corgi
LiquidParasyte