Google I/O 2013 - Structure in Android App Design
Why Stack Overflow recommends it
Stack Overflow users link it when answering Android navigation drawer and app-structure questions, since it is the official Google guidance on choosing navigation patterns.
Recommended by 1 people across 1 different months, 2013 to 2014.
What it is
A 2013 Google I/O session by Android design team members Jens Nagel and Richard Fulcher on organizing a growing app's navigation. It compares patterns such as spinners, tabs and the navigation drawer and explains how to make an app predictable and pleasant to use.
What people said
Recommends Martin · 2013-05 · Stack Overflow · on “Android Navigation Drawer Design”
Navigation drawer has to be created for each activity, although you could inherit Activity and create a parent class that handles navigation drawer specific code if code duplication is a concern. Using a drawer does not limit you to use one fragment per screen, just listen to onClick in drawer and initiate as many fragment transactions as you need. When it comes to structuring your app, there is no universal advice, I would recommend you to watch Google I/O 2013 talk - Structure in Android App Design [this video] . Navigation Drawer is kind of the main theme of the talk.
Cites iamreptar · 2013-11 · Stack Overflow · on “Android layout with navigation drawer”
Technically, you shouldn't use ActionBar tabs with the NavigationDrawer: "You shouldn't use navigation drawers with action bar tabs. If you're aiming for a UI similar to that of Google Play Music, you should implement tabs manually (and beware of how this looks on tablet—you don't want full-width tab bars on tablets). Also make sure to check out the Structure in Android App Design [this video] session from this year's Google I/O for a detailed run-through of the various interface patterns available for exposing app hierarchy." - Roman Nurik, Android Developer Advocate @ Google [LINK] Using FragmentTransaction [LINK] in the Activity that inflates Main.xml : FragmentTransaction fragmentTransaction
Cites Nic Hubbard · 2014-08 · Stack Overflow · on “Managing multiple hierarchies using Fragment Manager and DrawerLayout”
I have an app that is using a DrawerLayout and each item in the drawer will load a Fragment . The structure looks like: News -> News Story Photos -> Gallery -> Photo Events -> Event Directory -> User Type -> User Profile Each top level is an item in the Drawer , tapping one will take you to that fragment and you can go deeper into that section by adding additional fragments on the stack, e.g. navigating from Photos to a Gallery to a photo in that gallery. It gets confusing when I need to manage the navigation of each of these sections as individual stacks. On iOS I would use a UINavigationController for each section so that I could manage either separately. But on Android I am not sure how t