Navigation box, problems with the concept

Question

This is my first question. I would like to know your opinion about the navigation box. I tried some projects and I read a lot about it, but somehow I can’t understand how it works. Here are my reasons / doubts:

• Theoretically, you can go anywhere from your application from anywhere in the world, I mean, this concept forces the designer to work only with Fragments, turning your only activity into a kind of “concept of God”, which is not a good idea for development deep navigation apps.

• If there is a way to combine the navigation box and actions, should I implement the same navigation box again and again at every event? I really do not see this.

I am talking about this because I am trying to adapt one of my applications and use this kind of navigation on it, but I can’t figure out how to do it .. I still think it’s better to have multiple actions and, of course, Snippets on them, but I don’t know how to combine them to get the maximum navigation box performance. I saw similar questions on this site, but I did not find the answer I'm looking for. Maybe I didn’t read the documentation enough, or maybe I'm wrong, and I didn’t understand how this template really works.

Thank you for your help.

Answer 1

You can use the navigation box with active actions.

Just create a BaseActivity class that implements the box,
and let all your other actions expand this one.

Answer 2

A simple reason to use the navigation box: efficiency .

Firstly, the navigation box is not active. This is just a layout that can be easily inserted and out of sight. Of course, this is really a matter of intuitive implementation, so there is no absolute answer to when or when not to use the box. If you feel that the user may be endowed with the privileges of this stream of user interface, then this is worth doing.

If you have a problem with the implementation of the template, you should start with a children's step and learn from official official documents .

Answer 3

There is nothing wrong with the fact that you have one action that contains your navigation box and collapses fragments on time and to the left when you move to the menu drawer. In addition, “moving anywhere” applications from the navigation box should not cause concern if you have good navigation. Good navigation for the navigation box is probably broken down into top-level and detailed views . Your top-level views are groups of content that you are likely to place in your navigation box.

A good example of this is the Google Plus Android app. There is one main action, and the navigation box provides all the top-level views, which are fragments that are replaced and exit the main action. As you further immerse yourself in the content, you get detailed views, which are actions.

Take a look at the official design documentation for the Application Structure and Navigation Box for more information.