What To Do About Fragments? (en)
summary
Argument for defaulting new screens into fragments with concrete tradeoffs: fragments solve tablet master‑detail, view pager and dialog fragment reuse without duplicating controllers but add lifecycle complexity (extra states, retained fragments) and awkward APIs like commitAllowingStateLoss. Course materials (Big Nerd Ranch 5‑day bootcamp, book exercises rewritten) show fragments enable animations maps and touch examples and are used in-house with good practical results, yet fragment testing and state bugs remain surprising.
AI-written summary · about
chapters (14)
- 0:00Introduction to Android
- 2:00Philosophy of teaching
- 4:29Core android concepts
- 6:07The case for fragments
- 7:20Fragment complexity
- 11:05Solving UI problems
- 14:00Critical necessity
- 15:47Fragments as default
- 19:27Drawbacks and testing
- 22:46Exploring alternatives
- 25:50Building on a baseplate
- 27:45Community and tooling
- 31:55Beginner vs expert
- 33:55Conclusion and Q&A
related talks
30mFragments: What are they good for.
33mFear No Fragments
18mFragments: The good (non-deprecated) parts
56mYou've been told lies about Fragments
46mAndroid Jetpack: How to smartly use fragments in your UI
31mFragments — As Incredible as It Seems
33mBust the Android Fragmentation Myth
46mModern Android: How to ditch Activities and Fragments