MVVM at Scale: Not so Simple
summary
Argues that MVVM can help but often just moves complexity into a single object, shows a small Swift app called Trip Check‑in app that uses Foursquare for place data and native date pickers, moves date‑validation and formatting into testable view models (immutable structs plus a state holder), injects view models into view controllers, uses a coordinator for navigation, avoids reactive dogma, captures business rules in unit tests without UIKit, and warns about value‑type copying and coarse vs granular updates.
AI-written summary · about
chapters (4)
related talks
33mMVVM as good (anti)pattern in iOS
36mMVWTF: Demystifying Architecture Patterns
41mMVI: a Robust and Modern Architecture
19mThe Art of Functional State Management for iOS Apps
17mApp architecture - singular vs plural
30mArchitecting an app with MVP and ViewModels
35mBreaking Up with Big ViewModels
49mDeveloping a clean architecture-inspired React application with MVVM