Apple held its September event yesterday at 18:00 BST, and for once I came away from an iPhone launch genuinely interested in an iPhone I have absolutely no intention of buying.
The iPhone Duo is real. Apple has finally made the foldable phone it spent years allowing everybody else to beta-test first, and I actually think it looks rather good. It folds out into a 7.6-inch display, has a 5.4-inch display outside, runs the same A20 Pro as the new iPhone 18 Pro models, supports proper side-by-side multitasking and will even get Apple Pencil support later this year. It starts at £1,999, because of course it does.
There were also the iPhone 18 Pro and Pro Max, new Watches and new AirPods. I could go through all of those feature by feature, tell you how many megapixels each camera has and repeat Apple’s battery-life figures, but Apple already has a website for that and I don’t think anybody needs me to make a worse version of it.
What I actually finished the event with were three questions, beginning with the fairly obvious one: where the hell is the iPhone 18?
There is an iPhone 18 Pro. There is no iPhone 18.
Apple announced the iPhone 18 Pro and iPhone 18 Pro Max today. It announced the iPhone Duo. It did not announce the ordinary iPhone 18.
That is not me missing something in the keynote. There simply isn’t one.
Reporting around the launch suggests Apple has split what used to be the annual iPhone release into two parts. The expensive phones come first — 18 Pro, 18 Pro Max and Duo — while the normal iPhone 18, 18e and the next Air are expected in early 2027. Apple itself has not announced those phones or committed publicly to that timetable, so for now we have the slightly absurd situation where Apple sells an iPhone 18 Pro without selling an iPhone 18.
I can understand some of the logic. Apple’s iPhone range has become enormous, and launching every possible variation simultaneously would mean explaining a base phone, an e phone, an Air, two Pros and now a foldable during the same presentation without the whole thing turning into somebody reading a particularly expensive Argos catalogue.
Splitting the cycle might make more sense operationally. From the customer’s side, it is still weird.
For years, September has meant the new iPhone. Not necessarily the one you personally want and not necessarily one worth upgrading to, but there was an extremely understandable cadence: number goes up, normal one appears, Pro one appears alongside it. This year, the number has gone up only if you’re willing to spend Pro money.
If you own an ordinary iPhone 15 or 16 and have been waiting for the ordinary iPhone 18 as your upgrade, Apple’s answer today is essentially to keep waiting. Maybe moving the ordinary models to spring ultimately produces a cleaner release schedule, and I can see an argument for not dumping six phones into September every year. It is nevertheless difficult not to notice that the first half of this new schedule consists entirely of the expensive ones.
Apple has not cancelled the ordinary iPhone, as far as anybody knows. It has just made the ordinary customer wait while the premium range goes first.
Then there’s the Duo
The Duo is the bit I actually found interesting.
I have never been desperate for a foldable phone. They are cool pieces of engineering, but most have existed in the category of technology I enjoy looking at in a shop and then very happily leave in the shop. I don’t particularly want to spend laptop money on something I can accidentally close around a grain of sand.
Apple’s version is annoyingly compelling.
The passport-ish size when closed makes much more sense to me than simply producing another enormous slab. The inner display looks genuinely useful rather than just phone but wide, particularly with two apps running beside each other. Apple has clearly thought about how iOS should adapt to the different orientations, and being able to prop the thing up for video, FaceTime or StandBy without carrying another stand around is exactly the sort of hardware-software integration Apple tends to be good at.
Then I looked at the controls.
On Apple’s own Duo pages, Touch ID lives in the side button and Camera Control is another physical control placed around the edge of the device. Apple also describes the Duo as comfortable to use one-handed while closed.
Which hand?
I have poor dexterity in my right hand
I should be precise here because poor dexterity and simply being left-handed are not the same thing.
I can use my right hand, but not with the same control or reliability as my left. A design which favours controls on the right side of a phone may be mildly awkward for somebody who just prefers their left hand; for me, anything involving precise repeated presses or coordinated movement can be more difficult.
When the Duo is closed, I suspect most people will work something out. Fingers wrap around phones, Touch ID can recognise different fingers and the closed device is relatively small. I am not going to declare a phone I have never touched inaccessible based on product photography.
Opening it is the more interesting part.
You now have a 7.6-inch device built around a hinge. Its defining interaction is physically moving two halves of the phone relative to each other, and Apple naturally demonstrates that with two hands. If your right hand has poor dexterity and your left hand does most of the precise work, how comfortable is that actually going to be?
Can you open the hinge against a surface with one hand? Once it is open, can you rotate it so the hardware controls are more accessible from the left without the interface becoming awkward? What happens to Touch ID in those orientations? How much grip strength does the hinge need? Can you reposition it without relying on the kind of coordinated movement Apple’s promotional material takes for granted?
Apple is, to its credit, very good at software accessibility. iOS has AssistiveTouch, Voice Control, Switch Control, Eye Tracking and a fairly extensive collection of ways to avoid physical buttons.
That helps with the interface. It does not solve the hinge.
AssistiveTouch can replace a button. It cannot unfold a phone.
That is what makes the Duo interesting from an accessibility perspective. A slab phone has physical requirements too, but a foldable makes one of those requirements central to the product. It is not enough for iOS to become accessible once somebody has already managed to get the hardware into the right shape.
Maybe this is completely fine in practice. I have not held one, and perhaps the hinge is light enough to manipulate against your body or another surface without much trouble. There may also be orientation behaviours or accessories which make the whole thing much easier than it appears in Apple’s demonstrations.
I would just like Apple to show that.
“Comfortable to use one-handed” is quite a claim for a device whose defining feature involves unfolding it.
Please don’t make this horrible to develop for
There is another Duo question I have, this time wearing my developer hat rather than looking at it as somebody who might have to physically use the thing.
Please, Apple: do not make developing for this phone a nightmare.
A foldable immediately gives me horrible visions of apps full of branches checking whether the phone is open, closed, half-open, upside down, sitting like a tiny laptop, running one app on each side or doing whatever other pose somebody has discovered five minutes after buying it.
I really do not want this to become the iOS equivalent of writing a website in 2007 and discovering that you now need a separate stylesheet for every screen ever manufactured.
Thankfully, Apple’s developer guidance for the Duo is actually quite reassuring.
Apple says that if an app already uses standard system components and has been built to resize properly, it should adapt to the Duo with relatively little work. The outer display behaves like a compact iPhone layout, the inner display gives you a regular-width environment, and Apple explicitly tells developers not to build a bespoke interface for every possible position of the hinge. Use size classes, flexible layouts, safe areas and the existing adaptive components, and let the system deal with most of it.
That is exactly what I wanted to hear.
An app also runs on the Duo without needing to be recompiled specifically for it, although adopting the newer SDK lets it make better use of the displays. NavigationSplitView, TabView, sheets, popovers and the other standard components have been taught how to deal with the new form factor themselves.
If that works as advertised, lovely. Please keep it that way.
The stuff that makes me slightly nervous is everything outside those standard components.
The Duo has two displays, a folding region which can become a reserved area when the phone is partially closed, cameras in different places depending on which display you are using, asymmetric safe areas and an inner display where the assumptions we have spent years making about an iPhone screen become considerably less safe.
There are new APIs for querying reserved regions when custom interfaces genuinely need to know what space is unavailable, and Xcode 27.1 can simulate the Duo opening, closing, rotating and folding without requiring developers to spend two grand on one just to test their app.
All of that sounds sensible.
It also sounds like exactly the sort of thing that becomes a pain in the arse if your app has accumulated a few innocent assumptions such as “the screen has one rectangle”, “the safe area is roughly symmetrical” or “UIScreen.main means something unambiguous”.
I maintain iOS software. I know how quickly “you only need to make a couple of layout adjustments” can turn into staring at a view at two in the morning asking why it has decided to move twelve pixels to the left on exactly one device.
So this part is less criticism and more pleading.
Please let the Duo remain a particularly weird size of iPhone, from an app developer’s perspective, rather than becoming its own parallel platform that every iOS developer now has to maintain.
Apple’s guidance suggests that is what it wants too. The advice is basically to make interfaces respond to the space they have rather than asking whether they happen to be running on a Duo in some particular hinge position.
That is probably healthy for iOS generally. Apps should not be full of hard-coded assumptions about a particular phone resolution in the first place, especially now that the same SwiftUI code increasingly runs across phones, tablets, Macs, windows of arbitrary sizes and whatever else Apple decides to unfold next.
I just know I am eventually going to open one of my projects in the Duo simulator and discover which assumptions I did not realise I had made.
Please let there be fewer of those than I am imagining.
Oh good, the Apple vs Samsung war is back
Of course, Apple making a foldable also means we get another round of the Apple versus Samsung war.
I use “war” loosely. Nobody is storming Cupertino. Mostly it consists of two enormous companies spending absurd amounts of money making phones and then social media managers posting memes at each other while people online defend whichever rectangle they bought as though their family honour depends on it.
Still, the Duo makes this particular round unusually funny.
Samsung has been making foldables since the original Galaxy Fold in 2019. That first launch was famously rough enough that review units started breaking and Samsung had to delay the release, but it kept going. Seven years and eight generations later, Samsung has done a large amount of the boring, expensive work involved in figuring out hinges, flexible displays, durability and what people actually want a folding phone to be.
Apple has now arrived and announced a passport-shaped foldable remarkably similar in broad concept to Samsung’s Galaxy Z Fold 8.
Samsung’s response was exactly as subtle as you would expect.
Its post-launch campaign included “Welcome to Foldables” billboards and social posts accusing Apple of “reheating our leftovers”, alongside the usual #ItsTimeToSwitch stuff. Reuters’ coverage of Samsung’s response also points out the particularly funny bit: Samsung has spent years building the foldable supply chain Apple is now entering, and Samsung Display itself supplies foldable screens into that ecosystem.
Meanwhile Apple’s pitch for the Duo included John Ternus describing previous foldables as being like two phones awkwardly stuck together.
So yes, they are doing this again.
Samsung says Apple arrived seven years late and copied its homework. Apple says everybody else was doing it wrong and it has finally made the version worth buying.
Somewhere between those two statements is reality.
I do think Samsung deserves credit here. Whatever you think of the Galaxy Fold line, Samsung was willing to ship the strange thing before the category was safe. The company got publicly smacked around when the first one broke, fixed it, came back and then spent years iterating on an idea which most people still considered a novelty.
Apple gets to enter a much more mature market.
That is also very Apple.
The company has rarely needed to be first to a category. It was not first to the smartphone, tablet, smartwatch, wireless earbud or a long list of individual phone features. Apple’s favourite move is to watch everyone else work out which bits are terrible, wait until the technology is mature enough, build its version tightly around its own software and then market the resulting product as though history began on Tuesday.
Sometimes that is irritating.
Sometimes it works extremely well.
The Duo is probably going to be a good test of which one this is.
Samsung has years of experience making foldables, and the Galaxy Z Fold 8 is already a mature product. Apple has the advantage of controlling iOS, its developer ecosystem, its chips and almost every detail of how the hardware and software interact. If developers really can treat the Duo mostly as another adaptive iPhone rather than a separate species, that integration could matter a lot more than whether Apple arrived first.
There is also something slightly absurd about the tribal version of this argument because Apple and Samsung are not actually two isolated kingdoms at war.
They compete brutally in phones while simultaneously existing inside the same enormous electronics supply chain. Apple can stand on stage explaining why its foldable is better than the category Samsung spent years developing while components originating from Samsung’s wider corporate empire help make the thing possible.
Consumer technology is messy like that.
I also suspect that, if the Duo sells well, Samsung will experience the most annoying possible outcome: Apple entering the category may validate foldables to a huge group of people who have ignored them for years.
People who have spent half a decade looking at a Galaxy Fold and asking “why would anybody need that?” will see an Apple logo on broadly the same concept and suddenly decide foldables are the future.
Samsung is absolutely entitled to find that funny.
At the same time, Apple entering the market puts more pressure on Samsung to improve. Samsung has owned a huge chunk of this category without having another company with Apple’s ecosystem and customer base competing directly against it. Now it does.
That is the bit of the Apple versus Samsung “war” I actually care about.
I do not care which trillion-dollar corporation wins an argument on Twitter. I care whether Samsung having better foldable hardware forces Apple to improve the Duo, and whether Apple making iOS work properly on a folding screen forces Samsung to improve what it does with Android.
If they want to spend the next five years publicly taking the piss out of each other while making each other’s phones better, carry on.
That is a phone war I can live with.
Apple also basically Sherlocked Bevel
The Watch part of the event produced another familiar feeling.
Apple Watch Series 12 and Ultra 4 now have Readiness, which uses activity, vitals and sleep to produce a score intended to tell you how prepared your body is for the day. Apple has also introduced Health Age, which tries to place various health measurements in the context of your chronological age. Apple explains both in its announcement of the new health and fitness features.
If you use Bevel, that probably sounds familiar.
Bevel already has Recovery, Sleep and Strain scores, a real-time Stress score, Energy Bank and Biological Age. The app’s entire appeal is taking the large pile of health data an Apple Watch already produces and turning it into something more useful than individual graphs.
In other words, Bevel has been Sherlocked.
Not entirely. Bevel does much more than produce a recovery number, and Apple adding first-party versions of a couple of its ideas does not erase the rest of the app. If anything, Apple putting Readiness into watchOS validates the basic premise: most people do not wake up wanting to inspect their HRV graph. They want to know how knackered they are and whether going hard at the gym today is a stupid idea.
This is also what platforms do. Third-party developers find a useful way of working with the platform, the platform owner sees that people like it, and eventually some version turns up as a system feature. There is a reason Apple has supplied the industry with its own verb for this.
I do not actually object to Apple adding Readiness. If the Watch is already collecting all this data, making better use of it in the operating system is an obvious improvement.
What interests me is where Apple draws the hardware line.
Apple ties its version of Readiness to the new health-sensing hardware in Series 12 and Ultra 4, including much more frequent heart-rate and HRV measurements. That may make Apple’s metric better than anything it could have produced from previous Watches, and with health features there is a perfectly reasonable argument that Apple should not publish a number unless it is confident in what that number means.
But Bevel already produces a useful approximation from data older Watches can collect.
So why does Apple’s version need to be a cliff?
Why not give an older Watch a less detailed Readiness score based on the information it has, while explaining that Series 12 produces a better one because its sensors collect substantially more data?
There may be a perfectly good reason. Apple may have validated its algorithm specifically against the newer sensing system and decided that anything less would be misleading.
The interesting part is that we have seen this pattern before.
On my iPhone.
My Mac can do this. My phone can’t.
I have been using the new Siri AI features for about two months on my Mac mini M4, slightly ahead of the normal release cycle because I’m running Apple’s public beta.
I cannot use them on the iPhone sitting next to it because that phone is an iPhone 15.
Not an ancient iPhone. Not something I found in a drawer with a 30-pin connector attached. An iPhone 15.
Apple Intelligence supports the iPhone 15 Pro and Pro Max but not the ordinary iPhone 15. On the Mac side, support goes all the way back to M1.
That makes the contrast particularly obvious for me because I have already been living with the newer Siri. I know what it is like when it has the extra context and capabilities, because the public beta put those features on my Mac before the final release. Then I pick up my phone and immediately drop back to the older experience.
Same Apple Account, same ecosystem, same assistant, completely different capabilities.
There is a technical reason. The ordinary iPhone 15 has an A16 and 6GB of RAM, while the 15 Pro has an A17 Pro and 8GB. Apple has said from the beginning that running its models on-device depends on memory, bandwidth and Neural Engine performance.
I am not claiming Apple has a secret switch somewhere labelled:
if poor_person_phone: siri_stupid()The hardware requirements are real.
What bothers me is that Apple chose the hardware too.
The base iPhone 15 having 6GB of RAM while the Pro had 8GB was not an unavoidable fact of nature. Apple decided how much memory went into each model. Nobody surprised the company a year later by inventing machine learning. Neural Engines had been part of Apple silicon for years, and Apple obviously knew it was investing heavily in AI before Apple Intelligence appeared on a keynote slide.
A limitation can be technically genuine now and still come from a product decision made earlier.
The Mac comparison makes that especially obvious. Apple is not simply reserving AI for whatever shipped this year, because an M1 Mac from 2020 still qualifies. Apple silicon Macs started with enough headroom that the software could grow into them.
The base iPhone 15 did not.
That is still Apple’s problem.
Bevel makes the question harder to avoid
This is why the Bevel comparison matters beyond the usual joke about Apple Sherlocking an app.
Bevel is a third-party developer working with the health information Apple exposes from hardware people already own. It cannot add a new sensor to your Watch. It cannot decide that the answer to a difficult engineering problem is to sell you next year’s chip. It has to look at the data available and work out what useful experience can be built on top of it.
Apple has a different set of choices.
Sometimes new hardware is genuinely required. My iPhone 15 cannot unfold, and no amount of clever software is going to give it the Duo’s second display. An older Watch cannot suddenly sample a sensor more frequently than the hardware allows.
The murkier question is whether a feature needs to disappear entirely when the old hardware cannot provide the bestversion of it.
Bevel can produce recovery information from existing Apple Watch data. Apple’s new Watch can produce a more sophisticated Readiness score from better data. Those two facts can both be true.
Likewise, perhaps Siri AI cannot run locally on an ordinary iPhone 15 at a speed Apple considers acceptable. That explains why my phone cannot run the full implementation. It does not automatically answer whether there could have been a smaller model, more selective cloud processing or some reduced version of the experience.
Apple may have good answers to all of these questions. My issue is that “requires X or later” collapses several very different situations into one neat compatibility note.
Sometimes something genuinely cannot work. Sometimes it could work badly and Apple has decided badly is worse than not at all. Sometimes Apple could build a reduced version but has decided that doing so is not worth the engineering effort.
And sometimes the clean hardware cutoff is also extremely convenient for a company whose business involves selling the hardware on the other side of it.
Those are not the same thing.
Supported, except for the interesting bits
This is the bit of modern Apple software support I find increasingly difficult to judge.
Traditionally, asking how long a phone would receive updates gave you a fairly useful idea of its lifespan. If an iPhone kept getting iOS, it kept getting the new iOS.
That is less true now.
My iPhone 15 runs the current operating system. I can visit Apple’s page for that operating system and watch demonstrations of its headline features. Then I hold down the side button and get a different Siri because my phone does not meet the Apple Intelligence hardware floor.
An older Apple Watch can receive the current watchOS while newer Watches get a health layer which becomes one of the major reasons Apple gives you for caring about that release in the first place.
There is nothing inherently wrong with that. Software gets more demanding, sensors improve and eventually old hardware cannot keep up. I would be more suspicious if Apple claimed every feature could run identically forever.
What feels different is how quickly “supported” can stop meaning “gets the things Apple is advertising”.
An iPhone 15 does not feel old. A Watch being replaced today certainly did not feel old yesterday.
If major software features increasingly depend on hardware that is one or two generations old, then the question “how many years of updates does this get?” stops telling me what I actually want to know.
What I want to know is how many years the device will remain part of the version of iOS or watchOS Apple talks about on stage.
That is a much harder thing to put on a spec sheet.
It should also change how we look at hardware when it launches. Six gigabytes of RAM did not make the iPhone 15 a bad phone in 2023 and it does not make mine a bad phone now. It still does basically everything I bought it to do.
But in hindsight, six gigabytes also meant Apple’s mainstream phone had very little room for the software Apple itself was already building.
When the eventual base iPhone 18 arrives, I am going to care a lot more about that sort of headroom than I used to: not just whether it is fast today, but whether Apple is building it to participate in whatever iOS becomes three years from now.
Three questions, really
That is what I ended up thinking about after the event.
Where is the ordinary iPhone 18?
How well does a foldable iPhone actually work if your right hand has poor dexterity and your left has to do most of the precise work?
And when Apple says the interesting new software needs newer hardware, how often does “needs” mean physically impossible, how often does it mean Apple does not like the degraded experience, and how often does it mean Apple simply chose not to build one?
I suppose there is now a developer footnote to the second question too: if the Duo is going to exist, please make it boring to support. I mean that as a compliment. Give me good adaptive APIs, make the standard controls do the sensible thing automatically, and do not make me write if duoIsHalfOpenAndBeingHeldLikeABook anywhere in my code.
The Apple and Samsung sniping around it is mostly funny to me. Samsung is completely entitled to point out that it has spent seven years making the sort of phone Apple unveiled yesterday, while Apple is completely entitled to think it can now make a better one. I would much rather that rivalry happen in hinges, software and battery life than in people screaming at each other because their phone has the wrong logo on it.
The iPhone 18 Pro looks extremely good, although I’m probably not the person Apple is trying to sell it to. I’m more of a base iPhone guy: give me the regular model, the sensible price and the features that make it a good everyday phone. The Duo is one of the most interesting pieces of hardware Apple has made in years. Siri AI, from actually using it early on the public beta on my Mac rather than judging it from a keynote demo, is considerably closer to what Siri should have become years ago.
I’m not anti-Apple here. I use a Mac every day, my phone is an iPhone, and I watched the event because I like this stuff. Apple is still very good at making hardware which makes me want to spend ten minutes figuring out how they engineered it even when I have absolutely no intention of buying it.
That is why the gaps stand out.
I want the ridiculous £1,999 folding phone to exist. Technology would be considerably more boring if companies only made sensible things I could personally justify buying.
I also want the ordinary phone.
I want to know whether the folding one was designed around people with limited dexterity before the accessibility software gets involved, and I would strongly prefer not to discover that every iOS app I maintain now needs a small collection of Duo-specific hacks to survive being folded in half.
And when Apple builds something like Readiness after developers such as Bevel have already demonstrated what can be done with existing hardware, I want to know why Apple so often seems to start from the newest device rather than asking what version it can bring backwards.
Not because every limitation is fake, but because “supported” is becoming a much less useful description of what an Apple device can actually do.
My iPhone 15 cannot run Siri AI. My Mac can, and because I’m on the public beta I have already been using it long enough for that mismatch to stop feeling theoretical. Bevel can already take Apple Watch data and tell me something useful about recovery. Apple can now do something similar itself, provided I have the right Watch.
Maybe every one of those boundaries has a sound technical justification.
I would still quite like to know where Apple thinks the boundary between can’t and won’t actually is.
Comments
Checking AT Protocol sign-in…
No comments yet
Be the first to share your thoughts on this post.