And you are never going to get anyone on your side with ragebait like this. Even if you don’t intend it that way, you must know this is how it’s coming off.
I get it, but how can I interpret the same situation? Like you said, it is one thing entirely when it is forced.
This certificate issue would be forced… for everyone. Nothing anyone can do.
But the issue, as I have stated, is compounded. I’ve been very critical of devs who repeatedly and pointlessly remove support for no reason at all. I’ve seen conversations where devs discuss how soon they can start requiring iOS 26 minimum. I’ll be extremely harsh with the criticism when I see that.
But why are they able to do this? Well, because adoption has always been massively high.
And like I said, I don’t think most updates are forced… do you? Maybe I’m wrong. Maybe the prevalence is higher. Maybe people have more issues than I think and they ask support and support tells them to update. Maybe more people go to Apple Stores for repairs than I think.
But I think we both know this isn’t the case.
Devs requiring iOS 26 within a month of release and eventually forcing even the most reluctant (me, if you like) to update or upgrade, even Apple’s own policy, and all of the people who remove support so quickly for no reason at all would stop immediately if adoption plummeted.
This certificate issue, if it comes to realisation, obviously doesn’t help.
But like I said, I’m harsh because users are partly to blame. If adoption is always so high, how do we expect devs, Apple, and those in charge of determining compatibility to maintain long-term support for many iOS versions? Those in charge of iOS development have said it many times: I’m not going to support iOS 15 today if 0.3% of my userbase runs it.
How do we expect Apple to care more about older devices? iOS 26 is proof. “Just impact older devices in a way you haven’t done for years with this redesign. We know people will install anything and everything we put out anyway”.
Of course, the alternative is this thread: just botch the certificates and force it anyway, which is planned obsolescence and it’s what we’ve been criticizing.
But even if this weren’t the case, Apple doesn’t even need this. They can severely impact devices and people will update regardless, which removes the incentive for devs to support older versions, and which removes the incentive for Apple to care at all. And it removes the incentive of Apple ever caring about this certificate, too!
Many people have called this planned obsolescence to incentivise upgrades. I say maybe, but is it? Like I said, people update anyway!
In early 2023, when iOS 16 was current, only 8% of iPhones ran iOS 14 and below. 72% ran iOS 16 within three months of release. Of ALL active iPhones. 8%. iPads had a similar figure, 10%. It drops to 4-5% for iPhones released in the previous four years (I’m assuming that includes the Sept 2018 release of the iPhone XS/Xʀ maybe? I don’t know).
By May 2022, 99% of iPhones launched in the previous 4 years ran iOS 15 or 14. Leaving only a small fraction of Xs/Xʀ/11 on iOS 12 or 13.
For compatibility reasons, you definitely didn’t need to update an iPhone 11 from iOS 13 to iOS 15.
So after seeing these numbers, honestly, tell me, because I can’t see it and I’m trying: how do you want me to respond to a complaint that says:
“I’m a long-term iOS user. I updated to iOS 26 on whichever iPhone. I saw that the beta was rough, but I thought maybe with the official release it would get better. Battery life is now 40% worse and I can’t downgrade. Liquid Glass is horrible and consumes too many system resources. iOS 15 had destroyed my iPhone 6s, iOS 17 was rough on the Xʀ, and it’s now happening again”.
You knew… and you updated anyway? How should I respond?
Apple and devs get away with these issues because adoption is too high. There’s no incentive.
An absolutely fascinating definition of “doomed” you must have.
Really? Your phone updating from 2025 software to 2027 software is causing you to feel “doomed”? I wish my life were that simple.
It’s a figure of speech within this context. Of course, ultimately nothing of this matters at all.