Android Architecture Components
summary
Android Architecture Components arrive as a practical MVVM stack: ViewModel objects survive orientation changes and hold UI state, LiveData broadcasts cached values only to active lifecycle owners (so network results survive rotations but can reemit unwanted toasts), and Google supplies sample utilities like NetworkBoundResource (four-method pattern) and SingleLiveEvent to handle offline caching and one-off events. Components interoperate with RxJava and let teams migrate screen-by-screen without rearchitecting an entire app.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:45Android architecture in 2015
- 4:15Naive MVP approach
- 6:22Orientation change problem
- 8:57Loaders to solve lifecycle issues
- 11:51Google’s architecture components
- 13:19ViewModel and LiveData
- 16:13Why use architecture components
- 17:16Shared ViewModel for fragments
- 19:31Single Live Event tip
- 21:21Network bound resources
- 23:10LiveData in model layer
- 25:41LiveData vs RxJava
- 28:52Conclusion and benefits
related talks
38mAndroid Architecture Components
20mArchitecture Components
47mAndroid Architecture Component
44mAndroid Architecture Components, a New Way to Build Apps
44mARCH Components
28mInternals of Android Architecture Components
21mAndroid Achritecture Components Introduction
47mClean app design with Architecture Components