Clean app design with Architecture Components
summary
Shows a concrete migration: keep an MVP passive‑view presenter as pure display logic, add a ViewModel to hold UI state that survives configuration changes so the presenter is stateless, wrap state in LiveData so the presenter observes updates, and use Room for local storage that can return LiveData directly. Demonstrates a simple login app that survives rotation, reduces Android dependencies for unit tests, and lets components be introduced incrementally without a full rewrite.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:49Clean architecture goals
- 13:16MVC MVP MVVM comparison
- 21:46Passive view in Android
- 27:26Android challenges
- 28:30Architecture Components intro
- 30:58Lifecycle owners and observers
- 33:27ViewModel integration
- 35:57LiveData for state
- 36:59Room database wrapper
- 38:45Final architecture breakdown
- 39:50Future of Android development
- 42:14Q&A
related talks
39mClean app design with Architecture Components
30mClean App Design with Architecture Components
44mAndroid Architecture Components, a New Way to Build Apps
38mAndroid Architecture Components
40mI Wrote an App Using Architecture Components… And Here’s How It Turned Out
31mAndroid Architecture Components
28mHands-on Android Architecture & Architecture Components
41mViewModels, LiveData and Lifecycles, oh my!