Note that there are some explanatory texts on larger screens.

plurals
  1. PONavigation Drawer Menu on Android 2.X - Small Screens
    primarykey
    data
    text
    <p>I have recently coded an application and included a DrawerLayout with the <a href="http://developer.android.com/design/patterns/navigation-drawer.html" rel="nofollow">Navigation Drawer</a> pattern. This application must support ldpi/small devices and android version 2.1+ for market share reasons.</p> <p>One user made an observation about the Drawer Menu icon looking 'cut' and the app being hard to navigate because of this. I guess this is expected, considering that all mayor apps (Twitter, Instagram, Gmail, etc) haven't updated the app for this kind of devices. Though, they are using this pattern for newer/bigger devices/platforms.</p> <p>Considering that the DrawerLayout has been included in the support library, i would expect apps to start backporting it to 2.X sooner or later. Maybe big players haven't done it because <strike>Google officially deprecated LDPI</strike> ldpi/small devices are rare nowadays and <a href="https://code.google.com/p/android-ui-utils/issues/detail?id=175" rel="nofollow">even unsupported for some community tools</a>, but what would be the right thing to do in order for the app to be successful in this matter? Is there any guideline to follow on this topic? If you have to support ldpi/small and 2.X, would you go with a drawer navigation menu? why?</p> <p>Thanks for your comments.</p> <p>[Edit]</p> <p>Went too far, for some reasons i thought Google actually deprecated LDPI/small, but it was just some community tools/libs that i've seen around that actually did it. Even the ADT template doesn't generate the drawables for LDPI/small. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload