Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When an application has a single view, the Back button probably resumes whatever previous application was running/suspended. I’m tempted to provide an explicit button which says ‘Back’ right there on the UI …
Should I provide an explicit back button in my view, or should I simply override the navigation button provided by the OS? My gut says the latter would be counter-intuitive. Are there any recommendations on this by the android community?
That entirely depends on your application. Normally, your application is made out of multiple activities (
Activityobjects), and the back button will go to the previous activity.So if your app has a main menu (activity A), which has a button to go to search (activity B), which will lead to search results (activity C), then pressing the back button on the search page gets you back to the main menu. This is fully automatic, you don’t need to write anything for this to work.
That’s how Android works, and that’s how you should write your app. All Android devices have a device button (physical or on-screen, in case of Honeycomb), so don’t waste precious screen real estate on a “back button”. Don’t be like the iPhone.