Whilst the support might be "outstanding" - the discussion is what happens once devices are no longer supported.

You can't release all the documentation just because the entire phone isn't supported. Many of the components come from other suppliers and aren't obsolete, and you can't just reveal all your suppliers' IP.

▲

prmoustache 18 hours ago | parent | next [-]

You could if you had a tiny bit of respect for your customers and obtained the necessary licenses to do so.

	▲	astrange 18 hours ago \| parent [-]
		I don't think anyone has ever accused, say, Qualcomm of having respect for their customers. Much less someone else's customers.

▲

19 hours ago | parent | prev | next [-]

[deleted]

▲

actionfromafar 18 hours ago | parent | prev [-]

They don't have to - just give an option to unlock the device when it's EOL.

It's not a security problem, since they don't support it anylonger anyways!

They could even make it so, that iOS itself refuses to boot if the device is unlocked. That way you can't accidentally have an iOS running that's compromised in some way.

But you can still boot Linux or Android or whatever you want to do to it.

▲

a day ago | parent | prev | next [-]

[deleted]

▲

rswail a day ago | parent | prev [-]

No functrionality is lost when a phone no longer receives iOS updates. All of the existing functionality continues.

Access to new features is not available, and app developers may no longer support updates to their applications.

But AFAIK, Apple apps (maps, music, phone, iMessage etc) on iPhones no longer receiving iOS updates continue to work.

▲

thayne 20 hours ago | parent [-]

Apps that connect to a service over the Internet (maps, music iMessage) could stop working if Apple changes the APIs that those apps use. This is even more likely to happen to third party apps.

You won't get updates to the trusted root CAs, which means you won't be able to visit sites with certificates signed by CAs created or renewed after support is dropped. And your browser will continue trusting CAs that have had their trust revoked.

And as web standards evolve there will be websites that use features and APIs that your browser doesn't support and may break in subtle, or not so subtle ways. And there is no way for you to install a more up to date browser.

And then of course, you won't fixes for any new security vulnerabilities that are found.

So yeah, it's not as bad as getting bricked, but it as also worse than continuing to work as it always has, but with no new features.

▲

rswail 15 hours ago | parent [-]

The original post was about Apple not giving proper support to after-EOL phones.

Saying "could stop working" and "won't get updates to the trusted root CAs" is all future issues.

How long should Apple be required to provide updates, both security/vulnerability and future API support?

Currently, iPhone 6S, released in 2014, can run iOS 15, which received its latest update in 2025. The iOS 15 apps work with Apple's services, some with reduced functionality because it was never in iOS 15.

So that's a 10 year old phone.

	▲	thayne 12 hours ago \| parent [-]
		> How long should Apple be required to provide updates, both security/vulnerability and future API support? If they want to drop support for still functional hardware, they should make it possible to install your own software on it.