Progressive Web Apps Are Easy Now - Or Are They
summary
Built a real Progressive Web App called BetterPoker.net that runs offline, keeps users logged in, and analyzes hands by narrowing an opponent’s preflop range from about 137 to 28 possible holdings. Implementation uses service worker caches entire app (workbox), a web worker for range calculations, Preact for UI, and a manifest + HTTPS. Notes iOS limits (OAuth loop, storage eviction) and needed skipWaiting/clients.claim to force updates; Lighthouse used for audits.
AI-written summary · about
chapters (8)
- 0:00Start
- 15:56Progressive Webapp Enablers
- 20:22Cross Device Functionality
- 21:39Cross Device Interactions Are Hard
- 22:47Implementing Interactions
- 24:03Service Workers Are Tricky
- 24:32Testing Interactions
- 25:43Getting Started
related talks
32mProgressive Web Apps
38mProgressive Web Applications: The What, the Why and the How
59mProgressive React Apps
35mProgressive Web Apps: trick or real magic?
53mProgressive Web Applications - The best of both worlds (App & Web)
31mWeb for all The power of progressive web apps
23mBuilding a Progressive Web App
46mKeynote: Progressive Web Apps
