React Native hindsight from Pl@ntNet
summary
React Native is used to run the Pl@ntNet app (about 30M users/year) with one mobile developer maintaining both Android and iOS. Benefits described include fast screen development and iteration (example: a group-management flow built in about a week) and using redux with redux-persist for local state; downsides include unstable third-party native modules (camera roll, maps), ongoing native bug maintenance and heavyweight Java/Obj‑C patches (e.g., patched Android camera‑roll code), and tooling tradeoffs between Expo and a fully native setup.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 7:23Live demo React Native app
- 10:12FlashList performance
- 13:03Cross-platform rendering issues
- 18:17State management Redux
- 21:43Permissions and APIs
- 27:16Debugging React Native
- 31:28Common bugs solutions
- 37:04Dependency updates
- 41:18Build and deploy
- 43:25Stability stats
- 45:30React Native future
- 46:52Experience and conclusion
related talks
17mDispatches from React Native
25mReasons to give React Native a(nother) try
01h 01mReact Native: A Better Way to Do Mobile
44mReact Native: how to succeed with your mobile app
52mWhy you should use React Native for your next mobile app
23mReact Native Or Expo? Both.
25mGoing Native
45mReact Native: Things we learned the Hard Way