The State of One Codebase For All The Platforms
summary
Compares two real strategies: a paint-to-pixels engine (Flutter/Skia style) that guarantees visual consistency but breaks accessibility and native patterns, and a native widget mapping (React Native/Xamarin) that leverages platform accessibility but struggles with consistency. Calls out concrete problems—navigation state vs web routing, screen-reader APIs, gestures, native modules, and build outputs—and lists practical tools and wins: react-native-web, Solito navigation sharing, Expo native modules and EAS builds, React Aria / React Native Aria, Reanimated and Tamagui.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:04Platform approaches
- 3:24Native widgets and challenges
- 5:06UI, navigation, and gestures
- 7:55React ecosystem for cross-platform
- 9:06Universal UI libraries
- 10:40Native base and component systems
- 12:17Navigation solutions
- 14:16Accessibility and hooks
- 17:02Animations and gestures
- 19:00Native modules and build systems
- 20:23Future and conclusion
related talks
59mOne Codebase to Rule Them All - Using React Native Everywhere
39mWorking Across Platforms
30mJesse Weigel - One Codebase to Rule Them All - Using React Native Everywhere
47mReact Native code reuse: Architecture that works
45mMobile navigation
25mDon't Just React, Mobilize
28mCross-Platform React
21mNative, React Native, Flutter and More