Clean app design with Architecture Components
summary
Shows how Android Architecture Components—Lifecycle, ViewModel, LiveData, Room—slot into an existing clean architecture to solve lifecycle, state and persistence problems. Uses an MVP-style presenter for presentation logic, a ViewModel to persist user state across rotations, LiveData for lifecycle-aware observation, and Room to return LiveData from local cache; long-running network ops continue through config changes and results reattach to the UI. Testing strategy emphasizes fast JVM unit tests plus Robolectric and Espresso. presenter scoped to activity, ViewModel survives config changes
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:56Clean architecture basics
- 6:29Separation of concerns
- 7:56State synchronization
- 8:58Testability and testing pyramid
- 12:07UI architectures overview
- 13:09MVC pattern
- 14:35MVP pattern
- 15:39MVVM pattern
- 17:44Choosing MVP for Android
- 18:26View vs Activity separation
- 20:10Login activity with MVP
- 24:09Android challenges
- 25:11Architecture Components intro
- 26:16Lifecycle and ViewModel
- 29:25ViewModel in presenter
- 30:31LiveData for state
- 31:37Room for persistence
- 33:03Long-running operations
- 34:05Full stack flow
- 35:54Resources and wrap-up
related talks
47mClean app design with Architecture Components
30mClean App Design with Architecture Components
44mAndroid Architecture Components, a New Way to Build Apps
40mI Wrote an App Using Architecture Components… And Here’s How It Turned Out
28mHands-on Android Architecture & Architecture Components
42mTestable Android Architecture
38mAndroid Architecture Components
47mAndroid Architecture Component