Yes, I used web sockets for Signal for a while. It drained 30% of my battery when the phone sat idle for a day. Absolutely bonkers. Made the phone almost unusable so had to revert to FCM or disable notifications.
Comment on ICEBlock climbs to the top of the App Store charts after officials slam it
NotMyOldRedditName@lemmy.world 1 week agoIt’s actually not possible to build a push service like FCM or APNS on Android and have it function at the same level as FCM. FCM has special permissions to bypass certain stages on the device to ensure message delivery that nothing else can match.
The best you can do is approximate it with an always active websocket and a foreground service always running with battery optimizations disabled, but good luck not having that foreground service shut down on occasion as well. Devices are hostile to them for battery saving purposes.
bent@feddit.dk 1 week ago
NotMyOldRedditName@lemmy.world 1 week ago
Ya, it can be brutal on battery.
I worked on an app once where delivery was critical, so we gave them the option of the active service+websocket, but for them the trade off was acceptable.
Pushes can be pretty flakey given all the shenanigans OEMs do on the device, even when marked as high priority correctly.
Zak@lemmy.world 1 week ago
It’s true that FCM will result in more reliability and a better UX than other ways to implement notifications. Doing something else is still the right choice for certain use cases, such as those where privacy or keeping the entire codebase open source are top priorities.
NotMyOldRedditName@lemmy.world 1 week ago
Ya, for sure. My beef was just with people saying you can roll your own, but glossing over the reduced user experience and reliability if you do.
With those trade offs it’s absolutely doable.