Comment by mirkodrummer
1 day ago
again battery friendly how? because you install them first? please... as I said native apps still abuse notification system(and battery) pushing ads. Apple just hate the web platform, and them trying to push alternative solutions is just PR for how little they care about PWAs and their progression
Battery friendly because notifications can be coalesced by the OS and processed without having to fire up a full browser engine process and JS VM just to unpack the notification and post a visible notification.
Even in the case where the app needs local processing to show the best notification, having this as fallback removes the risk that the app misses the deadline to display a visible notification and therefore loses its push subscription (which is a behavior Chrome and Firefox have too).
We're also not removing classic Web Push, so web apps can deny themselves the benefits of Declarative Web Push if they don't like it.
This is a PWA-only feature; why would they spend the time to implement this if they didn’t care about PWAs?
also a webkit only feature far from the web standard, hence their carelessness
The blog post documents a relatively long engagement process with the web standards process. Starting with publishing an explainer (pretty common for the browser engines), directly talking with the other browser engines and web developers at the W3C TPAC conference, making concrete proposals to the relevant web standards githubs, taking feedback, etc.
Can you elaborate on the carelessness here? What should've been more careful?
I expect you will apply this to the other browsers who are 100x worse than Apple at adding proprietary features.
And if you read the article Apple reached out to the other browser vendors to push it as a standard.
It's standards track and we've had positive signals from Mozilla and Google. Apple is just the first to ship in this case. Are you also mad when Apple is _not_ the first to ship a feature? Is there any way to win?