Not to mention that the opposite is also true where a large number of "native" apps are really just wrapped up web apps and many suffer these same issues.
Part of the reason I'm not more bothered by Apple making PWAs viable is that they've failed to crack down on apps that don't meet their performance standards, anyway, letting those apps get away with just being terrible-performing, non-native-feeling web-app wrappers. That whole class of trash-tier "app" may as well be a PWA, I guess.
I'd rather they kick out every app with an unjustifiably-long launch time or with janky non-native behavior in places where it has no reason to be so, but since they're evidently not gonna do that, may as well have PWAs.
Ultimately, itβs a business decision, because paying for 3x the people or 3x the time to implement one feature on web, iOS and android is not something that people like to do, let alone the headache of coordinating feature parity and release timeline with said teams.
That's certainly not inherent to every PWA, e.g. there is no need to have a "loading screen for every click".