this post was submitted on 05 Dec 2023
79 points (100.0% liked)
Technology
37727 readers
592 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you use on android apps from the playstore, most apps are built to relay their notifications through Google's Firebase Cloud Messaging (FCM), so they don't have to have a background notification listeners running 24/7. It also means less overhead from multiple notification listeners from every app having its own. So yes, if an app is built on top of google play services, it requires "google play services"
https://en.wikipedia.org/wiki/Firebase_Cloud_Messaging
If an app says it doesn't rely on google play services, it uses an alternative notification listener or websockets, which might not be as effective, because Google is inbuilt and won't kill its own apps, the scale of its infrastructure, and its habit of listening on people's activity.
Add in Androids habit of killing background services, and you don't always get your notification when the app isn't in the foreground.
Even Signal from Playstore uses Google Play Services for notifications.
https://old.reddit.com/r/signal/comments/g217a6/what_can_google_glean_from_signal_using_fcmgcm/
There is also an alternative push protocol called UnifiedPush, but not many of the popular privacy focused messengers care to implement it.