Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Other iOS 27 and new iPhones

SMG4fan7236

SMG4fan7236

macrumors newbie
Original poster
I think that Apple wants to achieve a snow-leopard styled approach with this update. But in order to do so, they would likely want to clean up code. This extends to dropping support for not a chip preset (like A13), but the entire home button family (because SE 2 and 3 are rarely used, only 1% of people for each model use them, everyone else uses gestures) and not release a new iPhone this year as there are already many models and a new one only creates more code. However, there is an exception: Devices with an A12 Bionic (including iPhone XS/XS Max and XR) will regain support for iOS 27, and iOS 18.8 will be released alongside iOS 26.7 and iOS 27.0 for those people on those devices who aren’t ready to upgrade yet. For those iOS 26 devices that are still on iOS 18 will be prompted to either upgrade to iOS 26.7 or iOS 27 (depending on choice, the iOS 27 option will not appear for SE 2 and 3). After that iOS 27 update, the iOS 28 update would then support devices with A13 or later (redropping the A12), and release new models (iPhone 18/18 Plus/18 Pro/18 Pro Max/Fold/Air 2).

What do you think?
 
Last edited:
Why drop the A13? It's the only one that really got slowed down. Maybe A14 too.

My SE2 with A13 got really slow, my SE3 with A15 not.
 
Adora said:
Why drop the A13? It's the only one that really got slowed down. Maybe A14 too.

My SE2 with A13 got really slow, my SE3 with A15 not.
Click to expand...
The A13 chip should be dropped because it cleans up old code, and we shouldn’t drop the A14, as we can’t drop two chips at once.
 
What does old code (as it is software) has to do with dropping the A13? 🤔
There is exactly nothing, the A14 could handle but the A13 not, they are not very different in features (unlike A17 Pro to A18, where they went from ARMv8.x to ARMv9).
An cleaner code would help older CPU even more.
So no, I don’t see Apple dropping any A-series this year.

And Apple not releasing a new iPhone this year - we don’t have to talk about it. We know it’s not gonna happen.
 
Last edited:
  • Like
Reactions: TheBeverage, Homme, Tsepz and 1 other person
If iOS/iPadOS27 focus on performance and stability it should be running better on all devices. My take is that all devices that support iOS 26 will be able to run iOS 27. One think that matters a lot is the size of RAM on devices, but Apple don't really seem to care about either one of them. Its more years since release that seem to matter.

If Apple can support the SE2020 that only has 3GB of RAM, and the same goes for the iPad 9, they should in theory also support the XS and Ipad Pro 10.5 that has 4GB of RAM.
 
  • Like
Reactions: Slix and Tsepz
SMG4fan7236 said:
The A13 chip should be dropped because it cleans up old code, and we shouldn’t drop the A14, as we can’t drop two chips at once.
Click to expand...
This, literally, makes no sense. You don’t leave a chip generation on bloated code. You leave it on clean code.
 
Chidoro said:
This, literally, makes no sense. You don’t leave a chip generation on bloated code. You leave it on clean code.
Click to expand...
Reverend Benny said:
If iOS/iPadOS27 focus on performance and stability it should be running better on all devices. My take is that all devices that support iOS 26 will be able to run iOS 27. One think that matters a lot is the size of RAM on devices, but Apple don't really seem to care about either one of them. Its more years since release that seem to matter.

If Apple can support the SE2020 that only has 3GB of RAM, and the same goes for the iPad 9, they should in theory also support the XS and Ipad Pro 10.5 that has 4GB of RAM.
Click to expand...
Cobold said:
What does old code (as it is software) has to do with dropping the A13? 🤔
There is exactly nothing, the A14 could handle but the A13 not, they are not very different in features (unlike A17 Pro to A18, where they went from ARMv8.x to ARMv9).
An cleaner code would help older CPU even more.
So no, I don’t see Apple dropping any A-series this year.

And Apple not releasing a new iPhone this year - we don’t have to talk about it. We know it’s not gonna happen.
Click to expand...
I edited the OP. Reread it.
 
SMG4fan7236 said:
I think that Apple wants to achieve a snow-leopard styled approach with this update. But in order to do so, they would likely want to clean up code. This extends to dropping support for not a chip preset (like A13), but the entire home button family (because SE 2 and 3 are rarely used, only 1% of people for each model use them, everyone else uses gestures) and not release a new iPhone this year as there are already many models and a new one only creates more code. After that iOS 27 update, the iOS 28 update would then support all iOS 27 devices, and release new models (iPhone 18/18 Plus/18 Pro/18 Pro Max/Fold/Air 2).

What do you think?
Click to expand...
The question is why should they drop the support for touch devices? And does that have any benefit for users with gesture based devices in terms of cleaning up code and so on?
I'm guessing there's very little to gain for dropping support for these devices. The benefit might be less work for developers, both Apple and third party when developing OS and apps. Especially in terms of having to design the GUI around older screens with lower resolution.

I hope Apple will focus on extending support for devices as they are lagging behind compared to some of the Android phone companies that's out there. Apple can afford to support devices a lot longer and its only greed that's keeping them from doing so.
 
Reverend Benny said:
The question is why should they drop the support for touch devices? And does that have any benefit for users with gesture based devices in terms of cleaning up code and so on?
I'm guessing there's very little to gain for dropping support for these devices. The benefit might be less work for developers, both Apple and third party when developing OS and apps. Especially in terms of having to design the GUI around older screens with lower resolution.

I hope Apple will focus on extending support for devices as they are lagging behind compared to some of the Android phone companies that's out there. Apple can afford to support devices a lot longer and its only greed that's keeping them from doing so.
Click to expand...
Because barely any people use them, and maintaining only one source of code (gestures) saves them a ton of money. It also improves the update, too.
 
