Progressive Web Apps Are Easy Now - Or Are They
summary
Builds a real Progressive Web App: a poker hand-reviewer that parses hand-history files, runs range analysis in a web worker, and caches the whole UI so it runs offline. Uses a service worker (implemented with workbox) plus hashed asset names, explains cache strategies (stale-while-revalidate, network-first), and needed skipWaiting/clients.claim to force updates. Covers touch vs mouse event handling, OAuth login failing on iOS, testing with emulators and Lighthouse, and confirms the app works across desktop and Android but has iOS quirks.
AI-written summary · about
chapters (12)
- 0:00Introduction and travel story
- 2:06Why build a poker PWA
- 5:53Demo of poker analysis app
- 9:02What are PWAs
- 12:58Service workers explained
- 15:27Caching strategies with Workbox
- 17:33Web app manifest setup
- 18:39Making apps responsive
- 20:22Handling touch and mouse events
- 22:50Cross-device interaction challenges
- 24:14Service worker updates and testing
- 25:17Final advice and resources








