Progressive React Apps
summary
Project scaffolding registers a service worker by default but real work is the runtime architecture: register it in production, use Workbox to define cache strategies for statics, persist dynamic API data into IndexedDB (or use PouchDB+CouchDB replication) and implement conflict resolution or sync logic, handle install via a web manifest and HTTPS, surface push notifications and the beforeinstallprompt at sensible moments, and verify behavior with Lighthouse audits so offline, installable, and update semantics actually work.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:11Our Application
- 6:16Don't break the web
- 8:15Feature detection
- 11:46Responsive - Tools
- 14:01Offline First
- 20:44Service Workers
- 29:35Where does the data handling happen?
- 33:37Redux Observable
- 42:17Discoverable
- 43:23Re-engageable
- 48:21Installable
- 52:02Lighthouse
related talks
59mProgressive React Apps
35mProgressive Web Apps: trick or real magic?
35mProgressive Web Apps with Angular 2
01h 00mBuilding Progressive Web Apps with React
33mManaging data and resources in your Progressive Web App like a pro
32mCross-platform Progressive Web Apps
38mProgressive Web Applications: The What, the Why and the How
27mProgressive what apps?
