Hacker News Reader

Comment by owebmaster | Hacker News Reader

> aside from PWAs competing with their App Store

Yeah. Aside. Let's just ignore that Apple intentionally prevents users from using the browsers most needed feature for the common user today killing it just like they killed Flash.

View on HN

Thankfully, otherwise the Web would already be ChromeOS Platform, because that is what 99% of the folks that don't use Safari would install.

Intentionally how? Mobile Safari has pretty broad support for PWAs: https://pwascore.com

It does not. It doesn't support the installprompt event and hides the "add to home screen" behind 4 actions/clicks to make sure the users don't easily install PWAs.

So one missing thing is enough to decide that PWA support isn't broad and Apple doesn't care about them, despite all those supported PWA APIs?

> behind 4 actions/clicks to make sure the users don't easily install PWAs.

I maintain a PWA for retainer client. Our website has a paragraph telling users how to install the PWA via the share button. We'd have a paragraph telling them how to install it from the App Store too if it weren't a PWA.

I think the fact that the paragraph is necessary is the damning part

Like I said, we'd have that paragraph even if the app was on the App Store. If it's damning, then it only damns the users because they're goldfish.

One missing thing? You think Apple forgot to implement the install event? Or that there is some technical reason?

No, I'm asking if that's the one thing you're hung up on? I feel like that was obvious.

On macOS i use Safari for PWAs. It is just fine.

But I use Firefox as my primary browser. PWA support non-existent. They killed their basic PWA support many years ago. There are suggestions they will support it in the future.

On Linux/Windows, I use Brave for PWAs.

Reply on news.ycombinator.com