Skip to main content
Wildo.ai Coming soon

Events and external data

Mobile push delivery is planned

There is no mobile push delivery: no device registration, no push provider and no push notification channel.

Planned — not available yet.

Mobile push is a planned notification channel without an implemented device-delivery path.

Mobile push delivery is planned

There is no mobile push delivery today. Nothing registers a device, no provider sends to one, and the notification channel vocabulary has no push member: an earlier push channel accepted declarations and sent nothing, so it was removed rather than left to look available.

For notifications available today, use the implemented in-app or email channels, or the transactional SMS service for its supported workflows.

Example — Choose an available notification path

A product needs to notify someone of a change now. It uses an implemented notification channel: a live in-app message for someone in the application, or an email for someone who is not.

For engineers

The notification channels are declared in notifications.shared.schemas.ts:

export enum CoreUserNotificationChannel {
  EMAIL = 'email',
  WEBSOCKET = 'websocket',
  FRONT_END_SUCCESS = 'front_end_success',
}

A working push feature needs a device-subscription lifecycle, a sender/provider contract, payload templates and delivery handling. Those are implementation work, not configuration an application author can switch on.

Use in-app messages for an active application session, and the implemented notification channels appropriate to the product’s reach requirements. Transactional SMS is a separate service and does not imply general push support.

Building a B2B product or an internal tool?

Wildo is not self-service yet. Tell us what you have in mind and we will say plainly whether it fits, and what happens next.