I’m not conflating them in the way you think I am. You seem to be unaware of what a PWA actually is. As an example, if you go to twitter.com on your iPhone in

I’m not conflating them in the way you think I am. You seem to be unaware of what a PWA actually is. As an example, if you go to twitter.com on your iPhone in Safari, you can click the share button, click Add to Home Screen, and you will get a very app-like Twitter experience when you launch what you just added to the Home Screen. Because it is an app. Literally the only reason I’ve seen that most people would be dissatisfied with the Twitter PWA is because it lacks notifications. In my experience, it is often faster than the native app and does fewer dumb things, like clicking on a YouTube link actually opens in the YouTube app, instead of the way the native Twitter app tries to keep you in a modal web view. Regardless of Apple marketing, PWAs run in a more secure environment than native apps, because Safari is used to dealing with untrusted code on every single page you load. Apple leaned too much on their insufficient app review process instead of native app isolation technologies for too long. They have fortunately corrected course over the last couple of years… but native apps still present higher risk. (PWAs also run completely isolated from the regular Safari browsing session, so you will naturally need to sign into Twitter again even if you were already signed in within Safari, but then it stays signed in exactly like the native app.)