NavigationDrawer with Activities vs. NavigationDrawer with Fragments

Question

Take for example the app I\'m currently working on: - it has an navigationDrawer with multiple items; there are two items which interest me for now, i\'ll call them X and Y

Answer 1

I was in similar boat and I used Activities method, that way I have each Activity with group of fragments for a particular nav click on the NavigationView. Obviously I use NavigationView, but managing all those fragments with just one MainActivity is really a painful task.

I rather prefer EachActivity managing their own fragments when we click a nav item. This gives me a better performance, since I do not need to worry about lifecycle of soo many fragments and it's backStack and add/remove/show/hide hell.

I used the following SO Question to cleverly use a BaseActivity implementing NavigationDrawer, and sharing it with all the other Activities. The real magic is it does not duplicate code, or it's not just plain old Inheritance technique.

Here's the link, do check it out

I used this method in two of my project's and it's running very well plus I do not have to deal with fragment management right from the very start.