Taking Web Apps Offline
summary
Built Google Docs Offline that lets users edit and persist documents without a network by moving the app model to the client, storing state in IndexedDB, and syncing via a shared worker plus a background page granted by the Drive Chrome app. Offline loading uses an appcache fallback manifest and URL rewriting with the history API; mismatched HTML/JS versions are solved with Chrome-specific intercept entries. Works in Chrome today; cross‑browser and performance quirks remain.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:34Background
- 1:47Google Docs
- 6:36Shared Worker
- 7:14Background Page
- 8:31Application Cache
- 9:19The Difficulty with Docs
- 10:37Fallback Location
- 13:05Css and Js Bundles Have To Match the Landing Page
- 19:21Intercept Entries
- 19:38Chrome Specific App Cache Entries
- 21:52Network Outages
related talks
01h 01mMake Your Web App Work Even Offline — It's Possible!
48mThe Web's future is offline
40mWeb Apps without Web Servers
30mOffline First: Making Your App Awesome When the Network Isn't
45mOffline First (Web) Apps
41mOffline Web Apps don't exist anymore!
22mSurviving the Offline Apocalypse
52mOffline web applications don't exist anymore!