Chopping Expo up into universal modules to take over the world
summary
Expo SDK is refactored from a monolith into separate native + JS libraries so apps can opt out of unused APIs and plain React Native projects can import individual pieces. Implementation defines four module types — internal modules, exported modules, singleton modules, and view managers — wired by a module registry and platform adapters (React Native adapter implemented; Flutter adapter planned). 19 APIs are already extracted. Builds shrink and customization improves, but linking is manual, JS→native adds an extra proxy hop, and tool support is still missing.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:49Expo
- 3:14Expo Decay
- 5:05Implementation
- 10:51Module Registry
- 12:32React Native Adapter
- 13:45Proxy
- 14:35Advantages and disadvantages
- 16:59Whats next
- 18:09Outro
related talks
22mReact Standard Library
53mWhat's next for React Native and Expo
16mSome breaking news from RN world
25mLimitless App Development with Expo and React Native
42mPanel Discussion
26mIntroduction to Cross‑Platform Development with React Native and Expo
23mReact Native Or Expo? Both.
19mExponent: A React Native development tool