On Mon, Feb 1, 2010 at 1:40 PM, Stormtap Studios <[email protected]>wrote:
> Should I put back > buttons on a navigation bar so the user can stick purely to the > touchscreen? > If you want, that's a UI decision that's up to you. > 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? > Probably this. 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? > Probably, given that's how pretty much every app that has more than one activity works. > 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. > There's a spreadsheet someone shared on here a while back, though I don't have the link handy on this machine. If I remember I'll post back with it. ------------------------------------------------------------------------------------------------- TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- 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
