React Native case study: From zero to a super hero app
summary
A personal Android app becomes a cross‑platform React Native app that actually supports iOS and Android, using Redux + Realm for offline-first state with linear migrations, Redux Observable for side effects, React Native Paper for theming, and CodePush for JS updates. Background sync ends up working on Android by bridging a native sync adapter to headless JS but remains unresolved on iOS. Navigation state gets persisted to survive OS kills, animations use the native driver for smoothness, and widgets and permissions require native code.
AI-written summary · about
chapters (35)
- 0:00Intro
- 2:07Features
- 4:15Architecture Stack
- 4:57Redux State manager
- 5:07Realm Database
- 5:25API calls
- 6:02Download TV Show example
- 6:58Fetching
- 7:48Storing
- 8:43Linear migrations
- 9:22Realm linear migration
- 11:47Paper Provider
- 12:14Twitter example
- 13:04react-native-i18n
- 14:47i18n - Android
- 15:43STOP THIS MADNESS
- 17:08Tablets and more
- 20:17To the background
- 20:48JS bundle destroyed
- 21:38Rehydrate
- 23:40Headless JS for iOS
- 24:19Android SyncAdapter
- 24:45react-native-sync-adapter
- 26:38Widget example
- 26:51Android Widgets
- 29:15Delightful interactions
- 30:23is not enough
- 30:51Permissions on iOS
- 31:47Permissions on Android API 23 or above
- 31:57Default targetSdkVersion for React Native on 29 September, 2017
- 33:12Dangerous on Android
- 34:14Remove permissions
- 36:24Default package name (By React Native)
- 36:43Change your package name
- 37:56Ratings
related talks
41mReact Native - A native love story
28mAsynchronous & Offline Magic Tricks on React Native
26mReact Native: A Beginner's Journey
44mReact Native: how to succeed with your mobile app
25mGoing Native
24mReact Native - Success case study
01h 13mMigrating to React Native: A long-term retrospective
31mRewriting a Large Hybrid App with React Native