Cross-Platform React
summary
Claim: shipping features becomes faster by sharing front-end code between web and native. Team uses React Native, wraps state and API logic so 60% reusable (reducers, selectors, API calls), but UI components are mostly not reusable and connects need refactoring for performance. Built a full native replacement, moved a shared core into one repo, and experiments with react native web and storybook prove web works well enough for 1% of users. Conclusion: prefer a mono repo and accept maintenance tradeoffs.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:57Why transition Or how to sell this to your boss
- 4:14React native in a few minutes
- 5:11What happens with components?
- 8:40Higher order components
- 10:19Styling
- 12:10Business logic
- 13:55Redux
- 16:51Sharing is caring
- 19:20What about the web?
- 21:33React native web
- 27:01Summary
related talks
21mBuilding Cross-Platform Component Libraries for Web and Native with React
34mMonorepo: React Web & React Native
46mReact Native for Web Panel Discussion
11mCross Platform React
25mGoing Native
34mMonorepo: React Web & React Native
27mReact Native: From pure Web app to a Web & Mobile hybrid
16mBuilding Cross-Platform Apps with React Native + Next.js