OneSignal push
Push is useful for reminders and commercial alerts, but only if it is permissioned and restrained. The product should not train users to ignore it.
Good push use cases
- Wear reminder after a user opts in.
- Wishlist price or availability alert.
- Partner gift reminder.
- Appraisal or export ready.
- API quota warning.
- Retailer catalogue job complete.
- Creator campaign deadline.
- Corpus correction reviewed.
OneSignal constraints
OneSignal web push needs:
- HTTPS.
- A service worker on the same origin.
- User permission.
- Separate setup for each domain or subdomain origin.
- Testing across browsers and iOS home-screen flows.
Reference:
Architecture decision
Keep OneSignal as the push delivery layer, but keep Sniffopotamus as the source of truth for:
- user identity
- consent
- tags and segments
- event semantics
- suppressions
- audit logs
Do not let a push vendor become the product brain.