> Every other problem one could conceive of is solvable.
I think the biggest problem with PWAs is the resource usage. A well written PWA will use a lot more battery, network, CPU, and memory than a well written native app. That's not solvable.
PWAs are a lowest common denominator solution. They are good for developers but bad for users.
> A well written PWA will use a lot more battery, network, CPU, and memory than a well written native app. That's not solvable.
What complete nonsense. It's hardly baked into the rules of the universe. Of course Apple could figure this out at a technical level, it just doesn't work for their profit margins. Besides, it should be my choice and not Apple's whether I want to install an app that uses more CPU.
> They are good for developers but bad for users.
There are entirely valid use cases where the expense and hassle of making native apps prevents any app existing at all. Small businesses building apps for their staff, individuals building apps for themselves or families, small groups of friends.
It depends on what the app is doing. If it's something I load once a day to read HTML content that's already been downloaded, how's that going to be less efficient?
> If they had great support for PWAs a lot of companies and developers would go that route and there would be no native app option.
No. Apple doesn't want to let go of the app store model and the money it gives em. Every other problem one could conceive of is solvable.