> While WebKit is making progress on PWA support, at the time of this writing, PWAs remain a second-class citizen on iOS. The iOS App Store’s support for PWAs is non-existent, requiring a web view-based solution like PWABuilder’s.
> Additionally, because iOS doesn’t allow 3rd party browser engines, your PWA is limited to WebKit’s PWA capabilities, which are currently lagging behind other browser engines.
Google isn't abandoning PWAs, and in fact Chromium continues expanding support to make them as native as possible:
https://web.dev/window-controls-overlay/
Might I also add that the web app manifest is also an open standard, that Safari is lacking on:
This has been available for close to a decade.
Guess what. Users hate it. They hate mobile web apps and their slow, clunky, feature-poor, non-native interfaces and for that reason they will also hate PWAs.
https://blog.pwabuilder.com/posts/publish-your-pwa-to-the-io...
> PWAs remain a second-class citizen on iOS
> PWABuilder doesn’t guarantee that your app will be accepted into Apple’s App Store.
> In 2019, Apple released new guidelines for HTML5 apps in the App Store
2019 isn't close to a decade.