iOS 11 removes support for 32-bit apps, renders legacy iDevices obsolete

Shawn Knight

Posts: 15,296   +192
Staff member

Apple on Monday treated developers and audiences around the world to a sneak peek of its next generation mobile operating system. While not exactly groundbreaking, iOS 11 does bring some useful features and improvements to the table like peer-to-peer Apple Pay and a redesigned Control Center.

Unfortunately, those with legacy devices won’t get to realize any of its benefits.

You see, iOS 11 is only compatible with devices running 64-bit processors. Apple’s A7, which debuted in the iPhone 5S in 2013, was the first Apple mobile device to utilize a 64-bit processor (such has been the case for all subsequent launches as well). This means that phones and tablets running Apple’s 32-bit A6 (and earlier) chip like the iPhone 5, iPhone 5C and the fourth generation iPad won’t be able to use iOS 11.

Similarly, apps that don’t yet support 64-bit architectures also won’t run on iOS 11.

Apple in early 2015 mandated that all new iOS applications and updates must include 64-bit support. This requirement didn’t, however, extend to apps already on the App Store. What this means is that apps that are still in use but haven’t been updated since 2015 must be infused with 64-bit support in order to run on iOS 11.

To see if you have any 32-bit apps running on your iDevice, head over to Settings -> General -> About -> Applications and check the App Compatibility list.

Screenshot via 9to5Mac

Permalink to story.

 
Funny. In desktop environments, 32-bit programs have no issue running in a 64-bit OS. Is iOS an operating system where 32-bit and 64-bit apps create friction when run together? If not, I don't understand what Apple could gain from enforcing 64-bit only. Wouldn't this just limit a huge number of existing apps?
 
Funny. In desktop environments, 32-bit programs have no issue running in a 64-bit OS. Is iOS an operating system where 32-bit and 64-bit apps create friction when run together? If not, I don't understand what Apple could gain from enforcing 64-bit only. Wouldn't this just limit a huge number of existing apps?

It's a requirement to make you purchase new equipment, just like the jump from PowerPC to Intel, and EFI 32 to 64. It's how Apple makes money, as they're a hardware company and make older things obsolete. Microsoft is primarily software first, so they phase out Windows 2000 / XP / Vista and force you to Windows 8 and 10.
 
Funny. In desktop environments, 32-bit programs have no issue running in a 64-bit OS. Is iOS an operating system where 32-bit and 64-bit apps create friction when run together? If not, I don't understand what Apple could gain from enforcing 64-bit only. Wouldn't this just limit a huge number of existing apps?
Not a huge number - they have been setting themselves up to phase out 32-bit for a long time now. Most apps are 64-bit compatible. Particularly recently maintained ones.

And I can understand the want. They eliminate the cludge of a 32-bit mode running in a 64-bit OS. They can remove that component of the OS and the free the resources it occupies. 32-bit API is also probably dated and dodgy compared to the newer cleaner 64-bit version.
 
Back