The Art of Functional State Management
summary
Argues that immutable state plus reactive streams make iOS state predictable and testable, demonstrates concrete code: a counter and a user‑profile fetch implemented with Combine publishers (CurrentValueSubject, map, assign, sink, stored in Cancellables) and with async/await for simpler single‑response flows. Shows that Observation macro on iOS 17 replaces Published/ObservableObject with two lines and per‑property notifications, reducing boilerplate, and notes tradeoffs: compilation/runtime portability and initial learning curve. Examples compile and the counter and network examples work as shown.
AI-written summary · about
chapters (10)
- 0:00Introduction to state management
- 1:49Core principles of functional programming
- 6:05Swift and functional programming
- 6:27Reactive programming explained
- 9:40Combine framework overview
- 13:08Traditional MVVM vs Combine
- 14:52User profile with network request
- 17:43Combine vs async/await
- 20:54Observation framework comparison
- 25:46Key takeaways and recap
related talks
19mThe Art of Functional State Management for iOS Apps
34mThe Art of Functional State Management
35mWhy "The Composable Architecture" Matters for iOS App Development
40mFunctional iOS Architecture in the SwiftUI Era
45mArchitectural Thinking on Flutter State Management
44mState Management in Flutter
27mPut it All in State
43mGood Intentions II: Enemy of the State