Netflix's Reactive Android Components - The Redux Revenge.
summary
Built two native apps (Android in Kotlin, iOS in Swift) in three months with four engineers, using GraphQL for fetching and quicktype to generate identical models; architecture mixes Redux with componentized UI so every widget exposes a single render method and subscribes to a global store. Components transform the global state to local state to avoid unnecessary re-renders, lifecycle ties use Jetpack ViewModel to avoid leaks, RecyclerView uses a custom adapter that diffs in background, and testing instantiates components and calls render to hit ~60% coverage. unidirectional data flow render(state) single-method components multi-platform by architecture
AI-written summary · about
chapters (13)
- 0:00Introduction and Netflix context
- 4:30Multi-platform by architecture
- 7:41Red Components architecture overview
- 10:08Fragments and UI component separation
- 12:34Component state and render method
- 15:48Layout approaches for components
- 16:52Redux store and render loop
- 19:22Optimizing render loop performance
- 21:07Components in RecyclerView lists
- 25:18Navigation components with Redux
- 27:49Unit testing components and Redux
- 31:43Recap and key takeaways
- 33:50Q&A and resources
related talks
39mNetflix's componentization architecture with RxJava + Kotlin - Part II
35mcomponentization architecture with RxJava + Kotlin
37mRedux on Android, the nitty gritty
47mCross-Platform Redux and SwiftUI / Jetpack Compose
25mGoing Native
04mBuilding Applications for a Studio in the Cloud at Netflix
34mFrom zero to app in six weeks
55mReact: Not Just a Popular Library