https://support.apple.com/iphone/repair/battery-power
It looks like on some issues, we still have market power.
https://support.apple.com/iphone/repair/battery-power
It looks like on some issues, we still have market power.
"free" battery costs at least $130 for Applecare and it's rarely worth it. Without Applecare, it only costs $30 to replace.
At most you can say they where trying to fix a hardware issue with software which is never a clean solution.
Take it to an Apple store, call Apple support, or take it to any one of your friendly neighborhood repair shops?
> ludicrously high amount
Battery replacement costs:
Google Phones: $79
Apple Phones: $79
Samsung Phones: Nothing 1st party, $50 was the cheapest 3rd party I could find.
This honestly doesn't even seem like that much when the battery itself retails for $25 before shipping. That plus an hour of skilled labor to do the replacement puts us right around $80-$100. And when a new battery extends the life of your $800 phone for another 2 years its hard to say the value isn't there.
That said I don't think 79 USD every two years is ridiculous for a 700+ USD device. It better not take an hour, though!
Then after what could only be described as a media shitstorm Apple responded to the criticism by putting the decision in the user's hands and offered battery replacements for around material cost. I mean $30 is ridiculously cheap when just the battery for my Android phone is $24 before shipping and labor. I'm honestly jealous.
What engineer thought that slowing down devices would be 'transparent'?
Apple engineers slowed the CPU in the phone, in order to keep battery life reasonable, and prevent the phone from restarting when worn batteries couldn't deliver power. Windows does this with laptops.
Apple's mistake was not disclosing it. There an argument for user experience that advocates making the best choice for the user and not over burdening them with options.
Instead, they pushed their users to buy new phones, or pricey fixes for a manufacturing mistake
They did, technically, in the release notes for the update that introduced it. That said, it could (and should?) have been more prominent.