Hello folks, I'm porting an iPhone app to the Android OS. The iPhone app is based on the iPhone navigation controller template, the principal component of this being the large navigation bar at the top of the screen. For those who don't know the iPhone SDK, the navigation bar tracks the user's location in the hierarchy of information presented by the application, and establishes a "stack" of views. When I click on an item on the current view I can push a new view onto the stack, this automatically places a back button on the navigation bar that would pop the current view off the stack and bring my back to the previous view.
I don't see an equivalent widget or API to this in the Android SDK, so I'll have to implement something similar on my own if I want to maintain the same style of navigation. What I am trying to figure out is how I should manage control of the stack. Should I put back buttons on a navigation bar so the user can stick purely to the touchscreen? Or should I make use of the back button on android phones and leave more space for the title of the current screen on the bar at the top? Can anyone comment on this? Is it safe to rely on the presence of the back button for all devices the app may be running on? Or do some phones not even have a physical back button? Any links explaining the hardware differences between all the android devices would be helpful here if someone can share. Thanks! Robert Hawkey Stormtap Studios -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
