That's not how long they will provide software support. It's how long you can get a hardware repair. Some "vintage" products will get current software support but not others. Some products have lost software support before even reaching "vintage" like the first Gen iPad.
That page shows "vintage" products, which is a category they apply after "5 to 7 years". It describes replacement parts and (bought) maintenance service in store locations.
They don't state how long they will provide software updates.
I like to keep phones a long time. Before I finally slotted in a sketchy new third party battery, my last android would suddenly shut off at anywhere from 15-30℅ battery remaining because of the voltage drop. I think they deserve a pass for that "scandal".
The timestamped part of the video shows an iPhone 15 and 17, both on iOS 26.3. 45% on the iPhone 17 and 25% on the iPhone 15.
Only the iPhone XR in that test is on iOS 18. It scored behind all of the models on iOS 26.3 except for the iPhone SE. But that's not a useful comparison because who knows what condition the XR's battery is in at this point, and nothing else ran on a comparable iOS version.
Not sure what point you were trying to make with that video, but it doesn't really demonstrate cross-version battery performance.
They started throttling devices based on battery age after "Batterygate" in 2016, after a wave of news that their phones were suddenly shutting off on high load because the batteries terminal voltage dropped. They do not "artificially slow down before a new release".
The were sued because in their typical arrogance, they neglected to _tell_ people about that. They did not lose, they settled a class action suit.
As a result, they made battery management and state a lot more transparent in iOS, as they should have done in the first place.
Claiming malicious planned obsolescence, as you did, requires facts not in evidence.
Of course they did. My iPad 2 worked perfectly up until iOS6 and crawled to a screeching halt after upgrading to iOS7. Constant lags, freezes, sometimes even crashes of the same apps which worked fine a week before. And to protect consumers even more, Apple blocks firmware downgrade, despite old version working just fine for years later.
Try iOS 26, you'll see what it means in practice, you will get a phone with worse battery life, slower operating system and no path to downgrade, only way is to upgrade your phone to the next big thing.
If it's not malicious, then it's gross incompetence, but at the end of the day, it will still eventually require to purchase a new Apple device, when a downgrade would have been enough.
It's a long-term issue, because even if it will get fixed in two years, then the battery damages due to severe drain are permanent, and this is to be paid with your pocket, or again... upgrade to a new iPhone.
It's not the first cycle like this, slower software is deployed to all iPhones, older iPhones lag, and you have to purchase the fresh new iPhone.
==
"Apple implemented unfair commercial practices", the Italian competition authority said in a statement (after fining Apple).
The companies encouraged users to upgrade operating system software but did not make clear the increased demands that new software would make on smartphones, according to the authority.
This "caused serious malfunctions and significantly reduced performance", which provoked users into upgrading their devices, the authority said.
https://www.bbc.com/news/technology-45963943
==
This is about the generic software updates.
The main issue is that you have no path to downgrade, no way to use your own OS, and your only choice is to hope for an update from Apple that will revert back your device to its normal way of working, or, purchase a new phone, which won't have this issue.
It's literally impossible that they have not noticed, so if not planned obsolescence, at least, it is intentional degradation of existing products (or that their team is not able to notice...)
It's rather the other proof around that we would like to see, that Apple did not know the impact of what they are doing. If they knew, you know what it means.
> They did not lose, they settled a class action suit.
I mean... settling means you lost, almost by definition. You were sued and then paid the person who sued you. Settling is the result of almost all lawsuits where the company knows they were at fault - why would you go to trial if you know you're going to lose?
Now, don't get me wrong - your overall point could still be correct. Many companies who still do believe themselves to not be at fault, offer a settlement purely for the reason that it's cheaper in terms of legal fees (or perhaps less of a PR nuisance, or just generally lower-risk) than going to trial.
> I mean... settling means you lost, almost by definition.
No, since "settling" is something both sides do, if it were losing, it would be both sides losing.
Settling is a decision to compromise to mitigate the cost of litigation (and in the US, which does not have loser pays as the default rule, that can be quite expensive even if you win) as well as the risk of loss. You can’t really characterize it as being more "winning" or "losing" for anyone one party without a much more detailed consideration of the specific terms and the expected costs of litigation, etc.
> You can’t really characterize it as being more "winning" or "losing" for anyone one party without a much more detailed consideration of the specific terms and the expected costs of litigation, etc.
Yeah... you can. The party suing received $500 million. That's a win.
Yes, a settlement has to be agreed on by both sides, but that doesn't mean the party suing didn't win. It just means that, maybe they could have won more.
Where you and the parent commenter are correct is that, the result of this case is not the same as a court verdict regarding the legality of Apple's conduct. That part true - if we're talking about "was Apple truly intentionally killing their phones to get you to buy a new one", the outcome of the case says nothing about that.
But to make a statement like "they didn't lose, they settled" is just misleading. Almost every company that has ever done something illegal settled, that's not an argument either. This case had at least enough merit to spook Apple into coughing up over half a billion dollars ($500 million to the class action and $100 million to the coalition of state attorneys general who sued Apple for deceptive practices). (Again, not proof of guilt but at least evidence of the claims having some merit.) In the grand scheme of things they definitely lost.
That is a gross misrepresentation of the situation. Old batteries' internal resistance rises and they become unable to deliver high current. If you try, thanks to V=IR, the output voltage will droop and you'll brown out. Limiting CPU speed prevents high current draw and random device resets. The alternative was to let it run fast and have it randomly reset under load even when battery is 50% full.
All of this is only relevant cause apple devices are often used for so long after release (5-7 years, this message typed on a 5 year old iPhone) [1] (random source, more available on google.com) while statistically few android devices last long enough in consumer pockets for this to matter (2.5-3 years is average)
With the hiring 1111 interns thing, I think these companies (amazon as well) need to realize this is doing anything but inspiring confidence in those interns. Instead of being excited about going there, more of them would opt to go elsewhere instead of returning full time, or if they do return full time they'd be in fear of being let go next.
Hey, thanks for the pointer. Had I known this, I would have used codex (as a matter of fact, I have never used it before and this prompts me to use it if I can get something like this much quicker with codex). I think making codex copy this for a new content will be much easier now. The issue was with making things the way I exactly want, the exact intuition, the exact primers, and the exact visuals to drive the point home.
Woah very cool, yeah I think the cards and heading/subheading structure is very similar to what codex outputs, but I can tell the different visualizations definitely require your own personal touch
It's covered in the first 10~20min or so of the game, and is really a minor side point.
Off topic, put P5 as a game doesn't really care about spoilers much, there is one specific story telling gimmick that will screw with you if you're really sensitive to these kind of things.
