React Native for Web Panel Discussion
summary
Companies report real results: a major marketplace migrates parts of its site to React Native Web years ago and sees faster feature delivery, one media app reuses 90% code reuse across web, iOS and Android, and teams build a custom design system (Flipkart DLS) plus component libraries. Key tools and fixes: react-native-web 0.18 supports className, a PR adds gap to Yoga and RN, Next.js + Expo monorepos are common, and Metro lazy bundle loading (microfrontends) is imminent. Remaining blockers: layout divergence, web-only CSS features, accessibility mapping and animation bundle size.
AI-written summary · about
chapters (19)
- 0:00Introduction and panel setup
- 4:50Flipkart’s React Native Web migration
- 7:01Flipkart’s design system journey
- 8:23Early React Native Web experiences
- 10:52Design system philosophy
- 11:55Layout differences across platforms
- 12:19Showtime’s React Native Web insights
- 14:27Accessibility across platforms
- 15:51Glue Stack’s universal components
- 19:03Monorepo and codebase management
- 20:49Choosing React Native Web parameters
- 23:39Webpack Module Federation discussion
- 25:25React Native Web challenges
- 29:15Platform-specific UI implementations
- 33:36Animations in React Native apps
- 37:16Skia Library for complex graphics
- 38:19Audience Q&A and wrap-up
- 39:06New React Native architecture
- 40:34Future of React Native Web
related talks
28mCross-Platform React
42mReact Native Panel & Q&A
38mThink Your React Native App Can’t Run on the Web? Think Again!
28mWait, you’re shipping React Native to the web?!
34mMonorepo: React Web & React Native
35mMigration Web (Angular) to Mobile Development (React Native)
57mReact Native Panel hosted
01h 01mReact Native: A Better Way to Do Mobile