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.
> 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.
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.
Where "support PWA" and "no shenanigans" are which of the ever shifting sets of APIs?