If you’re an iPhone user still addicted to Flappy Bird, be ready to experience withdrawal symptoms.
When Apple launches iOS 11 in September, the company will drop support for old 32-bit applications—which is most apps released before 2014. Apps that haven’t been updated by their developers to run on the more efficient 64-bit architecture will cease to work
That’s true, but this article is also completely ridiculous in its conclusions. Here’s one of the solutions that Nemati suggests:
One obvious move: Create an emulator. By creating what amounts to simulators of old iOS versions, Apple could keep its past alive indefinitely. It’s something we saw recently when Nintendo released NES Classic, a replica of its stocky first gaming system loaded with 30 cherished early games. At 2.3 million units sold, it’s a good example of an emulator being used to make a quick buck (or more) on the back of nostalgia.
Emulating the Nintendo Entertainment System is easy today on low-powered, cheap, hardware. The Classic Edition kind of made sense for Nintendo as a product, but it is unlikely that Apple would ever release something similar.
Planned obsolescence is Apple’s modus operandi. It needs to keep customers buying new iPhones with updated specs. It’s unfortunate for consumers, who may have grown attached or even paid for these soon-to-be-defunct apps, and a shame for the creators who may see their work disappear.
The idea that Apple wants people to be unhappy with their devices on a schedule is almost as ridiculous as the idea of the iPhone Classic. Would you continue to buy things from a company that make you unhappy? I think you should replace things when they no-longer meet your needs or when there are new features that would dramatically change the experience of using that object in your life.
I agree that there should be some effort to archive these old applications, Apple is rich enough to do something about it, but it is going to be difficult to do that in today’s software environment.
Here are some of the software and hardware hurdles anyone who wanted to archive old iOS software would have to overcome:
- What’s the definitive article? With desktop software and older console games you could pack something up in an ISO or a copy of a cartridge’s ROM and say “this is the definitive article.” That’s difficult to do with networked software that is constantly being updated. You might say that the final version of the software released to the public by the original developer is the definitive article, but I bet some people would want a prior version because it did something differently, or the first version because it represented the most raw and original idea the developer had.
- An iPhone Classic that is running an out-of-date version of iOS for using old applications would probably be inappropriate for a general audience as it would lack modern security and networking features for accessing any data online. Any exploits that enable jailbreaking also enable bad people to do bad things to that device.
- What about the iPad, would there have to be an iPad Classic Edition? An Apple TV Classic Edition? An Apple Watch Classic Edition?
- Could you imagine Apple going on stage during an event to try and explain a custom version of the iPhone that exists solely to run historical software? “Here’s the iPhone Classic, it only runs iOS versions up to 10.” It would confuse their messaging around whatever iPhone they’re actually trying to sell. That’s not our problem as users and developers, but it’s another reason why they would be less likely to have anything to do with such an effort.
- This old App Store. They’d also have to maintain an older version of their app store and review software updates for those 32bit apps that couldn’t be transitioned to 64bit.
- Users would be frustrated when something doesn’t work right because an underlying piece of infrastructure is gone like an API server for logging into games.
- Developers who are still around would be stuck attempting to support versions of apps that they haven’t worked on in years. Is every app in this Classic App Store going to have a “probably unsupported” label on it?
- Apple still needs to encourage developers to transition to 64bit. All of that infrastructure would have to exist while they’re also encouraging developers to update old apps to 64bit.
- Apple has offered emulators for desktop software to run during transitions in the past, but desktops have the power and the room to explain what is going on with older software running in emulation or virtualization.
- I’m not sure if a modern iPhone even has the potential performance to virtualize an older device without destroying the performance of modern software running on the same device at the same time.
- How do you explain what is going on in any way that makes sense to a regular person?
Honestly, I think the only people in a position to solve this are software pirates, and they are still going to have a difficult time trying to do that for all of the games and other software out there on mobile platforms. Any other group would have hurdles that are too large to jump over in keeping this old software alive. It’s a problem for every modern online software distribution mechanism. Sony’s and Microsoft’s online stores for the PlayStation and Xbox both have this issue. Nintendo’s laughable online shop couldn’t even give you access to software you purchased previously without calling their support line and begging for it until they released the Switch and you’d still lose your game saves if your Switch is lost, broken, or stolen.
Software preservation is well and truly fucked.