Redux for Android
summary
Argues that adopting Redux on Android centralizes user state into a single store, makes data flow unidirectional, and dramatically improves testability and debuggability; uses Kotlin with ReKotlin, ViewModel + LiveData as the presentation bridge, reducers and middleware for async work, and a custom reducible interface to keep action+reducer code together; notes deep-copying nested state is a real pain, migration took 2–3 months, and the architecture proves useful in production.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:13Why not Redux always
- 2:39Dosh architecture goals
- 8:55Redux core concept
- 10:42Redux architecture deep dive
- 12:27App state modeling
- 14:56Actions and reducers
- 19:29Presentation layer
- 21:56Middleware explained
- 26:28Benefits of Redux
- 27:54Q&A session
related talks
37mRedux on Android, the nitty gritty
45mExploring the possibilities of Unidirectional Data Flow Architectures on Android (en)
15mRedux Architecture in iOS
15mRedux is dead, long live redux!
47mCross-Platform Redux and SwiftUI / Jetpack Compose
51mBuilding React Applications with Redux
51mRedux, beyond React
31mArchitecture metamorphosis: a real case study