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

After having spoken to more developers, as well as having investigated more `push` event implementations, it's clear that JavaScript is predominantly needed for analytics (including, indirectly, for commercial purposes), and that there's little appetite from the ecosystem to change this.

We're very interested in any proposal that enables the resource consumption of push notifications to decrease—primarily processing costs, secondarily storage costs. Disassociating push subscriptions from service workers is appealing as it removes the need for push-only service workers, and including the notification's contents directly in the push message is great for developer ergonomics and flexibility.

However, given the above, the `mutable` attribute is very likely to negate much of the opportunity to decrease processing costs. The storage cost savings don't really apply to Chrome since we don't remove otherwise in-use service workers on behalf of the user. Something `<a ping>` or a beacon could be a good alternative to consider, ideally providing some flexibility on timing guarantees.

Because of that, our position should also be considered negative.

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

Message ID: <w3c/push-api/issues/391/2646571285@github.com>