Using Service Workers in Ember
summary
Ember app for the developing world (target ~14,000 hospitals) proves service workers make offline usable: build uses broccoli-serviceworker to precache assets, includes serviceworker-toolbox for network strategies, and routes API calls to a local pouchDB so the app appears to succeed when offline. Moving pouchDB sync in service worker shifts blocking IndexedDB work off the main thread and improves performance. Notes: HTTPS required (localhost excepted), hard refresh disables service worker, and CI/headless browsers lack SW support.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:01How I Started Working with Service Workers
- 1:35Hospital Information System
- 5:16Cache Api
- 5:41Fetch
- 6:07Persistent Background Processing
- 7:44Resources
- 8:03Serviceworker Cookbook
- 8:20Chrome Developer Console
- 11:32Simple Configuration
- 13:09Serviceworker Toolbox
- 20:46Push Notifications
- 21:16Background Sync
related talks
27mTaking Ember Offline
26mGoing Progressive with Ember
05mLightning talk: Service Workers, use them
23mGo Offline with Service Workers
52mGoing offline
17mService Worker and the Appification of the Web
33mService Workers
01h 29mService Workers in Action: Building an Offline-Capable Webshop in under 90 minutes