I remember when the microsoft app store on windows 8 were a bunch of websites wrapped into an app. It really lowered the quality of apps and the overall appeal of the windows app store.
That being said, how will PWAs get around the apple and google requirements that apps downloadable from their stores where they mention apps can't just be a website wrapped into an app?
> "It really lowered the quality of apps and the overall appeal of the windows app store...how will PWAs get around the apple and google requirements that apps downloadable from their stores where they mention apps can't just be a website wrapped into an app"
Fair question. Google is implementing a new quality bar for PWAs in their store. See this post[0] for details.
Microsoft also is doing work in this area. We're not ready to share details, but will likely in the coming months.
With PWABuilder, our goal is to help devs build quality PWAs: ones with rich offline experiences, measurably great performance, and apps that are functionally rich. This implies something more than e.g. your resume packaged as a PWA. Towards that end, PWABuilder analyzes your PWA and gives you feedback on capabilities: encourages use of our rich web components[1], helps you build a great offline experience[2], and more. Whether your app is functionally useful (i.e. not just a brochure) is a quality bar left to app stores themselves.
That being said, how will PWAs get around the apple and google requirements that apps downloadable from their stores where they mention apps can't just be a website wrapped into an app?