What problem does it solve?
It solves the operational complexity of sending notifications across different push ecosystems by providing one provider-agnostic interface for both browser Web Push (VAPID + Service Worker) and Expo Push.
Core Features & Use Cases
- Unified push abstraction: Send the same logical notification to both web PWA and future native Expo recipients, selected per stored token platform.
- Token registration + outbox workflow: Register device tokens via tRPC, inspect queued sends in the push outbox, and manage delivery status for debugging and testing.
- Service-worker delivery for web: Receive push payloads in the Service Worker and render notifications and click-through navigation consistently.
Use case example: When a customer earns a stamp or is eligible for a redemption, use push to notify them on their phone (Expo) and/or PWA device (Web Push) with correct titles, bodies, metadata, and click actions.
Quick Start
Use the push.send API to send a stamp-earned message to a customer, ensuring the browser or token platform has been registered first.