[kevincox]

This is fairly easy to resolve by packing up your PWA and submitting to the various stores. Bing will even detect and automatically add "popular PWAs" to the Microsoft store.

So sure, you still end up paying the Apple/Google tax for discovery (and the Apple tax for looking like an app instead of a webpage) but it gets you that discovery you want and you only need to maintain a single codebase.

And example is my app which I packaged up using https://www.pwabuilder.com/. It was just a couple of clicks to publish to the Play Store. It will look as pretty as you make it and most users won't realize that it isn't a "native" app. Honestly the biggest issue is that it doesn't download the app until the first launch. (Although you can use different tooling to include a copy of the site in the app)

https://play.google.com/store/apps/details?id=com.player_one...

[ChrisKingWebDev]

Does building a PWA this way support In App Purchases? I would much prefer keeping my app as a PWA, or in my case, a managed Expo React Native app. But eventually I'll have to break it apart to support IAP.