React Native at Eaze Marijuana Delivered
summary
Eaze runs two mobile apps — a cross‑platform driver app and a consumer app that later split with Android moved to Kotlin — maintained by a four‑person mobile team. Key specifics: code push enables over‑the‑air updates for sideloaded drivers, five native repos remain for long‑running background work, an experiment packaging React Native as a native aar works only without npm modules, and the JS–native bridge is asynchronous today which complicates integrations.
AI-written summary · about
chapters (12)
- 0:00React Native at Eaze
- 1:07Why Eaze chose React Native
- 2:29React Native in 2018
- 3:13Driver app benefits
- 4:15React Native learning
- 4:35CodePush for driver app
- 5:19React Native challenges
- 6:00iOS team kept React Native
- 7:04Android to Kotlin
- 8:06Integrating React Native
- 9:08React Native bundler limits
- 9:50Future of React Native
related talks
28mShould I use React Native too?
27mReact Native at Uber Eats - handling scale and complexity
17mDispatches from React Native
50mReact Native hindsight from Pl@ntNet
45mReact Native: Things we learned the Hard Way
41mAs Easy as Ever - Apps for Android and iOS with React Native
20mBuilding a Mobile App with Expo, EAS and React Native
25mReact Native at Traveloka