Asynchronous & Offline Magic Tricks on React Native
summary
Claims that a React Native app can survive offline by combining redux-offline with device NetInfo and an optimistic queue with commit/rollback, demonstrates a small Trello-monitor that enqueues POSTs FIFO and replays them with exponential retries (doubling up to ~10 minutes). Implements persistent state via Redux Persist migrations plus transforms/compression to avoid size limits, uses redux-saga for side effects, and discusses backend conflict strategies (HTTP 409, timestamp or first-writer rules); the demo shows the approach working end-to-end.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:01Client Expectations
- 2:25Offline Issues
- 3:35Defensive Designer
- 4:11Avoid Failure
- 4:53Reading Strategies
- 6:27Redux Persistence
- 7:09Redux reducers
- 8:11Redux persist
- 8:50Redux issues
- 10:00Redux persist migrate
- 12:02Varnish Memcached
- 12:48Reading Data
- 13:00Handling Failure
- 13:35Be Optimistic
- 15:12Redox Queue
- 17:47Redux Offline Configuration
- 19:00Warnings
- 20:16Side Effects
- 23:23Conclusion
- 23:47Conflicts
- 24:27Handling Conflicts
- 26:34Rejecting Conflicts
related talks
28mOffline first applications in React Native done well
20mOffline-First React Native: Designing for production
42mReact Native case study: From zero to a super hero app
24mZero-Latency React Native: Apps Without Loading Spinners
32mGoing Over The Speed Limit Synchronous Rendering in React Native
08mLightning talk from Lenka Vondrackova
01h 03mModern app development with Fable and React Native
24mThe Performance Myths of React Native apps