> Also, Google has intentionally crippled Android and background app running, so you have to depend on FCM to deliver notifications, and you can't deliver FCM notifications uf app is installed via apk or fdroid or other third-party appstore.
FCM could indeed offer support for non-play-store apps, but weren’t background apps on Android leashed in because abuse of the capability was rampant and was torpedoing users’ battery life? I remember this being a pretty big Android issue for less technical users and an annoyance to more technical users.
If the user hides it, the app loses background capabilities.
Also, notification area becomes unusable if there are too many persistent notifications. Syncthing, VPN, xmpp client, and you almost have no space for regular notifications, they become stacked.
> weren’t background apps on Android leashed in because abuse of the capability was rampant and was torpedoing users’ battery life?
This should have been addressed by giving the user a capability to determine power usage by each app and either allow it if he needs the app, or restrict background running.
The way it was done is far from adequate. Also, many manufacturers (samsung, xiaomi, huawei) cripple android even further. See https://dontkillmyapp.com
FCM could indeed offer support for non-play-store apps, but weren’t background apps on Android leashed in because abuse of the capability was rampant and was torpedoing users’ battery life? I remember this being a pretty big Android issue for less technical users and an annoyance to more technical users.