What problem does it solve?
Web Push notifications for CometChat chat are fragmented across client Service Worker logic, subscription management, a push-sending backend, and CometChat webhook wiring, so users miss new-message alerts when the tab is in the background or closed.
Core Features & Use Cases
- End-to-end Web Push plumbing: client subscription creation, server webhook handling, and browser notifications for new messages.
- Click-through to the right conversation: notification click focuses an existing tab or opens a new one to the correct chat thread.
- Production-grade guardrails: VAPID key separation, webhook signature verification (HMAC), HTTPS requirements, deduping behavior, and iOS Safari PWA-only caveats.
- Typical use case: a user receives alerts for messages in a group or 1-on-1 chat even after closing the browser tab, then lands directly in the right conversation on click.
Quick Start
Enable notifications and call the skill’s registration flow after login so the browser creates a push subscription and registers it to your push server keyed by the CometChat user UID.