Going Progressive with Ember
summary
Shows how to make an Ember app a real PWA: add an app manifest to get an icon and splash, register a service worker to cache assets and serve content offline, and use local storage strategies (localForage or ember-local-storage and ember-pouch backed by PouchDB/CouchDB) to let users create while offline and sync later. Use FastBoot for server-rendered first meaningful paint and Ember Engines for lazy-loaded JS (note current friction between Engines and FastBoot). Lighthouse scores improve; Safari still lacks service worker support.
AI-written summary · about
chapters (18)
- 0:00Isle of Code
- 1:47The Web Ahead
- 2:24PROGRESSIVE WEB APP?
- 3:43LOOKS GOOD?
- 4:24INSTALLS ON DEVICE?
- 7:52WORKS OFFLINE?
- 10:43BACKGROUND SYNC
- 12:10ember-service-worker-asset-cache ember-service-worker-index
- 17:59Ember data adapter for local forage
- 18:42Ember Data for PouchDB/ CouchDB
- 20:03FIRST PAGE RENDER
- 20:30Server side rendering
- 21:08SECOND PAGE RENDER
- 21:29TIME TO INTERACTION
- 22:33TOOLS
- 24:56BACK TO THAT DREAM...
- 25:292. IT IS DOABLE WITH EMBER
- 25:58WE NEED YOUR HELP!








