What is the planned Push notifications module designed to do?
Notifications bring users back at useful moments. The planned module covers Apple Push Notification service, Firebase Cloud Messaging, device registration, notification templates, event-triggered notifications, scheduled reminders, notification usage limits, and retry and delivery-state handling. Future advanced capabilities may include iOS Live Activities and Dynamic Island updates.
The aim is that you describe what should be sent and when, and the backend handles tokens, queues, retries, and limits. You should not need to build a separate sending service.
How does the Push notifications module connect to other modules?
The notifications module is designed to subscribe to approved events from other modules instead of being called by custom code.
- Push notifications + Authentication. A device token is designed to belong to a signed-in user. When a user signs out or deletes an account, the registration is meant to be removed with it.
- Push notifications + Background jobs. A daily reminder is a schedule that triggers a template. The job layer is designed to handle timing and retries.
- Push notifications + Business logic. A rule can emit an event, for example a streak about to break, and a trigger is designed to send the matching template.
- Push notifications + Subscriptions. A lifecycle event such as a trial ending can notify the user. Usage limits can differ by plan.
- Authentication + Background jobs + Push notifications. Together they are designed to deliver per-user scheduled reminders for a habit app, with no worker code in your project.
What would you configure in the Push notifications module?
You list the channels you use, write templates, and map events or schedules to templates. You also set limits so that no user receives more messages than you intend, and you choose how failures are retried.
The configuration on this page is illustrative. The syntax is not final.
What stays your own code with the Push notifications module?
You write the message copy and decide the tone. You also own the notification permission prompt in the app and the choice of when to ask. The apps you build must follow platform rules and the law on messaging, including opt-in and quiet hours where they apply. Edict is designed to give you the controls, and it does not decide your messaging policy.
Is the Push notifications module available yet?
Planned. Edict is in development, and this module is not available. Push notification delivery is not claimed until it is implemented and tested on real devices. This page describes the intended design and gives no dates.
Join the beta waitlist to follow progress.