React Native is the new black
summary
Argues React Native replaces Objective‑C/Java/Swift for many apps, citing a real team at magnets who built their app from scratch using only JavaScript and hot reloading, with performance benchmarks showing GPU/CPU close to native and Maps even faster. Explains using platform-specific .js files (iOS.js / Android.js), native modules for BLE, and when native code became necessary for a custom swiper animation that took days. Notes pain points: heavy debugger memory use, slow repo maintenance, navigation quirks. Recommends RN for small teams, fast delivery, and non‑animation‑intensive apps; go native for complex animations, high‑performance or large teams.
AI-written summary · about
chapters (24)
- 0:00Introduction to React Native
- 1:16What is React Native
- 3:07Pros and cons overview
- 4:12Cross-platform differences
- 5:19Sharing logic with web apps
- 6:03Performance comparison
- 7:56JavaScript advantage
- 8:38Hot reloading benefits
- 9:00Ease of learning
- 9:44Debugging challenges
- 10:26Complex animations struggle
- 11:53React Native limitations
- 13:19JavaScript quirks
- 14:10Tooling complexity
- 15:11Facebook maintenance issues
- 16:35When to choose React Native
- 18:01Animation complexity
- 18:47Fast development cases
- 19:31Small teams and startups
- 20:37Existing apps migration
- 21:22Big companies and games
- 22:53Learning resources
- 23:37Tips for using React Native
- 24:26Q&A Bluetooth Low Energy
related talks
01h 01mReact Native: A Better Way to Do Mobile
52mWhy you should use React Native for your next mobile app
54mReact Native Better Than Native
29mWhen “Good Enough” - Just Isn’t Good Enough
31man iOS Developer's Opinion of React Native
31mReact Native in 40 minutes
10mReact Native, your UX superhero
27mBuilding high quality mobile apps with React Native