Fragments: What are they good for.
summary
Fragments claim to let you reuse UI components across Activities, ViewPagers and navigation drawers while hiding a hairy lifecycle; the details matter: use the support library fragments (updated ~three to four times a year) for child fragments and features, prefer FragmentStatePagerAdapter for memory-sensitive ViewPagers, show dialogs with show(fragmentManager, tag), and treat tablets with a master/detail layout. Practical limits and rules surface — max three fragments per activity (five for tabbed layouts), headless fragments do background work but are usually not worth the pain.
AI-written summary · about
chapters (4)
related talks
37mWhat To Do About Fragments? (en)
18mFragments: The good (non-deprecated) parts
46mAndroid Jetpack: How to smartly use fragments in your UI
56mYou've been told lies about Fragments
33mFear No Fragments
31mFragments — As Incredible as It Seems
46mModern Android: How to ditch Activities and Fragments
39mACTIVITIES AND FRAGMENTS ARE NOT MVX VIEWS