Automatic Progressive Web Apps using the Angular Mobile Toolkit
summary
A single CLI command flips an Angular app into an installable, offline-capable PWA using @angular/service-worker and Angular CLI; the build emits a service-worker bundle plus an ngsw manifest that lists hashed files and plugins. Plugins provide static content caching, route resurrection, external-resource caching and flexible dynamic content strategies (freshness vs performance). A companion library exposes update events and registers push notifications; demos show the app working offline and receiving pushes, but service worker only runs in production builds.
AI-written summary · about
chapters (22)
- 0:00Start
- 3:37Milestones of the web
- 5:3710 characteristics
- 7:402 packages
- 8:584 main parts
- 10:39NGSW installation
- 11:18App build
- 14:28Static content caching
- 15:00Route redirection
- 16:34Extending NGSW manifest
- 17:24External content caching
- 19:04Dynamic content caching
- 25:37ngu-app-shell
- 27:19Companion
- 28:05Gentle app update flow
- 29:52Push notifications
- 32:42Push settings
- 33:05Push subscription
- 34:58Basic Service Worker
- 35:40Extending functionality
- 36:06Automatic PWA
- 36:45Roadmap
related talks
30mAutomatic Progressive Web Apps using the Angular Mobile Toolkit
22mAutomatic Progressive Web Apps using Angular Service Worker
37mAngular PWA: crafting apps that adapt anywhere
24mBuild progressive web apps with Angular
41mOffline Web Apps don't exist anymore!
41mPerformant and Accessible Angular Apps as PWAs
35mProgressive Web Apps with Angular 2
25mCreating an Angular Progressive Web App: which option will work better for you?
