Redux on Android, the nitty gritty
summary
Argues Redux is practical on Android for state-driven features and can be used as a subcomponent, not an all-or-nothing rewrite, with reducers as pure functions so unit tests stay trivial and predictable. Uses Kotlin data classes and the built-in copy() shallow copy to keep immutability and avoid huge GC spikes. Describes tradeoffs between middleware vs action creators, common pitfalls (infinite dispatch loops, async dispatch scrambling call stacks), and cites libraries (Evan Totara’s Redux, Recottlin) and a Pusher blog post.
AI-written summary · about
chapters (16)
- 0:00Introduction and motivation
- 3:05App architecture basics
- 6:35Unidirectional data flow
- 7:41Redux principles explained
- 9:05State modeling in Redux
- 12:16Immutable state updates
- 13:21Global state scope
- 15:07Actions and their role
- 17:11Pure functions and reducers
- 20:01The Redux store
- 22:52Common dispatching pitfalls
- 25:21Handling side effects
- 26:26Action creators vs middleware
- 28:56Middleware chain explained
- 30:42Redux challenges and trade-offs
- 33:32Final thoughts and resources
related talks
38mRedux for Android
45mExploring the possibilities of Unidirectional Data Flow Architectures on Android (en)
15mRedux is dead, long live redux!
25mRedux is dead, long live Redux!
33mReduxKotlin.org: Redux for All Kotlin platforms
42mRedux-ing like a Pro
15mRedux Architecture in iOS
44mThe Fundamentals of Redux