Think Your React Native App Can’t Run on the Web? Think Again!
summary
A production e‑commerce React Native app is ported to the web using React Native Web with a Next.js website, Solito for unified routing, a monorepo (Nx), styled‑components, Lottie, and TanStack Query; migration takes about 12 months, not because tech fails but because of product cruft. The org keeps 7,000 LOC with only ~175 platform‑specific lines and 24 web files out of 312, the RNW bundle is ~70KB, SSR with Redux Toolkit proves impractical, and the cross‑platform release hits 4.9 stars.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 7:27React Native Web
- 11:39React Native across platforms
- 12:00Proof of concept setup
- 15:52Next.js integration
- 18:00Screen navigation challenges
- 22:15Styling and animations
- 23:19Platform-specific features
- 24:48State management and SSR
- 26:56Proof of concept results
- 28:43Platform-specific code
- 30:09Performance optimizations
- 31:56Monorepo challenges
- 32:58Migration worth it
- 33:40Q&A
related talks
28mWait, you’re shipping React Native to the web?!
46mReact Native for Web Panel Discussion
28mCross-Platform React
27mReact Native: From pure Web app to a Web & Mobile hybrid
28mShould I use React Native too?
14mBeyond Mobile: Taking Your React Native App to Desktop and Web
34mMonorepo: React Web & React Native
35mMigration Web (Angular) to Mobile Development (React Native)