tl;dr PWAs are on the brink of being a "thing": technical abilities are accumulating, but it's not clear if the political will to "commit to the web" exists. If you have experience developing native apps, just do that. There's no reason to jump ship and make a PWA because it's not clear if they're going to take off or not.
Google has shown some investment in PWAs on Android with the development of "WebAPKs", a way to manage the installation of progressive web apps through the Play store.
However, this mechanism is not entirely public: Chrome for Android will create a WebAPK when asked to add a PWA to the home screen, but currently you cannot create a WebAPK yourself and list it in the Play Store.
The point I'm trying to make is that while PWAs are slowly gaining technical abilities, Google hasn't yet gone "all in" wrt PWAs being a true form of "app". It's not clear where exactly they're headed; there are some indications that there is a kind of "cold war" between the Chrome and Android teams.[0]
Microsoft has shown much more commitment to PWAs by making them available in the Windows app store. I believe Firefox has some support, and I'm only aware of Safari recently starting development of Service Workers, a necessary component for PWAs.
As far as adoption in the wild:
- Google has created a PWA version of Maps, Maps Go, available in the Play Store. This shows that PWAs are technically capable, but still not "blessed", in that you couldn't make a PWA and list it in the store like that.
- Twitter Lite in the Play Store is a WebView wrapper around a PWA, getting around the restriction I just mentioned.
[0]: https://medium.com/@firt/is-there-a-cold-war-between-android...