Overview of OBACloud Push Notification Features
OBACloud provides three primary push-driven features using the same APNs device token. All endpoints are unauthenticated, and ownership is determined by possession of the APNs token or the specific resource URL. All features are region-scoped; if a region has no sidecar URL, push features are unavailable.
| Feature | Trigger | Token Association | Notification Type |
|---|---|---|---|
| Trip alarms | Rider-defined (e.g., 10 mins before arrival) | Attached to alarm at creation via user_push_id | Alert + custom arrival_and_departure payload |
| Live Activities | Server-pushed updates to Lock Screen | Attached to activity at creation via push_token | ActivityKit content updates (no user alert) |
| Service alerts | Transit agency publishing an alert | Proactive device registration via /push_registrations | Plain alert (title + body) |