Performant and Accessible Angular Apps as PWAs
summary
Angular projects get PWA features by running ng add @angular/pwa, which adds a service worker package, a manifest and an ngsw.json where caching strategies live; the service worker handles install/fetch/activate lifecycles, intercepts requests, and supports sw-update to prompt reloads when a new version is available. Real build used the background sync API to queue offline actions, yielding a 32% server call reduction, millions more users and an $8.8B increase in sales for the case study; iOS still lacks full push support.
AI-written summary · about
chapters (14)
- 0:00Introduction and thanks
- 1:46What is a PWA
- 3:31PWA superpowers
- 5:17PWA limitations
- 7:22Why I love PWAs
- 10:13PWA components
- 12:20Service workers explained
- 15:07Service worker lifecycle
- 20:01Service worker demo
- 22:33Angular and PWAs
- 27:23Angular PWA setup
- 30:35Angular PWA demo
- 35:40App updates with service workers
- 36:09Q&A
related talks
37mAngular PWA: crafting apps that adapt anywhere
17mCrafting Bespoke PWA Experiences with Angular
26mAngular PWA : The technology & pitfalls
43mAutomatic Progressive Web Apps using the Angular Mobile Toolkit
24mBuild progressive web apps with Angular
39mPROGRESSIVE WEB APPS 🚀 WITH ANGULAR
48mPWAs, are we there yet?!
41mOffline Web Apps don't exist anymore!