The (Awesome) Future of Web Apps
summary
Progressive Web Apps enable home‑screen install, push, offline and near‑native installs by combining a web app manifest with a service worker that precaches assets and applies runtime caching (sw‑precache, sw‑toolbox or workbox). Practical goals: show an app shell and render something under first paint <300ms; delay service worker registration until load; use code‑splitting, conditional polyfills, Lighthouse and DevTools coverage; leverage IntersectionObserver, requestIdleCallback, background sync, PaymentRequest and WebAssembly for faster, more capable web apps.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:44PWA Refresher
- 4:10Dynamic caching strategies
- 7:24Modern Best Practices
- 7:46Theme color
- 13:05Optimize first paint App Shell
- 15:18Debugging
- 28:48Passive event listeners
- 31:52Defer non-essential work
- 32:32Intersection Observer
- 34:47Background sync
- 37:42title: document.title
- 43:24Call to action
- 44:18Build your first modern Web App
- 46:18Google Web Fundamentals Mozila Developer Network
related talks
45mThe (Awesome) Future of Web Apps
47mThe (Awesome) Future of Web Apps
55mThe (Awesome) Future of Web Apps
38mProgressive Web Applications: The What, the Why and the How
47mProgressive Web Apps
46mKeynote: Progressive Web Apps
35mProgressive Web Apps: trick or real magic?
53mProgressive Web Applications - The best of both worlds (App & Web)
