Progressive Web
summary
Argument: keep the P in PWA by using progressive enhancement not replacing it. Practical claims: offline caching and background tasks via service workers, installability via web app manifest, payments via new Web Payment APIs, security via HTTPS and Content Security Policy. Patterns and numbers: ship a minimal HTML baseline then progressively add JS (aim for 50% coverage now and 98% as browsers update), follow the purple pattern to render fast, restore shareable URLs and navigation when removing the browser chrome.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:09Progressive Web Apps
- 1:58A quick example of a web app
- 6:59Declarative VS Programmatic
- 11:03The web is based on Standards
- 14:30The Web is Built to Last
- 26:38How Web Apps grew out of the mobile web.
- 29:38Why was native better?
- 34:00Layers of Progressive Enhancement
- 35:16Performance
related talks
47mProgressive Web Apps
43mProgressive Web Apps - the Return of the Web?
41mProgressive Web Apps
38mProgressive Web Applications: The What, the Why and the How
11mWhat's inside the term 'progressive web apps'
37mIntro to Progressive Web Apps
46mKeynote: Progressive Web Apps
50mThe (Awesome) Future of Web Apps
