Push without notifications

  1. The user grants permission.
  2. A whole lot of complicated stuff happens behinds the scenes.
  3. Next time the website publishes something relevant, it fires a push message containing the details of the new URL.
  4. The user’s service worker receives the push message (even if the site isn’t open).
  5. The service worker creates a notification linking to the URL, interrupting the user, and generally adding to the weight of information overload.
  1. The user grants permission.
  2. A whole lot of complicated stuff happens behinds the scenes.
  3. Next time the website publishes something relevant, it fires a push message containing the details of the new URL.
  4. The user’s service worker receives the push message (even if the site isn’t open).
  5. The service worker fetches the contents of the URL provided in the push message and caches the page. Silently.
  1. Display notifications based on those messages.
  • I grant push permission to a podcast. Whenever a new episode is published, it’s cached on my device.
  • I grant push permission to a blog. When there’s a new blog post, it’s cached on my device.

--

--

A web developer and author living and working in Brighton, England. Everything I post on Medium is a copy — the originals are on my own website, adactio.com

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jeremy Keith

Jeremy Keith

A web developer and author living and working in Brighton, England. Everything I post on Medium is a copy — the originals are on my own website, adactio.com