5 ms·
The Reality Distortion Field is strong in this one. So if I understand what you're saying, android's back button causes users to randomly mash buttons in froth
by tmuir 14y ago
The Reality Distortion Field is strong in this one. So if I understand what you're saying, android's back button causes users to randomly mash buttons in frothy fits of delirium, yet iOS's back button provides zen like enlightenment and happy endings.
Pushing the back button on an android phone, by default ALWAYS goes to the previous activity, or cancels context menus. Of course, it's possible to make the android back button do something else with the onPause method, just as it's possible to make that happen in the viewDidUnload method in iOS.
The dropbox and imdb android apps use tabs perfectly well.
Countless android apps use listviews to navigate.
- CubicleNinjas 14y agoThe point is consistency versus relative consistency.
- andrewljohnson 14y agoI'm actually not biased one way or another - we make apps for both, and I carry a Nexus and an iPhone wherever I go. But it's simple truth: * The iPhone back button always takes you to one, and exactly one, screen. * The Android back button can take you to many different screens, based on where you last were. That's a gigantic difference, and leads to the button-mashing I describe.
- nazar 14y agoBut when pressing some UI element gets you to other apps like browser, facebook etc, that Android back button behavior is what makes my life easier.
- joesb 14y ago> Pushing the back button on an android phone, by default ALWAYS goes to the previous activity. Good if it is the only apps you are using. But what if you switch to use others app for a while and switch back to this app. Can you remember the activity stack as of all the apps good as the OS does? Can you predict where back button is going to take you after not using the phone for half an hours?
- bergie 14y agoSo, you don't like the back button in browsers either? The Android back button does the same, but for the whole OS.