4 ms·

Thanks for your reply and time. I noticed UnifiedPush and your efforts there and I am curious. My summary after a brief glance is UnifiedPush will not achieve

by throw14082020 5y ago

Thanks for your reply and time. I noticed UnifiedPush and your efforts there and I am curious. My summary after a brief glance is UnifiedPush will not achieve anything useful, for the same reasons: iOS and Android push notifications are locked down. For example, sure, Android is OSS, but most of the functionality is provided by proprietary apps or Google Play Services. This results is challenges today, but further challenges down the road (App Store rules/policies change, stronger enforcement). About the battery usage, this is always a hard question to answer. 4% is very low, which seems good. But how could you measure that effectively? Perhaps if the connection is good, it might take 4% battery over 17h of "use". But could this be worse if network is intermittent (i.e. realistic conditions)? Or lots of data being used (or *abused*).

binwiederhier 5y ago
Yeah I mean it is what it is. We can all only work on the space that exists. The big boys control the market and the eco system. One battery saving idea: there is a ticket to let the user control the interval at which the topic is polled. Right now it's obviously a persistent connection. But likely polling every 5min may consume less battery.
altantiprocrast 5y ago
As binwiederhier said 'it is what it is' with proprietary platforms. However, you can still avoid going through Google now for the apps that do already support UnifiedPush Additionally, supporting UnifiedPush (code and adoption by app devs) is supporting: 1. Non-google app stores (e.g. F-Droid with it's great selection of FOSS apps) 2. Google-free distributions of Android 3. Linux phones The above amount to a small but non-trivial community, but imho supporting (or participating in) them ethically is something I like.