Creating an Angular Progressive Web App: which option will work better for you?
summary
Compares two concrete options and shows what actually works: using Angular CLI 1.6 to generate an app produces ngsw-worker.js and ngsw.json that enable an offline app shell after a production build, runtime caching with prefetch versus lazy groups, and data groups with freshness or performance strategies. Demonstrates push by sending a payload wrapped in a notification field, exposes the SWUpdate observable for prompting reloads, and gives a kill switch (remove ngsw.json) plus practical hacks for update timing and debugging.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:25Maxim Salnikov
- 1:5910 characteristics
- 3:58Generate a new Angular PWA
- 6:46Adding NGSW to the existing app
- 7:28Service worker build support in the CLI
- 8:57NGSW configuration file
- 10:29App shell resources
- 11:08App shell / on-demand
- 12:12Runtime caching
- 14:59Push notifications / send
- 15:57App version updates
- 17:10Check for updates
- 18:10Debugging update flow
- 20:31Checking the status
- 20:46Kill switch
- 22:20Main available features
- 22:32Angular Service Worker advantages
- 23:14On the roadmap
related talks
24mBuild progressive web apps with Angular
22mAutomatic Progressive Web Apps using Angular Service Worker
29mBuild progressive web apps with Angular
43mAutomatic Progressive Web Apps using the Angular Mobile Toolkit
35mProgressive Web Apps with Angular 2
33mProgressive Web Apps - the Angular way
54mBuilding an Angular PWA: Angular Service Worker or Workbox?
32mBuilding an Angular PWA Angular Service Worker or Workbox?
