Riding the state flow
summary
Argues a concrete MVVM recipe: model UI as immutable state and events, dispatch actions as Kotlin suspending functions backed by a coroutine actor and Flow, test by asserting a sequence of emitted states, and favor functional error handling with Arrow Either. Uses Uniflow and Kotlin coroutines, keeps common IO work off the main thread 95% of the time, and claims a small implementation surface — roughly five classes — rather than a reducer/store explosion.
AI-written summary · about
chapters (11)
- 0:00Traditional architecture issues
- 2:27Moving to MVP and MVVM
- 5:54Unidirectional data flow
- 10:49Simplifying state and events
- 13:48Implementing UDF in practice
- 20:25Error handling and binding
- 24:21Testing the architecture
- 27:02State guarding and complexity
- 32:48Shared view models and flows
- 37:32Functional programming and conclusion
- 41:25Q&A session