SMG4fan7236 said:
Because barely any people use them, and maintaining only one source of code (gestures) saves them a ton of money. It also improves the update, too.
Click to expand...
Not sure how it saves them a ton of money and improves the update. Touchdevices will be around for some time and are still very much being used. The last devices (iPhone SE) was sold up until last year.
There's also new touch devices, although a bit different, rumored to be released (the fold device).
Many of the gestures for non touch devices can be used on touch devices. They aren't that different from each other.
 
I’d imagine that Apple is going to get a lot of benefit from moving older objective c code to swift / rust more than anything?

Ditto re-architecting older parts of iOS to use more modern techniques.

Then Apple could help everyone who has older phones by not forcing spurious UI animations on them, as these are the things that slow a few years old phone down imho.

If it’s true that we will get a snow Leopard release with ‘no features’ - although integrating Gemini into iOS seems a pretty huge feature to me - maybe their software engineering team will finally have some time to do much of the above.
 
SMG4fan7236 said:
I think that Apple wants to achieve a snow-leopard styled approach with this update. But in order to do so, they would likely want to clean up code. This extends to dropping support for not a chip preset (like A13), but the entire home button family (because SE 2 and 3 are rarely used, only 1% of people for each model use them, everyone else uses gestures) and not release a new iPhone this year as there are already many models and a new one only creates more code. However, there is an exception: Devices with an A12 Bionic (including iPhone XS/XS Max and XR) will regain support for iOS 27, and iOS 18.8 will be released alongside iOS 26.7 and iOS 27.0 for those people on those devices who aren’t ready to upgrade yet. For those iOS 26 devices that are still on iOS 18 will be prompted to either upgrade to iOS 26.7 or iOS 27 (depending on choice, the iOS 27 option will not appear for SE 2 and 3). After that iOS 27 update, the iOS 28 update would then support devices with A13 or later (redropping the A12), and release new models (iPhone 18/18 Plus/18 Pro/18 Pro Max/Fold/Air 2).

What do you think?
Click to expand...
You basically make two assertions:
1. Apple can improve their code by removing support for some features.
2. Apple will not release a new iPhone this year.

Regarding #1, I have seen cases where removing code broke things, because there was an unexpected side effect (a latent bug) in the removed code that caused other code to work properly. Sometimes the safe approach is to leave things alone (let sleeping dogs lie).

Regarding #2, I think there's zero chance of that happening. Unless the sun exploded. Or a giant asteroid hit. Or something similar that's well outside the scope of Apple's planning and execution.
 
chown33 said:
You basically make two assertions:
1. Apple can improve their code by removing support for some features.
2. Apple will not release a new iPhone this year.

Regarding #2, I think there's zero chance of that happening. Unless the sun exploded. Or a giant asteroid hit. Or something similar that's well outside the scope of Apple's planning and execution.
Click to expand...

Lol, yep. Unless Samsung, Google, et. al. stop updating their phones annually, Apple will continue to release yearly.
 
  • Like
Reactions: Tsepz
I made this suggestion with Apple (about the SE 2 and 3) and they thought it was a great idea:
IMG_0279.png
 
  • Haha
Reactions: TruthWatcher412, Homme, Tsepz and 1 other person
iOS 27 should not drop the A13 chip, and since Apple is probably releasing the iPhone Fold series they should probably drop the SE 2 and 3 models to clear out home button code to make way for the new standard. Do you agree?

Note: This reply was merged from another post, so pretend this is the OP, forget posts #1-18
 
Last edited:
What does the home button have to do with the iPhone fold???

You know that there’s an specific image of iOS for every iPhone model, right?
 
  • Like
Reactions: Slix
SMG4fan7236 said:
Maintaining three different architecture code can clog up the OS
Click to expand...
I'm not an iOS developer, but from what I understand about developing iOS apps over the last 10 years or so, is that most apps use an automatic resizing for UI elements across different sizes. This is why making an iPad app from an iOS app is very easy to start doing, and going from an iPad app to a Mac app is the same way. Having a 4.7" screen in the mix isn't making things that much harder to develop (especially for Apple, who made these phones and know them and their differences well).

I completely disagree that Apple should drop the SE (2nd or 3rd gens). The 3rd gen was available until 14 months ago and runs the same A15 chip as the iPhone 13 and 14, and is less than 5 years old. The A13 in the 2nd gen is still a solid chip as well. I see a ton of SEs out in the wild still.
 
Slix said:
I'm not an iOS developer, but from what I understand about developing iOS apps over the last 10 years or so, is that most apps use an automatic resizing for UI elements across different sizes. This is why making an iPad app from an iOS app is very easy to start doing, and going from an iPad app to a Mac app is the same way. Having a 4.7" screen in the mix isn't making things that much harder to develop (especially for Apple, who made these phones and know them and their differences well).

I completely disagree that Apple should drop the SE (2nd or 3rd gens). The 3rd gen was available until 14 months ago and runs the same A15 chip as the iPhone 13 and 14, and is less than 5 years old. The A13 in the 2nd gen is still a solid chip as well. I see a ton of SEs out in the wild still.
Click to expand...
Most treat the iPhone 11 more useful than both as most have switched to gestures, look it up
 
SMG4fan7236 said:
Most treat the iPhone 11 more useful than both as most have switched to gestures, look it up
Click to expand...
I had an SE 2nd gen for 5 years before getting my 16e. I understand the differences. I don't think that has anything to do with how long Apple will support each of those models though.

And of course a lot of people would prefer the features a phone that was nearly 2x the price offers. I actually somewhat disagree in some cases: Control Center is harder to use on a larger phone where you have to scroll down from the top corner rather than up from the bottom of the screen.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back