Composable Native APIs
summary
Argues that Cycle.js–style streams plus small drivers layer make native React Native APIs declarative, moving imperative calls (vibrate, toasts, status bar, clipboard, text‑to‑speech) out of lifecycle hooks into singletons that handle bubbled requests. Shows code patterns: components become functions from many streams to many streams, index.android.js wires drivers and is very short, and an alpha decentralized P2P social app is built and running. Benefits demonstrated: composability test, interception, headless testing and bottom‑up design.
AI-written summary · about
chapters (29)
- 0:00Intro
- 0:25React Native
- 2:08What is this talk about
- 3:04Overview
- 3:31Why is react native harder
- 4:51Why should you use react native
- 5:16Nonofficial APIs
- 6:22Imperative Methods
- 6:51Action Creator
- 7:16Components
- 7:51Component Test
- 8:11Component Hierarchy
- 8:48Singletons
- 11:14Benefits
- 12:58Fractals
- 13:54Fractal Architecture
- 14:18Hierarchy
- 16:14Functions
- 18:15Boxes
- 18:54The Benefits
- 19:23Public Tab
- 19:44Sources
- 21:52React Components
- 22:52Index
- 23:10Social Network
- 24:09Streams
- 24:49Declarative
- 25:32Native Threads
- 26:44Conclusion
related talks
27mBuilding high quality mobile apps with React Native
01h 01mReact Native: A Better Way to Do Mobile
45mThe Dark Art of Native APIs
53mHow React-Native shapes the way we think about native apps
25mGoing Native
26mReact Native: Under the Hood
28mThe State of React Native
41mReact Native - A native love story