Surviving the Offline Apocalypse
summary
A working HTML5 offline-first app is described: it uses application cache with a dynamic manifest, stores structured data in IndexedDB (async transactions, indexes and key ranges), saves patient photos via the Chrome file system API with an IndexedDB polyfill fallback, and uses navigator.online plus online/offline events and retry flags to sync. The deployed system records about 9000 kids and successfully supports distributed clinics with intermittent mobile connectivity.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:21Surviving the Offline Apocalypse
- 1:09Why Does Offline Matter?
- 2:37Why Does Offline Matter To Me?
- 3:37The Problem
- 4:19The Solution
- 5:08Rules for Survival
- 5:42Live off the grid: Application Cache
- 8:15Application Cache Browser Support
- 9:51Supplies: IndexedDB
- 14:20IndexedDB Browser Support with Polyfill
- 14:49Adequate Weaponry: FileSystem API
- 17:48FileSystem Browser Support
- 19:12An Escape Plan: navigator.online
related talks
32mOnConnectionLost - The Life of an Offline Web Application
45mOffline First (Web) Apps
38mHow we developed an Offline‑First app using Persistent Storage
30mOffline First: Making Your App Awesome When the Network Isn't
56mGetting off(line): appcache, localStorage for HTML5 apps that work offline
31mI'm offline, cool! What now?
29mGive Apps Online Superpowers by Optimizing them for Offline
23mJavaScript: Off the Grid