The problem is that this requires a long running background connection.
And guess what Google tried to kill for battery saving purpose since a long time (long running mostly sleeping background processes). But then on Google in difference to Apple it's still possible (but less reliable) with the right setup and fully possible with a "proper" de-googled phone.
So depending on your setup you might either:
- not get notifications
- get them unreliable
- only get them if the app is open
- get them just fine
Also this might change from app to app, there clearly will be apps which will not have any 3rd party notification broker fallback, but given how Google doesn't have 100% delivicery guarantees they still should have (potential delayed) message syncing when the app is open.
Sometimes I get notifications, sometimes it may take hours for me to get the notification.
I rarely use instant messaging for important things, and when I do, I make sure to check my phone often so I don't miss the messages.
Is this stupid? Maybe, but I'm not going to install Google's closed source crap on a device that I carry almost everywhere. If that means I become a social pariah, then so be it.
Sounds heroic, but maybe does not help anyone? And if you really cannot tolerate closed source, than what kind of hardware do you use? As far as I know, they are allmost all closed and locked.
Pine64 is a fresh breeze, but they are also not free(nor stable) yet.
My workaround is simply, that I have a mobile, where I can remove the batterie, then I know, it is turned off.
Most importantly your app (and server) needs to be build to be able to fall back to a 3rd party message broker. But the common fallback is to just sync messages from time to time in background if the app runs as it's "good enough" for the case Google is temporary down or not available or you are one of the (from the App POV) view people which de-googled their phone.
