Hacker News Reader

Comment by dmitriid | Hacker News Reader

There's no such thing as "PWA". There's half a dozen to a dozen disparate APIs, and every PWA proponent has their own list of what they consider PWA support.

However, Safari has had support for basically everything you need for a PWA except, thank god, notifications.

View on HN

For how many websites use notifications unnecessarily... I have a hard time feeling sorry for anyone complaining about how they can only do notifications from an app (which Apple could review).

There are legitimate uses of notifications from websites, like being told from my webmail that I've received a new email. Or any other messaging service. But no, let's throw the baby with the bathwater because some blog sites ask for notifications to spam you.

Apple isn't crippling PWAs because it cares about the user. They get more money if you pay for an app on their App Store. Simple as that. In every PWA thread I keep reading the same Stockholm Syndrome argument that Apple are crippling PWA to save us from the notification spam. Meanwhile I have native apps spamming me with offers.

> Apple isn't crippling PWAs because it cares

Apple isn't crippling PWAs. Once again: there's literally no such thing as PWA. It's bunch of very different standards.

You decided that notifications support are a 100% must to qualify as "not crippling PWAs". Whereas to qualify as a "PWA" an "app" literally only needs two things: service workers and being able to be "installed". Everything else is just gravy.

Reply on news.ycombinator.com