Dispatches from React Native
summary
React Native delivers 90% in JavaScript for a big Cisco food‑supplier app meant to replace a legacy client that handles roughly $4.14 billion in revenue but Android requires extra work. Teams detach from detached Expo to write custom Java/Android modules, use react native device detection for styling, and fight JSX null‑safety, short‑circuit pitfalls, iOS‑first UI assumptions, and animation limits that force native drivers. Outcome: daily builds and mostly native feel, with Android cleanup handed to in‑house Android devs.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:49Gizmo Gadget Hopper
- 1:45React Native and Android
- 1:59Its not that fun
- 2:24React Native sunsetting
- 3:08React Native goals
- 4:43Why are companies dropping React Native
- 4:59Why people are giving up
- 5:28JSX sensitivity
- 7:50Styling
- 10:19iOS first mentality
- 11:49Is React Native worth it
- 13:16Airbnbs React Native experience
- 14:43Final thoughts
related talks
50mReact Native hindsight from Pl@ntNet
52mWhy you should use React Native for your next mobile app
39mReact Native - Unleash the power of React in your device
28mShould I use React Native too?
25mReasons to give React Native a(nother) try
41mReact Native - A native love story
25mGoing Native
31mUsing React Native to ship fast and navigate performance improvements