Android Drawer Design

Question

I have an existing application that has about 25 operations that move from the dashboard. I would like to switch and start using the navigation box and fragments. I went through the design pages of Nav Drawer online and an example application. My question is the best way to convert (structure) my application so that it matches the Nav Drawer pattern. If I switch my actions to fragments and use the main action to replace each fragment as the navigation progresses, but I'm not sure if this is good b / c for a tablet tablet, I may need a few fragments in my view and not sure it will limit me. If I go with the other direction that I was thinking about, I continue all my actions and just switch the necessary ones to fragments for tablets, but I would need every action to create a navigation box (I think?), Which in my case the box is dynamically based on server data. Any suggestions would be great.

Thanks Brandon

Answer 1

A navigation box must be created for each action, although you can inherit an Activity and create a parent class that handles the specific code of the navigation box if the problem of duplicate code is a concern.

Using the box does not limit the use of a single fragment on the screen, just listen to onClick in the box and initiate as many fragment transactions as you need.

When it comes to structuring your application, there are no universal tips, I would recommend you watch the Google I / O 2013 Discussion - Structure in the design of Android applications . The navigation box is the main topic of conversation.