What point are you actually trying to make? That because some people might not want to create PWAs you think it is OK for Apple to break the existing functionality for everybody in order to flip the bird at the EU?
Apple is not going to lose revenue even if did have perfect PWA support since most of its money from the App Store comes from pay to win games that wouldn’t monetize nearly as well.
Apple doesn’t care enough about PWAs because users don’t care.
Maybe you are right.
But what is a PWA?
Maybe I have special website and users can configure Bluetooth devices via that page. No need to install a native App, no need for pwa.
All you need is a browser which supports the latest specs.
Most people can't image what could be possible without installing a native App.
We only know what we are used to. Much more could be possible without the need for native apps.
I am deeply relaxed, I am old. Hypes come and hypes go. The current hype for native apps will decline. The web is the only universal platform.
https://caniuse.com/web-bluetooth
And even with Chrome, much of the support is behind flags.
As far as universal platform - if you’re that old, you should know how much “universal platforms” for GUI apps have sucked since Java Swing.
You should also know how every mobile platform has said at one point that you can “build great apps with web technologies” - Rim, Palm, Microsoft, Android and even Apple - and they have all failed and sucked.
Again you have failed to state what relevance one set of devs not wanting to use PWAs has on anyone else who might want to use them, you've just restated your previous case that some people don't want to use them.
> Apple doesn’t care enough about PWAs because users don’t care.
As already stated in response to your previous statement about users not caring: the users shouldn't need to care if the developers are free to choose the right tool for their task (native application or PWA) and platforms implement those options well.
Apple should care about PWAs if it cares at all about providing a standards compliant environment. It certainly seems to care enough to try to derail them as a petty consequence of being told to do something they don't want to do.
> as I said to a first approximation no one cares about PWAs
What you said was that no users care. That is fine: users shouldn't need to care. Users don't need to care about such implementation details if developers are free to choose the best tool for the job.
> why aren’t they more popular on Android - 70% of the market?
Largely because the apps have already been developed and there is no point rewriting for new tech just for its own sake. And for things like games (the main thing that has been mentioned here as not being done as PWAs ATM) a PWA might not be the best tool for the job as native can give better performance in some areas.
PWAs are more attractive for new projects, and those that don't need to take advantage of being closer to the hardware.