What's inside the term 'progressive web apps'
summary
Argues that progressive web apps are a concrete package: keep URL deployment while gaining OS presence and offline reliability by using service workers to control top‑level requests, do local caching and even server‑side templating in the client. Notes at least a dozen prior desktop/container attempts that failed by removing the URL advantage. Shows Chrome work that turns SPA frameworks (Ember/Angular/React/Polymer) into installable, fast, offline experiences and reports it actually reduces release friction and speeds navigation.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:23Why the name Progressive Web Apps
- 1:09How does this fit into the story
- 2:46Why is this different
- 4:35Web citizenship
- 5:43Its a race
- 6:41Low friction
- 7:29Progressive enhancement








