iOS 10.1 beta issues warnings for older, 32-bit apps slowing down your iPhone


The current iOS 10.1 beta update sees the addition of an alert warning users that specific apps – usually older, written in 32-bit code and not updated in quite a while – may slow down their device. It also suggests that the app's developer has to update it in order to improve compatibility.

Apple's idea is to direct users away from apps that still haven't been refreshed with native 64-bit support. The warnings appear upon launching such applications.

Back in late 2013, Apple started urging developers to submit 64-bit applications to take advantage of iOS' 64-bit support and the iPhone 5s' new, at the time, 64-bit processor. In 2015, 64-bit support for apps was made mandatory. Thus, the alert mostly deals with pre-2015 32-bit apps that still haven't been updated to comply with the App Store's 64-bit requirement.

Last September, Apple also began notifying developers that apps which haven't received compatibility updates will be automatically removed in a 30-day period if they aren't fixed. The messages, first introduced in the iOS 10 beta and probably coming to users with the iOS 10.1 update, likely are a part of this campaign.

source: MacRumors

FEATURED VIDEO

4 Comments

2. AlikMalix unregistered

This makes a lot of sense actually.

4. TechieXP1969

Posts: 14967; Member since: Sep 25, 2013

How does this make sense? A 32bit app should run equal or better than it would on its native 32bit foundation. When I run 32bit apps on Windows x64, they don't slow down. They either remain the same or gain some speed benefit.. They should not run slower. How can this make sense? Software is not like hardware. If you use slower ram with faster ram, then yes the faster ram will lower it's clock to match. That's just bull. Most of the apps running on iOS are 32bit. Unless Apple is removing support to actually run them properly, then that is the only way. 64bit processors support 32bit apps, because the instructions on the chip, still exist to make them work. The only way a 32bit app won't execute on 64bit, is you would need to remove 32bit support. So it sounds like Apple wants to remove 32bit support from IOS and to drive that, they are no .one going to support some 32bit code, which means the dev needs to fix it or app will not run, because the support for a part has been removed. They have already moved to making it so all new apps need to support 64bit exclusive, but don't ruin the experience in the process. How can you possibly be OK with this? This is as dumb as removing the headphone jack to make room for a larger vibrator. No matter how much money they waste in something so frivilous, haptic feedback is never gonna feel like the real thing. So why waste money on it?

5. iC-118

Posts: 260; Member since: Sep 29, 2016

Wise post.

7. sgtdisturbed47

Posts: 970; Member since: Feb 02, 2012

It's backwards compatible with 32-bit so I dont see the big push for 64-bit only. Primary advantage is access to more RAM but what program on a phone uses more than 3.5gb of RAM? Hell the phone itself has less than that. I don't see the benefit, so I definitely don't see the reason to force it. Any performance advantage the program would have would be negligible.

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at https://www.parsintl.com/phonearena or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit https://www.parsintl.com/ for samples and additional information.