You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider an Activity with a NavigationDrawer and a list of fragments. Using the drawer I can navigate to each fragment but in order to build a responsive and powerful application I have to :
Manage transitions between fragments
Do not instantiate every time a fragment but use an existing one if possible
Manage fragment state and its data
Working with AppCompatActivity and OptionsMenu (Backpressed & Toolbar back button/Title)
Perform an Android application working with fragments implies to manage a lot of things.
Would be great to have a guide for this.
I'm not asking for a sample, but for a documentation who explain how to implement this as best as possible.
Improve the NavigationDrawer part with these cases could be great.
The text was updated successfully, but these errors were encountered:
(It's dangerous to keep references to fragments since they have their own lifecycle (i.e. if you hold onto a reference and replace a fragment with another, that old reference may cause memory leaks -- so you have to choose between show vs hide...
Fragment states & data --> I am starting to be of the opinion they are better managed as singleton instances via Dagger than trying to use Icepick to store them (does anyone else have opinions?)
Consider an Activity with a NavigationDrawer and a list of fragments. Using the drawer I can navigate to each fragment but in order to build a responsive and powerful application I have to :
AppCompatActivity
andOptionsMenu
(Backpressed & Toolbar back button/Title)Perform an Android application working with fragments implies to manage a lot of things.
Would be great to have a guide for this.
I'm not asking for a sample, but for a documentation who explain how to implement this as best as possible.
Improve the NavigationDrawer part with these cases could be great.
The text was updated successfully, but these errors were encountered: