Google implemented PWA support years ago into both Android and Chrome, including web push notifications. Apple is the only one that purposely doesn't implement necessary features for PWAs like web push notifications.

Google and Mozilla have supported the web push API for going on 6 to 7+ years now.

Facebook's mobile website works well enough. They keep pushing me to use their lite app, but I suspect it's not in my benefit. The web app is a bit buggy (only the first few photos load on an image post), but there's no reason to think that couldn't be fixed if they tried.

Given the choice, I'd use Facebook messenger in my phone's web browser but they block it.

I don't agree that a native app is a better experience, as it gives less control to me the user.

Maybe it's a better experience for product managers who want to increase my engagement and collect as much information on me as possible.

In my interest, too. Pay attention to non-geeks using this "feature" and it's clear that web push is the 3rd party toolbar[0] of the modern web. Crap they enable by accident, then don't know how to get rid of.

[0] Ask someone who worked with computers in the late 90s and 2000s if you don't get the reference.

PWABuilder already has a "publish to Google Play" feature: https://blog.pwabuilder.com/posts/microsoft-and-google-team-...

We work with Google -- and even sync with them monthly -- on this platform. They are very cooperative and helpful.

And, PWAs published to Google Play can do push notifications and anything else PWAs normally do, using just standards-based code.

I'm confused, what are Google blocking? iOS famously lacks push notification browser support, but Android's browser and third party browsers on the platform all support it on Android (and have since forever).

Google already supports Web Push in Chrome. Mozilla in Firefox as well. Web Push is only blocked in Safari.

I’ve released a PWA with Capacitor in both app stores with push notifications.