I do not think that is correct. Both Google and Apple _do_ allow PWAs. You can use many of the offline APIs, etc. and publish a web app that can be "bookmarke

I do not think that is correct. Both Google and Apple _do_ allow PWAs. You can use many of the offline APIs, etc. and publish a web app that can be "bookmarked" to the home screen, have icons like native apps, work offline, etc. There has been some controversy around privacy controls that affect PWAs (https://ionicframework.com/blog/is-apple-trying-to-kill-pwas/ https://ionicframework.com/blog/is-apple-trying-to-kill-pwas...) , and of course it won't be able to access ALL native functionality. You can also publish Cordova/Capacitor/NativeScript, etc. based apps to the app stores. While there may be some incentive for app stores to cripple PWAs, and some privacy controls and technical reasons that limit access to some native APIs from web code, I don't think it's true that Apple or Google "don't allow" PWAs. For paid apps, I think the issue is discoverability. App Stores remain the main way people find apps, so publishing to those is often preferred for marketing, instead of saying "click 'add to homepage' to install." I do think there is a place for one or two "PWA App stores" I also think enterprise and in-house apps make a lot of sense as PWAs. Company's internal apps don't need app stores, and can save time and money targeting both platforms with PWA apps users can install from the company intranet.