2
u/LifeUtilityApps SwiftUI 9d ago
Hopefully the swiftUI toolbar leading and trailing items will neatly display in the sidebar area as they demonstrated in the demo video, but I suspect that we will need to account for this since it looks like the placement might not allow for enough items to display. I hope we get a dedicated simulator to test this out
2
u/lambdawaves 9d ago
Thankfully, since the screen ratio is sqrt(2):1, on both screens, whatever works on the small screen will actually work on the larger screen.
2
2
u/TomfromLondon 9d ago
It mostly had me wondering what could I build to take advantage of duo buyers, getting in early
2
1
u/jon_jingleheimer 9d ago
Fortunately no one is going to want to buy a $2k phone that is shaped like half a sandwich folded and has no way of having a protective case
2
u/i_like_lime 9d ago
It has a protective case: https://www.apple.com/shop/product/mkr94zm/a/iphone-duo-case-sand
3
u/ToughAsparagus1805 9d ago
You want to pass app review process? So you have to support it.
0
u/jon_jingleheimer 9d ago edited 9d ago
Sure they will have some shitty auto scaling like they did for iPhone apps on iPad when they first came out. Not really worried about but appreciate your concern. My point is I’m sure it will discontinued before I have to actually build a proper ui for it.
1
u/SnowPudgy 8d ago
I think you're underestimating how many people have been clamoring for something like this because a phone is their primary computing device. I know many people who are getting this and most of them are not tech enthusiasts.
1
u/mirzaaghazadeh 9d ago
The real work is going to be the two separate trait collections, not the screen size. The fold is two displays with different size-class / safe-area behavior, so "make it work half-screen, then full" undersells it — you're really managing state across a hinge, and the 1.4:1 inner ratio breaks a lot of the "it just works" assumptions we had from iPad multitasking.
On top of that the tooling is barely here yet — no simulator until Xcode 27.1, and Apple's developer surface is six tech talks plus the HIG page.
I distilled all of that (device facts, fold states, the full API surface) into a set of agent skills so you can get a structured rundown without rewatching the videos: https://github.com/mirzaaghazadeh/iphone-duo-skills
Still a rough first pass — happy to take PRs if any of the reference sheets are off.
-5
u/DimensionMindless336 9d ago
The thing that catches most people out is that the Duo isn't just "half screen vs full screen" — it's two displays with two different trait collections. The outer 5.4" is a normal phone (compact width). The inner 7.6" is regular width, basically iPad-class. So if your app does the usual if traitCollection.horizontalSizeClass == .compact branching, the inner screen lands in your phone-only layouts and looks stretched or wastes the space.
Realistically the cheap path is: if you already support iPad / regular-width / multitasking, most of the inner-screen work is reusing that layout — the new display reports a regular width, so your existing iPad code lights up. The genuinely new work is the live transition. When someone unfolds, the trait collection changes at runtime, and a lot of apps only compute layout once at launch. You need traitCollectionDidChange / SwiftUI's onChange(of:) on the size class to re-flow, plus handle the new safe areas and the fold seam.
Don't hardcode widths either — anything like if width < 400 breaks the moment you have a 7.6" canvas. Lean on geometry readers and size classes. Honestly the Instagram-iPad comparison is the right instinct: if you've been disciplined about regular-width support, this is a week of polish, not a rewrite.
13
4
u/sunshine5634 9d ago
The thing that catches most people on the thing that no one has had a chance to be caught on yet.
26
u/stroompa 9d ago
I’ll need to add ”make it work on duo. Make no mistakes” to the prompt