Introduction to Offline First Web Applications
summary
A replaceable Webmail PWA is built to work offline by wiring service workers to intercept requests, using the Cache API for assets and IndexedDB (115 MB used in one demo) for large local state, and queuing user actions to replay on reconnect; the Background Sync API (Chrome/Edge only) and the Persistent Storage API protect queued data from eviction. Tooling suggestions include Workbox, PouchDB/RxDB and Replicache-style replication, and a custom action-queue layer is shown that mutates local state immediately and reconciles or reverts changes after the server response.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:32The need for offline apps
- 3:37Defining PWA and problems
- 7:34Service workers and caching
- 11:07Background sync API
- 12:57Storage technologies
- 19:07Existing tooling and tools
- 21:45Architecture approach
- 23:59Introducing RMIJS
- 27:48Implementing mutations
- 30:00Live demo and results
- 33:33Open source plans
- 34:48Q&A session
related talks
52mOffline web applications don't exist anymore!
37mOffline web applications don't exist anymore!
30mOffline First: Making Your App Awesome When the Network Isn't
29mGive Apps Online Superpowers by Optimizing them for Offline
58mOffline Second
41mOffline Web Apps don't exist anymore!
45mOffline First (Web) Apps
38mHow we developed an Offline‑First app using Persistent Storage
