Panel 1: Offline
summary
Conference panel argues that current offline APIs are broken in practice: AppCache serves cached assets even when online, updates only when the manifest changes, and aborts an entire atomic update on one 404, so a Lanyard-style web app using Mustache ends up caching the UI shell but synchronizing content into local storage or IndexedDB with ad‑hoc logic. The practical fixes proposed are a programmable navigation controller, explicit quota/permission for permanent caches, and better async storage primitives; two‑way sync remains application‑specific and hard.
AI-written summary · about
chapters (4)
- 0:00Start
- 27:52How Do We Enable App People To Build Application Architectures Offline
- 37:19Problems with Synchronization
- 57:43Add a Futures Primitive
related talks
41mOffline First
44mDesign principles and implementation strategies for better offline experience
45mOffline First (Web) Apps
39mSay Hello to Offline First
56mGetting off(line): appcache, localStorage for HTML5 apps that work offline
33mOffline applications in an online world
29mGive Apps Online Superpowers by Optimizing them for Offline
06mI'm Offline, cool. What now?
