> throttle their own devices to manage power/battery trade-off?

With modern power management, the system constantly makes decisions on throttling up and down at the sub-millisecond level, balancing performance, power usage, battery lifetime and thermal constraints which affect component lifetimes. There are probably hundreds of combinations of criteria it uses to decide what to do and when.

This has nothing to do with Apple versus Android or open versus closed. All modern phone systems do this, the Android device makers face exactly the same issues. There isn't a single modern smartphone on the market that doesn't throttle the CPU in order to preserve device lifetime, because that's a big part of what thermal management is about. It's why people overclocking their CPUs are taking a risk. That running older batteries hotter and harder degrades them rapidly and risks device outages is simply a fact of physics. Painting these practices as 'planned obsolescence' is, frankly, incredibly ignorant.

Because for >80% of users, they DO know better.

I can try to start this conversation with my grandmother, but as soon as I say "throttling," her eyes glaze over - and just says "can you do it for me?"

Apple is trying to cut out that middleman. Even Android is getting on the "smart battery management" AI train, as no one outside of experts wants to do this.

Then don't use the word "throttling". Just say Apple made it slower to make the battery last longer.

There isn’t, because most users actually don’t know how to do things like regulate speed vs performance, and the whole point is that the throttling is dynamic to prevent shutdowns. What do you think the control should look like? An always present display of voltage levels, temperature, and throttling status?

And what do you mean - ‘make things as bad as possible to prove our point’? Where is that coming from?

I think on Android if you show developer tools, you can set the CPU governor mode.