Offline first applications in React Native done well
summary
Explains concrete patterns: store user and uploads locally first, show optimistic UI for image uploads, and keep a persistent action queue that retries on connectivity. Uses react-native-offline for isConnected, action queue and network middleware, and redux-persist with Realm to survive crashes and app kills. Implements an example app "insta meow" (on Play Store, App Store rejected) that demonstrates canceling queued uploads, rolling back failed requests, and the current limitation of no native background queue.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:28Overview of app connectivity
- 3:11Bad UI practices
- 5:14Best practices for UI
- 9:35Offline-first principles
- 12:26Implementation and tools
- 15:38Advanced state management
- 23:31Future improvements
- 27:42Conclusion
related talks
28mAsynchronous & Offline Magic Tricks on React Native
20mOffline-First React Native: Designing for production
42mReact Native case study: From zero to a super hero app
40mOffline Mode, Online Impact
24mZero-Latency React Native: Apps Without Loading Spinners
34mOffline-First Mobile App Design
34mReact Native: The dark side of Background tasks
35mHow Offline-First Architecture Could Save Your Apps