Hacker News Reader

Comment by zyb09 | Hacker News Reader

I think this is only a problem for people not familiar with Android. Once you get used to it, it's pretty straightforward and intuitive. Fact is, the back button always takes you back to the previous screen you where on, and it works systemwide. So when you opened an email from a notification, you get taken back from wherever you opened that notification. Yes, apps can mess with that behavior, but only bad apps do and those don't get used anyway. iOS navigation stacks work very differently, so this might be confusing for people coming from iOS.

View on HN

It's not that the behavior is unclear, it's that going back is not always what you want to happen.

Sometimes, you jump directly into an app, but then, you want to do other things inside that app; since the back button normally is used to move up inside an app, it's not always obvious how to do that (and it's sometimes not possible at all).

It actually doesn't move up. It always moves back, just like the back button on the browser. If you want to move "up" that is handled by the developer's UI preferences.

Android doesn't know what the correct "up" activity would even be. Unless they've changed that in 3.0, I have only used the 2.2 and 2.3 sdks.

"Back" is normally used to move "up" because most of the time, "back" and "up" are the same thing.

Possibly true, but users don't expect the back button to move up, they expect it to move back. In the web browser if you click on a link from HN and then hit back you don't expect the browser to direct you to the parent domain, you expect it to return to HN.

The web browser is a different case than something like the Gmail app, or the Kindle app.

I'm not too familiar with iOS, but may it be that iOS is emphasizing a "silo" view of apps (where you consistently stay within one app until you "escape" to the root), which Android deemphasizes the app in particular, in favor of a more unified feel?

Reply on news.ycombinator.com