Perhaps the status bar isn't a good solution, but I think there must be some better way of conveying that an activity has a menu other than requiring the user to press the menu icon to see if a menu pops up and hoping the user remembers that the activity has a menu.
For example, the Nexus One has four buttons below the screen: back, menu, home, search. In low light, the buttons are back lit. I don't know if those button lights are individually controlled, but an individually controlled menu button light could make it clear to the user whether or not an activity has a menu. In low light, the menu button light could be turned off when an activity doesn't have a menu. Why should the menu button be lit if the menu doesn't exist? On Jun 21, 9:10 am, TreKing <[email protected]> wrote: > On Sat, Jun 12, 2010 at 2:15 PM, greg <[email protected]> wrote: > > It seems that a menu icon and/or a long click icon in the status bar (i.e., > > along with the battery status icon) would help users know which activities > > have menus and/or views that have long click functionality. > > Not really - especially for context menu items, which can be many for a > given a screen. You'd just pollute the user's task bar for something that > only requires them to figure out once. > > Give your users multiple ways to do things or make it clear how to use your > app from the get go. > > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered > deviceshttp://sites.google.com/site/rezmobileapps/treking -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
