Re: About the new native notification library for mobile apps...
Posted: Thu Jun 25, 2026 8:32 pm
Hi Fred,
Actually, browser notifications aren't dead at all; they are heavily relied on by modern web apps like Discord or Slack, I use Slack in my browser for work and get toasts. The reason MDN flags the API as "Limited availability" instead of Baseline is due to mobile browsers, which throw a TypeError if you use the standard desktop constructor and instead require a Service Worker. On desktop, however, the MDN Notifications API documentation explicitly notes that it strictly requires a secure context (HTTPS/localhost) and *must* be triggered directly by a transient user gesture, like a button click, or the browser will silently kill the request, just like sound. I'd still really love to see this in SB, for proper PWA support.
Thanks as always and keep being awesome!
Actually, browser notifications aren't dead at all; they are heavily relied on by modern web apps like Discord or Slack, I use Slack in my browser for work and get toasts. The reason MDN flags the API as "Limited availability" instead of Baseline is due to mobile browsers, which throw a TypeError if you use the standard desktop constructor and instead require a Service Worker. On desktop, however, the MDN Notifications API documentation explicitly notes that it strictly requires a secure context (HTTPS/localhost) and *must* be triggered directly by a transient user gesture, like a button click, or the browser will silently kill the request, just like sound. I'd still really love to see this in SB, for proper PWA support.
Thanks as always and keep being awesome!