The Back Button Dilemma • Hacker News Board

Re: The Back Button Dilemma

#21

Post by LukasMathis » Fri, Jul 15, 2011, 5:22 PM UTC

MatthewPhillips wrote: post #17

LukasMathis wrote: post #13

Earlier quoted context omitted.

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.

Re: The Back Button Dilemma

#22

Post by MatthewPhillips » Fri, Jul 15, 2011, 5:42 PM UTC

LukasMathis wrote: post #21

MatthewPhillips wrote: post #17

Earlier quoted context omitted.

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.

Re: The Back Button Dilemma

#23

Post by KevinMS » Fri, Jul 15, 2011, 8:14 PM UTC

Coincidentally, I just finished a rails plugin that does something like this with rails and posted it a few days ago. In this case "back" is determined by a graph of your web app you feed to the plugin. Never managed to get any feedback on it though. However a similar concept has been running on a production site of mine for years with fairly good success; I just finished turning it into a plugin last weekend

http://kswope.com/2011/07/10/backstack-rails-plugin/

Re: The Back Button Dilemma

#24

Post by LukasMathis » Fri, Jul 15, 2011, 8:39 PM UTC

MatthewPhillips wrote: post #22

LukasMathis wrote: post #21

Earlier quoted context omitted.

"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.