On Jan 27, 3:20 pm, Matt Kanninen <[email protected]> wrote: > We are teaching users to always check the menu button. Some > developers don't use it, but that is not a Framework or a User error, > it is a Developer error.
That reminds me of the standard UI designer's joke: "Let me explain to you why this is intuitive!" If you have to explain it, then it's not intuitive, and if you have to teach users to do something, then it's not intuitive. And even if you teach them, why should they have to take the trouble to check whether a menu's available? Why can't we just tell them? (Answer: There's no reason we can't, and we should.) > Home means clear the stack. Back should do nothing after you clear > the stack. What does home mean to you? If you want similar > functionality to Home without clearing the stack you can long press > the home. I understand that's what it means, but only because I've read the developer documentation. The problem is that it isn't what users expect it to mean. In a web browser, Home means, "Take me to my home page," and Back means, "Take me back to where I was before." Long pressing the Home button has exactly the same problem. I'm working in application A. Then I switch to application B. Then I press Back and it takes me to... the home screen??? Peter -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
