Except everyone misuses such a thing, privacy gets violated, often don't test well for battery in many different conditions, and then users end up with a shit experience yet don't have the technical expertise to understand why (or which app is causing the problem). Android is particularly difficult since you can have a service running without an app present, so disabling it isn't very intuitive.

I think Apple has done a better job at this balance by not letting people shoot themselves in the foot at the cost the odd useful service not being possible.

I assume you can cite no evidence that your battery charging regimen makes any difference whatsoever.

I wonder if you could get the same effect by turning off only some of the Now cards. Perhaps a few of them are responsible for the majority of the battery usage.

It would be a shame to have to turn off all of them. I found most of them to be useful.

What on earth are you talking about? All of those things you listed as impossible will still be possible.

All Google did is restrict what apps can do in the background, and announced that there will be further restrictions in the future: all background tasks will have to be done through the JobScheduler API.

This does not prevent apps from doing stuff in the background, it just prevents them from doing whatever they want, whenever they want -- they will have to follow the proper procedure.

This is basically what iOS has done from the start.

If you don't see the app in front of you, iOS will very quickly kill it if it has any background tasks.

It's a leaky abstraction, but honestly I like the implicit promise/guarantee between the scheduler and the user.

I only get annoyed when I want some batch task like uploading photos, but even then it's not too hard to leave the phone powered on and unlocked on my desk until the photos upload...

Please provide a link to this if you can.