Falsehoods Android Developers Believe About Lifecycles
summary
Covers concrete lifecycle failures: orientation and multi-window aren't the only triggers for activity recreation, configChanges cannot stop all restarts, and process death by LMKD or permission revocation kills the process with no callbacks. Recommends ViewModel + SavedStateHandle or onSaveInstanceState, warns about the 1 MB binder transaction limit for Bundles (Google advises <50 KB), explains splash/init and backup edge cases, suggests testing with the Venom tool, Android Studio process-stop, and developer options.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:22Configuration Change
- 10:00Night Mode
- 13:41The Low Memory Killer Demon
- 15:30Four Stop Button
- 16:50The Saved State Library
- 24:59Use Fragment Arguments
- 27:14Binder Transaction Limit
- 30:40Retry Buttons
- 31:09Dialog Fragments
- 38:14Show Allowing State Loss
- 42:06Webview
- 44:03Test Your App
related talks
38mActivities in the Wild: Exploring the Activity Lifecycle
23mMaster of Lifecycle
30mSurviving a discontinuous world
34mThe Life and Death of an Android Activity
24mWhere did my State go
50mBirth, Life and Death, or What Happens to an App in the System
39mFrustration-free orientation changes
36mLifecycle for Android Developers