Exploring the possibilities of Unidirectional Data Flow Architectures on Android (en)
summary
Claims that unidirectional data flow yields time-travel debugging and deterministic bug replay, demonstrated with Redux/Elm/Cycle patterns and a small Java/Kotlin Android library. Demos include a counter and to‑do app plus a dev drawer that replays and disables actions; async work runs outside reducers; views are naively replaced (not diffed). Benefits: pure reducers, easier unit testing, composable components. Caveats: experimental, not production ready, concerns about memory footprint and UI rendering speed and unresolved hot‑reload integration.
AI-written summary · about
chapters (38)
- 0:00Introduction
- 1:15Disclaimer
- 2:18The problem
- 2:55Debuggers
- 3:20Redux
- 3:54OnTheRise
- 4:56Developer Experience
- 5:29Unidirectional Data Flow
- 7:07State
- 8:00App
- 8:23Layout
- 8:39MainActivity
- 9:38Plan
- 10:37Radix
- 10:49Update Function
- 11:59Updating Main Activity
- 14:00Cutting Code
- 14:55reducer
- 15:45time travel
- 16:47testing
- 17:53Elm
- 18:35Elm Architecture
- 23:04Contour Component
- 24:41Nesting Components
- 25:00Moving Components
- 25:28Views Become Testable
- 27:21Cycle
- 29:05Code
- 32:49Complexity
- 33:14Cycles
- 35:01Recap
- 35:19Demo
- 38:51Wrapping up
- 39:26Benefits
- 40:28Other interesting possibilities
- 42:55Lets have some fun
- 43:11And see
- 43:37Questions
