Composing Magic with MVI and Kotlin StateFlow
summary
A sample app shows two composables (word list and add-word) that swap for navigation, using Room + Retrofit + Coil and Dagger Hilt for DI. MVI replaces MVVM with a hot Kotlin Channel for UI intents that is consumed as a Flow, a reducer that copies previous state into a new immutable state, and a MutableStateFlow that holds the current view state. Compose constraints move buttons for possible motion layouts, coroutines handle threading, and the repo and slides live on the 360/dev branch.
AI-written summary · about
chapters (6)
related talks
29mModern Android Development using MVI architecture
43mHelp! ViewModel
34mArchitectures in the Compose World
36mCoroutine + Flow = MVI
49mRiding the state flow
33mFlowing Things, not so strange in the MVI world
37mFlowing Things, Not So Strange in the MVI World
39mSimple MVI: A LiveData Based MVI Approach