Mobile push delivery is planned
The notification model includes a mobile push channel for future device delivery. There is no current device-registration and push-sending path behind that declaration.
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 rather than assuming that a push declaration reaches a phone.
For engineers
The model contains this channel variant in notifications.shared.schemas.ts:
export const UserNotificationDefinition_PushSchema = UserNotificationDefinition_BaseSchema.extend({
channel: z.literal(CoreUserNotificationChannel.PUSH),
});
It accepts a declaration; it does not register a device, select a push provider or dispatch a device message. NotificationsDispatcherBackendService currently groups SMS and PUSH into a logging branch rather than a sending implementation.
Keep product behavior tied to an active sender
Do not use the presence of CoreUserNotificationChannel.PUSH as an availability check. A working push feature would also require device subscription lifecycle, a sender/provider contract and delivery handling. Those are implementation work, not configuration that an application author can switch on today.
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.