android

You can self host a Gotify server (single file executable, web interface), install the app, set it to connect to the server on the local network. Sending a message is as easy as a curl to the server. It will show up in the apps. https://gotify.net/ https://github.com/gotify/android The problem is that there is no iOS app. You could use the browser there but maybe ntfy would be a better fit (Android + iOS.)

There clearly is a need. It needs to be as easy as possible to switch away from Google, or developers won't do it. Additionally, an ecosystem where each developer is encouraged to go wild and implement their own notification system is not ideal. Sure, some of them will be competent enough not to deplete the user's battery within a few hours, but others will not be, and each individual app that does this contributes to battery drain in a tiny way, which adds up. > Many platforms before Apple/Google worked like this Mobile devices are an entirely different beast with strict battery life and data usage requirements. Another factor to consider is that Android will kill long-running background apps unless you disable battery optimization for said apps through a convoluted process (even if you show a persistent notification). [1] It would be re

I either do not have this issue, or it doesn't show up for me on the battery usage page. Are you sure it is widespread? (I have no GAPPS, LineageOS 17.1 -- on Galaxy S4). With that said, there is some work being done towards a FLOSS replacement for firebase [1]. Gotify can be used as a backend [2], among others ([3] too, I think). Not ready for prime-time, but almost, and development started pretty recently (mid-December). [1] #openpush:bubu1.eu (https://matrix.to/#/!ajsXAmvYUOjfmMJnGJ:bubu1.eu) [1] https://github.com/UnifiedPush/UP-spec/blob/main/specificati... [2] https://github.com/gotify/android/tree/unifiedpush [3] https://github.com/NoProvider2Push/android