Skip to Content
Platform.Ontology

Notification Triggers (abandoned)

Scheduled local notifications that fire without a server; not shipped.

Works without askingNotifications and backgroundNotificationsWeb browsersWhile you use it

In one line

Can't schedule a notification for later without a server; no browser ships it

Scheduled local notifications that fire without a server; not shipped.

Would have let a site schedule notifications for a future time without push. Chrome ran an origin trial and then dropped it, so no browser ships it.

What it can and can't do

What the user does: Nothing. Chrome tried an experiment, then dropped it

It can

  • Show a normal notification when a server sends one, which is a different feature
  • Use a reminder style app that depends on push instead

It cannot

  • Schedule a future notification from the page alone
  • Work in any browser today
  • Skip the notification permission, which it would still have needed
  • Run in Firefox or Safari

Browser support

BrowserStatusFirst versionReleasedNote
ChromeRemoved802020-02-04Origin trial 80 to 85, removed
EdgeRemoved802020-02-07None
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidRemoved802020-02-04None
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

APInew TimestampTrigger(timestamp); showNotification(title, {showTrigger})
Permission namenotifications
How access is grantedorigin-trial
What the user seesNeeded notification permission plus an origin trial token.
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsPer scheduled notification
How to take it backn/a
Inside an iframeService worker

Typical flow

  1. Request notification permission
  2. showNotification with showTrigger
  3. Browser fires at the time

Data you get

What comes back: Scheduled notification
Shape: event
How often: at timestamp

No individual data fields. The signal is the access itself.

Technical limits

  • Not available
  • Replaced by calendar apps and push

The story

What it is

A plan to let sites schedule alerts that fire without a server. It was dropped and not released.

For you

You will not see this feature. It was tested but never shipped. Scheduled alerts still need a server push or your app to be open.

For makers

Makers wanted to set reminders on the device without paying for a push server. Browser makers stopped the work. Developers use push messages or local checks instead.

Where you see it

TypeExampleApps
productivityA calendar web app wanted to schedule a reminder for a meeting an hour from now, with no server.Google Calendar
healthA medicine reminder site wanted daily alerts on the device, even when offline.None named
gamesA farming browser game wanted a ping when crops finish growing, with no push server.None named
travelA travel app wanted a boarding reminder two hours before a flight without a connection.None named
educationA language app wanted a daily practice nudge that works offline.Duolingo
fitnessA workout site wanted timers that alert you after rest periods while the tab sleeps.None named
shoppingA store wanted to remind shoppers of a sale start time without a server.None named

Risks

  • Never shipped
  • Could be spammy

Good uses and abuse

Legitimate uses

  • Reminders

Known abuse

  • None now

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2020-02, Chrome 80: Origin trial starts
  • 2022-01, Chrome 98: Trial ended and the feature was abandoned
  • Notifications. Can show messages on your screen outside the browser tab, once you tap Allow

Sources

How well checked: Inferred from related behavior.

On this page