[krn]

If I already have a web app with a built-in recurring subscription functionality, I shouldn't be required to abandon it just to get it published on the Google Play Store.

The entire idea of allowing PWAs on Google Play Store seems to be a part of Google's wider product strategy, which includes ChromeOS and Android Go, where using a native app is not always the best choice.

Microsoft Store has already been doing this for a while for a different reason: a lack of Windows alternatives to the most popular mobile apps.

Apple, on the other hand, has no business case for integrating PWAs into the App Store, because they would just reduce its revenue.

[taurath]

If they allow PWAs to get around the 30% IAP feature, then in 5 years there will be no more native apps, only PWAs. I doubt they will allow any non-google play in app purchases to take place.

[krn]

I think the essence of a web app is that it works on any platform. It shouldn't know anything about Google Play Store or Apple App Store. Otherwise, it's just a native app with a webview.

[pjmlp]

They are called PWA, not WA, with P meaning Progressive.

The idea is that the app should check for available browser/OS APIs that progressively enhance user's experience.

And no they aren't necessarily just a native app with a webview, on UWP a store delived PWA has full access to the UWP APIs, just like .NET and C++, no need to write extra FFI manually.

No need for Frankenstein solutions like Cordova.

https://developer.microsoft.com/en-us/windows/pwa

https://docs.microsoft.com/en-us/microsoft-edge/progressive-...