On Jun 30, 1:09 pm, TreKing <[email protected]> wrote: > On Sun, Jun 27, 2010 at 1:50 PM, Lance Nanek <[email protected]> wrote: > > Often it is pretty easy to add a button to your app's screen that opens the > > menu and also lets users know it is available just by being there, at least. > > Sure it's easy - and also a major waste of limit screen space for a one-time > function. > > I get your point about some people not realizing functionality is there, but > again, it's a one-time learning experience that really doesn't justify a > dedicated button or whatever, IMO. > > The skipping entries in the ADC2 app, for example, was just poorly > implemented - that should have been a dedicated button with the frequency in > which it was going to be used. > > Use a "quick start" dialog on the user's first run to let them know this > exists, or Toast messages as "Tips" as they navigate the screens perhaps. >
Even with a Toast tip, the user must still remember whether or not the menu exists, which indeed is a trivial task for a single activity but not so trivial when there are a hundred activities. If the presentation of icons that don't do anything is trivially handled by one time learning experiences, perhaps the application launcher should not bother to remove the icons of deleted applications. :*) -- 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
