All right.  I brought this up a few weeks ago on this list and some of the 
advice on the topic was to avoid menus entirely and replace them with 
in-app soft-menus from now on...despite the action bar.  I guess that 
advice was incorrect.

Thanks for the clarification.

On Thursday, November 1, 2012 10:42:21 PM UTC-7, Nirav Parmar wrote:
>
> "My understanding is that modern Android "best practice" is to not use the 
> system-level menu button or system-level options menu anymore since such 
> buttons are frequently difficult to access or even absent on some devices." 
>
> >> Keith , Your understanding is wrong here. Read about ActionBar. 
> http://developer.android.com/design/patterns/actionbar.html
> you can use that..Also, if device have hardware buttons(menu buttons) 
> Action Overlay will not display in Action bar otherwise you will get Action 
> Overlay..so all your functionality can be now placed in Action bar (which 
> we used to put in menu previously)
>
> "What I'm not sure about is whether I can still rely on the standard 
> 'back' button or whether I need to add such functionality to my UI (add a 
> soft button on my screen) on the concern that some devices may not present 
> a usable back button to the user."
>
> >> Again, that's not true.Each Android device will come up with standard 
> back button..This is how Android OS is designed..any device doesn't have 
> hardware buttons..Android OS will display Back ,Recent and Home buttons on 
> screen at bottom.
>
> >>Also, According to Android's new Design & Navigation pattern, UP button 
> is added.You can show UP button in Action Bar(Which can be used for 
> Application nevigation)
>
> Read Here , http://developer.android.com/design/patterns/navigation.html 
> .This 
> will clear you doubts.
>
> Thanks & Regards,
>
> Nirav.
>
>
>
> On Fri, Nov 2, 2012 at 10:41 AM, Keith Wiley <kbw...@gmail.com<javascript:>
> > wrote:
>
>> My understanding is that modern Android "best practice" is to not use the 
>> system-level menu button or system-level options menu anymore since such 
>> buttons are frequently difficult to access or even absent on some devices.  
>> I have gutted all menu access from my app as a result (I admit, it is quite 
>> tedious to get access to the menus on some devices since you have to tap at 
>> least once just to get a menu bar to appear and then again on a menu icon 
>> to get the menu...and I'm not sure even that approach works on all of the 
>> most modern devices).
>>
>> What I'm not sure about is whether I can still rely on the standard 
>> 'back' button or whether I need to add such functionality to my UI (add a 
>> soft button on my screen) on the concern that some devices may not present 
>> a usable back button to the user.
>>
>> Any thoughts on this subject?
>>
>>
>> Thanks & Regards,
> Nirav
>
>  

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to