From React to Native
summary
Built a working Guardian daily‑edition app as an MVP in six months with a team of three, using React Native and Expo and TypeScript. Performance hits 60fps but real problems appear: long articles in a WebView crush Android, nested FlatList layouts cause blank screens, and platform quirks force per‑OS fixes. Navigation choice (react-navigation vs react-native-navigation) trades performance for customization. Native modules and a device test strategy prove essential; documentation and bespoke layout cases remain painful.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:14SIX MONTHS AGO
- 2:41GETTING STARTED
- 2:59REACT?
- 7:38SPOILERS
- 12:51IMAGES!!
- 13:12use an icon font • use react-native-svg • use bitmaps
- 14:17LIVING WITH REACT NATIVE
- 14:39DEBUGGING
- 15:00ON-DEVICE DEV TOOLS REACT DEV TOOLS CHROME DEVTOOLS
- 16:35NAVIGATION & ROUTING
- 17:27YOUR APP IS A PHYSICAL PLACE
- 19:59react-navigation • react-native-navigation
- 20:28LISTS
- 22:42BROWSERSTACK FOR APPS
- 30:41SHAMELESS PLUG??
related talks
25mReasons to give React Native a(nother) try
31mUsing React Native to ship fast and navigate performance improvements
07mFrom Native to React Native
24mThe Performance Myths of React Native apps
17mDispatches from React Native
24mBuilding Stellar User Experiences with React Native
01h 01mReact Native: A Better Way to Do Mobile
53mHow React-Native shapes the way we think about native apps
