Set it. It shows up.
Real notifications on your phone and laptop, sent now, in 30 seconds or every minute, with a receipt for each one.
1 · This device
2 · The notification
3 · Receipts
Nothing sent yet.
Set it. It shows up.
Why this matters
What you just saw
The notifications that show up even when the tab is closed. Allow them once, write a message, and send it now or schedule it: in 30 seconds, in two minutes, or every minute until you cancel. Scan the code to add your phone, and both devices get it. The receipts say when each one went out and how many devices it reached.
How it works
One call in the browser registers the device: the platform serves the service worker, holds the VAPID keys, encrypts the payload and stores the subscription against this visitor. The server either sends straight away, which returns a per-device delivery report, or schedules the notification with an idempotency key, optionally repeating on an interval. The card reads the job back when it is due to show when it fired and how many attempts it took.
The bigger picture
Reminders, order updates, digests, “your export is ready”, waitlists, event alerts: push is how an app earns a second visit. Building it usually means VAPID keys, a service worker, a subscriptions table, an encryption library and a cron job to send the scheduled ones.
Why Maravilla
On Maravilla, push is a platform service. There are no keys to generate, no service worker to write and no scheduler to run, and it works for signed-in users and anonymous visitors alike. Scheduling is idempotent by key, so rescheduling on every save simply replaces the pending job.