Can I vibe code OneSignal?

Build a self-hosted web push notification service for an ecommerce platform using Node.js, Express, PostgreSQL, Redis, and BullMQ.

1. DATA MODEL:
- Store subscriptions with fields: id, user_id, endpoint (unique text), p256dh (text), auth (text), browser (varchar), os (varchar), user_agent (text), status (active, invalid, unsubscribed), created_at, updated_at.
- Store notification_logs with fields: id, subscription_id, payload (jsonb), status (sent, failed), error_message (text), sent_at.

2. FRONTEND SDK (Browser JS):
- Implement a lightweight JavaScript helper using Service Workers.
- Generate VAPID public key subscription requests using `registration.pushManager.subscribe()`.
- Provide a customizable double-opt-in modal UI before triggering native browser notification permission prompts.
- Send subscription JSON payloads to POST /api/subscriptions.

3. BACKEND API & QUEUE PROCESSING:
- Implement POST /api/subscriptions to upsert subscriptions into PostgreSQL.
- Implement POST /api/notifications/send endpoint for broadcasting notifications based on tag filters or targeting user_ids.
- Use BullMQ and Redis to enqueue message dispatch jobs asynchronously.
- Use the `web-push` NPM library configured with VAPID keys to send encrypted push payloads to browser endpoints.

4. FAILURE HANDLING & MAINTENANCE:
- Catch 404 (Not Found) and 410 (Gone) HTTP status codes from push services (FCM/Mozilla/Apple Web Push) and automatically mark subscriptions as 'invalid' in PostgreSQL.
- Implement rate limiting (max 100 messages/sec per domain) to prevent getting throttled by push gateways.
- Include automatic retries with exponential backoff for 5xx errors from push servers.

OUT OF SCOPE: Native iOS/Android app SDKs, in-app messaging overlays, complex visual journey flow builders.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs