Service Workers and their role in PWAs
summary
Service workers are shown as a real client-side proxy that registers, installs (cache.addAll) and activates to serve cache-first fetch strategies, offline fallbacks and background tasks. Concrete numbers matter: Google finds about 20% drop per install step and a 69% abandonment for an interstitial (69% abandonment), while native apps show ~16x engagement—PWAs aim to combine that reach and engagement. Examples include a Flipkart Lite PWA using web manifest, HTTPS, and push API + Notification API to deliver working offline and reengagement features.
AI-written summary · about
chapters (15)
- 0:00Start
- 8:45Native App Installation User Flow
- 9:49Progressive web Apps
- 13:07Service Workers
- 14:02How does a service worker work?
- 16:23Lifecycle of a Service Worker
- 18:19Registering a Service Worker
- 19:34Installing a Service Worker
- 20:54Activate a Service Worker
- 23:00General idea
- 27:37FEAR OF COMMITMENT
- 29:13Push workflow components
- 29:58What makes push notifications?
- 32:55Handle Push Event
- 35:38SERVICEHORKER
