I agree with most of the post, but I think making it hard to enable web push notifications is a good thing. The most common way I’ve seen web notifications used is websites tricking old people into clicking “enable notifications” and then constantly sending them ads and scams as notifications. Since web notifications became a thing, literally every single computer or android phone I’ve interacted with that’s owned by someone over 65 is shitted up by an endless stream of “Your computer has been hacked, call now for support”, “I’m in your area and horny, can we chat?”, “You won’t BELIEVE what happened to x celebrity”, etc.

If there would be real Chrome on iOS, then it would be possible to support Web Bluetooth API and I would not need to deal with Apple. A lot of people would not need to.

LLM slop, in addition to not being a convincing argument.

There is a vast space of PWAs that could be implemented without Bluetooth APIs, push notifications, or rotation lock.

But iOS has had “Add to Home Screen” since 2007, longer than the App Store has existed, and to a first approximation zero developers have ever opted to ship apps this way, even as Apple did make occasional improvements, like the Web Push API and metadata tags for app icons.

I guess it’s that two-tap process to install the app?