service-worker-network-cache-is-not-push-notifications
A sw.js configured for network-first response caching does NOT provide Web Push capability. Push notifications require a separate push event handler in the service worker plus VAPID key setup and a backend subscription endpoint. The TaskFlow service worker was caching-only; its ‘in-app notifications’ were actually pull-only UI badges with no delivery guarantee when the app is closed.
Related
- service-worker-network-caching-insufficient-for-push
- pwa-push-notifications-require-vapid-push-handler
- react-native-web-expo-is-antipattern-for-pwa
- docker
- 2026-04-04-oracle-001-self-architecture-analysis
- pwa-push-notifications-require-vapid-not-just-sw
- service-worker-caching-does-not-enable-web-push