When to Go Native Over Javascript
summary
Demonstrates concrete tradeoffs: Expo requires detaching to add native modules, CodePush cannot change native binaries so a new release is needed, and a navigation experiment shows native navigation renders fewer offscreen views and reduces memory compared with JS stacks. Builds a delivery app that proves periodic geolocation needs platform APIs so background location requires enabling iOS background modes and native timers. Code and example apps are on Github and the native parts work as shown.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:52What is Expo?
- 3:48How does Native Code affect expo?
- 5:05What is CodePush?
- 8:05Example App
- 10:21React Native Navigation
- 11:39Accessibility
- 13:19React Navigation
- 13:43Native Libraries Cons
- 15:15What does the Driver app do?
- 17:19Demo Source
- 18:16Testing
- 20:28iOS Background Modes
- 22:06Things To Note
related talks
26mIntroduction to Cross‑Platform Development with React Native and Expo
23mReact Native Or Expo? Both.
52mWhy you should use React Native for your next mobile app
35mBridging the Gap: How to use React Native in existing large native code bases
25mLimitless App Development with Expo and React Native
53mHow React-Native shapes the way we think about native apps
44mReact Native: how to succeed with your mobile app
25mReasons to give React Native a(nother) try
