Taking an Image Editor Offline
summary
Claims that using an application cache manifest lets a web app survive network outages and even keep a site usable when the server is down, but warns the manifest is an aggressive all‑or‑nothing cache that can break XHR and requires a build step (Grunt timestamp) to force updates. Demonstrates an image editor built with the File API + canvas (Blob URIs, dataURIs), shows local persistence via localStorage/sessionStorage, and suggests a Node fs shim to swap server storage for client file system storage; demos mostly work but expose caching nightmares.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:17The Application Cache
- 9:15Clear Your App Cache
- 15:17File Api
- 24:21Local Storage Api
- 25:45Performance
- 29:59Private Browsing
- 31:13Session Storage
- 33:53Dependency Injection
related talks
56mGetting off(line): appcache, localStorage for HTML5 apps that work offline
31mApplication Cache: Douchebag
06mI'm Offline, cool. What now?
17mImmutable offline webapps
01h 02mPanel 1: Offline
33mOffline applications in an online world
44mDesign principles and implementation strategies for better offline experience
48mThe Web's future is offline
