Re: [w3c/push-api] Declarative Web Push (Issue #360)

I think there's two main factors to drive adoption:

1. Robustness. Even if the browser sees need to remove your service worker or not invoke it due to consuming-end-user-resources concerns, a notification can still be delivered as keeping around a push notification registration is much lower cost and showing a notification without involving a service worker is lower cost as well.
2. Easier to adopt. If you don't need to create a service worker for push notifications, it will be easier to add push notifications to your website.

I think there's also some benefit that if you do enable service workers (through `"mutable": true`) you get a `push` event that contains much more structured data allowing you to simplify your client logic.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/360#issuecomment-2474147284
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/issues/360/2474147284@github.com>