> There's no such thing as a "PWA standard". There are half a dozen to a dozen various standards, and Safari supports the vast majority of them.
The parent talks about the webmanifest standard which is essential for PWAs (it describes the application and its package in a standard way). Safari does not support this, which is a pretty major standard to not support.
> Firefox usually clearly documents the reasons
I disagree. They state they have done user research (no information available on this) and that there is "little to no benefit" for a feature that was buggy and hidden behind configuration flags while at the same time enabling full support by default in their mobile browser.
> Ah yes, jeopardizing by ... supporting 99% of what passes for standard PWA features.
...except for notifications on iOS (which are coming, apparently, but it's taking them until somewhere next year) or A2HS on desktop (which they do support on iOS except in alternative browsers), which are pretty major limitations. The 1% remaining is still significant, the rest of the PWA standards Apple supports are just normal web standards that PWAs happen to use.
In all these discussions on HN the set of "essential standards" is always in flux, and is different for different people.
> They state they have done user research (no information available on this) and that there is "little to no benefit" for a feature that was buggy and hidden behind configuration flags while at the same time enabling full support by default in their mobile browser.
Because it's quite possible that it's buggy and confusing on desktop, but not so on mobile. Not so different from Safari, BTW which also has A2HS on iOS, but not on MacOS
> The 1% remaining is still significant, the rest of the PWA standards Apple supports are just normal web standards that PWAs happen to use.
So... The other ones are not normal web standards? Or are all web standards normal?
There's no such thing as a "PWA standard". There are half a dozen to a dozen various standards, and Safari supports the vast majority of them.
> Firefox removed support for some obscure reason
Firefox usually clearly documents the reasons
> Apple doesn't want to jeopardise its billion dollar app store
Ah yes, jeopardizing by ... supporting 99% of what passes for standard PWA features.