this post was submitted on 12 Jul 2023
2328 points (99.1% liked)
Technology
59590 readers
4961 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It’s up to individual developers what the minimum OS version they support for their app is. If you have previously downloaded an app and the minimum version is raised above the version you are running on your device then you can still download the most recent version that supports your device
Yeah, what happens is that it takes effort to keep supporting multiple OS versions. iOS has a history of users being like 90% on the newest OS every time there’s a major update, so a lot of companies only support one previous version beyond the current.
Android is a different matter. It has always been a fragmented mess and new OS adoption has always been very slow (it’s faster nowadays though). Because of that Google maintains a set of libraries that make sure Android features work the same way across multiple versions, which eases the burden on developers.
The problem is all of these apps are using proprietary APIs to communicate to centralized backends, which then deprecate the APIs and the old versions cease to work. Back when software was largely communicating over standardized protocols it was feasible to run an old version of software for years after it had been stopped being maintained, but protocols don't make money, APIs do.
I developed and shipped iOS apps, and what you wrote is actually incorrect.
Apple does not allow developers to put on the app store applications built targetting an iOS version below a certain point.
Also Apple controls the build environment for applications which are listed on the App Store: you have to build and push the app for the store on Xcode (contractually and enforced cryptograhically) and it even has to be running on a Mac computer (contractually).
So it's not up to individual developers what the minimum OS version they support for their app, at least not if they want to be able to distribute it via the App Store (which is the only way they can be distributed for non-rooted phones).
Absolutelly, lots of devs just go along with the Xcode defaults (which by the way, are a soft push by Apple) and build against a very recent iOS version, but those who want to support really old iPhones aren't allowed to.
But why should I have to have downloaded the app previously? The app version for the previous OS version was already published at some point. It's definitely available and it would definitely work on the device. All they have to do is allow you do install it. But they explicitly refuse so you'll buy a new device. Which is forced obsolescence by definition.