MVWTF: Demystifying Architecture Patterns
summary
Compares MVC, MVP, MVVM and MVI using a concrete task‑list implementation in Compose with coroutines, StateFlow and Android Architecture Component ViewModel, showing presenter vs viewmodel code, savedInstanceState vs ViewModel retention, and a state‑machine that emits state + side effects to fetch tasks. Claims MVVM is the practical default, MVI adds predictable transitions for many concurrent loads but costs boilerplate, and MVP is fine for quick prototypes or teaching; examples compile and demonstrate working state restoration.
AI-written summary · about
chapters (14)
- 0:00Architecture patterns debate
- 1:04Why patterns matter in Android
- 2:28Problem with Activities
- 3:51What patterns really are
- 4:12Model-View-Controller explained
- 6:59Why MVC failed
- 9:47Model-View-Presenter and its benefits
- 15:48Why MVVM replaced MVP
- 19:21ViewModel vs MVVM
- 21:49MVVM state management issues
- 24:15Introducing Model-View-Intent pattern
- 30:35Comparing patterns
- 32:42Choosing patterns
- 35:10Final advice & Q&A
related talks
43mMVC vs MVP vs MVVM vs MVI
30mArchitecting an app with MVP and ViewModels
41mMVI: a Robust and Modern Architecture
17mApp architecture - singular vs plural
34mArchitectures in the Compose World
41mStateMachine Architecture Based on MVI: Combining KMM, Jetpack Compose and SwiftUI
01h 02mA comparative approach to MVC, MVVM and VIPER: taking the best ideas without fighting against the platform
47mClean app design with Architecture Components