A comparative approach to MVC, MVVM and VIPER: taking the best ideas without fighting against the platform
summary
Compares MVC, MVVM and VIPER by naming actual tradeoffs and concrete fixes: uses structures for inert models to avoid shared mutable state, moves navigation to coordinators do dependency injection instead of segues, and centralizes shared concerns in explicit shared controllers not singletons. Shows where view models or presenters truly reduce responsibility, warns about rigid VIPER boilerplate, cites slides and course examples, and reports that these approaches are applied in sample projects and student apps with improved testability.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:20THE CULPRIT
- 6:46FIXING MVC (?)
- 9:39MVC'S HIDDEN COMPLEXITY
- 23:52VIPER
- 32:03CENTRALITY OF VIEW CONTROLLERS
- 33:46INERT MODEL TYPES
- 35:06MODEL CONTROLLERS
- 39:05INTERFACE CONTROLLERS
- 40:14LOTUS MVC
