Should I use React Native too?

on YouTube ↗28m

" summary

A white‑label React Native e‑commerce app ships from two engineers in six months, shares ~98% code between iOS and Android, and runs 4,000 customer apps in stores with ~12,000 daily users and ~2,000 bookings per day. Uses TypeScript, hot reloading, Jest snapshot tests and Detox for E2E, and Microsoft CodePush for instant over‑the‑air fixes. Main risks are the bridge bottleneck and fragile native upgrades, plus pain around navigation libraries and custom SDK bridging.

AI-written summary · about

" chapters (8)

1. 0:00Introduction and background
2. 3:57The multi-channel challenge
3. 7:52React Native in production
4. 13:12Development speed and hot reloading
5. 18:30Over-the-air updates game changer
6. 20:58Challenges and limitations
7. 23:45Team and prerequisites
8. 27:15Final verdict and conclusion

" related talks

• 45mReact Native: Things we learned the Hard WayGaurav Kaushik · Fragments 2017
• 43mBuilding a React Native App for 80 Million UsersTal Kol · ReactNext 2016
• 07mFrom Native to React NativeGreg Ryzhov · React Day Berlin 2019
• 17mDispatches from React NativeElizabeth Tiller · DevFest Florida 2019
• 51mRapid App Development With React Native: Lessons Learned at NSBErik Wendel · Mobile Era 2018
• 26mReact Native: A Beginner's JourneySimon Reggiani · AndroidTO 2018
• 35mBridging the Gap: How to use React Native in existing large native code basesLeland Richardson · ReactiveConf 2016
• 41mLessons Learned from React NativeGabriel Peal · droidCon NYC 2018