| > Also, you can’t tell what the back button will do - is it going to close the app or go back? I've yet to encounter a single app that “closes” when pressing the back button… > or one gesture that takes you home and one gesture to take you back. And while gestures are ok in terms of UX, they aren't discoverable at all, hence my argument about bigger barrier to entry for beginner with iOS. > That’s also part of the reason why Apple wants to keep it as a walled garden. Nope, the reason is a mix of company's culture and profit motive. Since job's death Apple has largely departed from its former design consistency obsession. > Once you deep dive, they might be about the same but Apple still has the consistency advantage. The consistency advantage Apple has only exist compared to different Android phones (jumping from one Android brand/OS version to another is generally confusing), but it only matters when you change phones, and people have refrained to upgrade their iPhones to newer iOS version for years now so jumping to a new iPhone also come with a feeling of confusion if you were used to a former iOS version. As I said before, most of what you're talking about doesn't really exist except on Apple's marketing and fanbase mind. |
Here is how to reproduce: Tap back button until the app closes.
Oh you will say that the app didn't close, it went into the background? Maybe, maybe not - users can't tell without further investigation.
This alone makes it 10x harder to use than iPhone. On iPhone, there's no concept of closing the app. Well, there's but its not a relevant thing %99 of the time because apps are very limited on what they can do in the background and its very obvious if the are doing something(you see controls on the screen because they will have to use some system service like playing audio).