Surviving a discontinuous world
summary
Android UI failures stem from concrete discontinuities: background tasks returning to an Activity that was rotated, destroyed, or whose process was killed. Recommended fixes: keep data across rotations with ViewModel + LiveData or retained Fragments and use onSaveInstanceState for destroyed Activities; avoid leaked callbacks with RxJava disposables or cancellation via Kotlin coroutines suspend points; sync list/detail state with startActivityForResult, EventBus, or a local repository; kill process to test lifecycle edge cases.
AI-written summary · about
chapters (7)
- 0:00Discontinuous world in Android
- 4:28Async processing challenges
- 11:24Async processing solutions
- 11:45Screen rotation issues
- 15:55Like button problem
- 23:12State persistence with activities
- 29:06Summary
related talks
45mFalsehoods Android Developers Believe About Lifecycles
34mThe Life and Death of an Android Activity
24mWhere did my State go
39mFrustration-free orientation changes
38mActivities in the Wild: Exploring the Activity Lifecycle
36mManaging Data Restoration with the Architecture Components
23mMaster of Lifecycle
41mViewModels, LiveData and Lifecycles, oh my!