[giancarlostoro]

I'll go a step farther. iOS is the only mobile OS that restricts PWA's and I think they do it on purpose to force you out of PWAs and into native apps. I think Apple should 100% support PWAs with no shenanigans, they should work 100% without Apple needing to approve of anything too.

Steve Jobs pitched PWAs way back when, I don't know why all we've gotten is a half-baked solution from Apple other than they want you in their App Store with a native app.

[LocalH]

They figured out that the App Store made them more money than PWAs do, that's why

[raw_anon_1111]

It came out in the epic trial that 90% of App Store revenue came from games. Those were not going to be web apps.

[danaris]

What specific aspects of PWAs are still not supported on iOS these days?

I know that Apple made some huge advances in that within the past couple of years, but I...generally don't want PWAs myself, so I haven't paid very close attention. If you don't use Apple devices, and thus also don't pay very close attention, you might check and verify whether what you expect to be true still is.

[orloffm]

I have a local transit map as a PWA, and iOS asks me for permission to use my location every time.

[moi2388]

It didn’t go in the app drawer and is relegated to the home page. And no access to certain APIs which native apps do.

[raw_anon_1111]

So why aren’t there any great PWAs for Android and why do all of the companies that make apps for iOS make apps for Android instead of telling Android users to just use the web?

[troupo]

> I think Apple should 100% support PWAs with no shenanigans

Where "support PWA" and "no shenanigans" are which of the ever shifting sets of APIs?

[bsimpson]

I get the point you're making (that standards evolve, and Apple will drag its feet again if it sees a profit), but that doesn't change that they've been gating functionality behind app-only APIs for decades to grow their walled garden and make the rest of us worse off for it.

You shouldn't have to install things on your phone. Most "apps" should just be websites, with a bookmark if you so choose.

[troupo]

> I get the point you're making (that standards evolve, and Apple will drag its feet again if it sees a profit)

No, that's not my point.

My point is that there's no such thing as PWA. There's a lose collection of standards, and everyone choses a set that benefits their narrative when defining PWAs.

For a very long time Apple supported all APIs (except maybe notifications) that even Google defined as necessary for something to be a PWA. Didn't stop people from pretending that this is somehow not PWA.

> Most "apps" should just be websites, with a bookmark if you so choose.

As Android shows, even there no one wants that, and there are very few PWAs of note.

[Incipient]

The main reason/value I find for a pwa over a normal bookmark is the isolation of data, and the way most browsers hide the address bar and toolbar. The actual service worker etc logic...could pretty much take it or leave it.