Opens Apple Developer Forums in a new tab. Apple may ask you to sign in or complete a security check.
The lab paneliPhone Duo Group Lab · September 16, 2026. Screenshot from Apple’s livestream, provided by Marc Laberge.
Explore the topics
THE LEARNING AGENDA
01 / LAYOUT
Across displays. Across poses.
Adapting layouts as the available space and device pose change.
Questions to explore
Which layout decisions should respond to available space?
How can navigation and reading position stay continuous when the pose changes?
02 / HINGE
Work with the hinge.
Understanding how the hinge should influence content and interaction.
Questions to explore
What guidance should shape content placement around the hinge?
How should touch targets and gestures adapt across poses?
03 / MULTITASKING
A good neighbor in Split View.
Keeping an app useful and comfortable as it shares the display.
Questions to explore
Which compact layouts deserve dedicated testing?
How should an app preserve its state during resizing and multitasking?
04 / CAMERA
A different point of view.
Building camera experiences that feel natural in different configurations.
Questions to explore
How should the preview and controls respond to a change in pose?
What camera scenarios should be tested on device?
Which Xcode for iPhone Duo?
CHECKED SEPTEMBER 16, 2026
COMING LATER IN SEPTEMBER
Xcode 27.1 beta
Apple has announced Duo SDK and Simulator support for later this month, with no exact date yet. The simulator will support Duo’s poses and orientations.
For Duo-specific testing, watch for Xcode 27.1 beta. You can explore the general layout examples below in the meantime. Check Apple’s downloads ↗
Try it in code
SWIFTUI · iOS 27.1+
Three independent SwiftUI examples. In an iOS app project, replace ContentView.swift with one example, then open the Xcode preview or run in Simulator. This journal targets iPhone Duo on iOS 27.1 or later. Duo-specific Simulator testing requires the upcoming Xcode 27.1 beta.
01 / ViewThatFits
Fit the available width
Switch from a row to a column when the content no longer fits.
Show Swift code
FitContent.swift
import SwiftUI
struct ContentView: View {
var body: some View {
ViewThatFits(in: .horizontal) {
HStack { actions }
VStack { actions }
}
.buttonStyle(.bordered)
.padding()
}
@ViewBuilder
private var actions: some View {
Button("Save to reading list") { }
Button("Share this discovery") { }
}
}
struct ContentView_Previews: PreviewProvider {
static var previews: some View {
ContentView()
}
}
Try this : Narrow the preview or increase the text size. The buttons stack vertically.
These examples teach adaptive layout fundamentals. They do not use Duo-specific hinge or camera APIs. The first example’s buttons demonstrate layout only.
Collected from Apple Developer on September 16, 2026. The hub also lists upcoming workshops, Q&As, and tools as they become available.
Questions from the lab
01 / ADAPTIVE LAYOUTS
For an app that already supports iPhone and iPad, should we treat iPhone Duo primarily as another adaptive size-class environment, or are there scenarios where Apple recommends implementing Duo-specific layouts?
Panel answer
Focus on making the app adaptable. Build on the work already done for iPad, then layer in the newer APIs and additions, such as vertical controls.
Paraphrased from Marc’s live notes; not a verbatim quote.
02 / SEATED MODE & ORIENTATION
Can the Duo be in seated mode with the camera side face down on the table, or only outer-screen down? If so, is it possible to detect which screen is face upwards vs forwards?
Panel answer
Seated mode should work either way: with the camera side down or with the outer screen down. The panel was not sure whether an app can detect which screen faces upward versus forward. Detection remains unconfirmed.
Paraphrased from Marc’s live notes; not a verbatim quote.
03 / CUSTOM TAB BARS
Will a custom tab bar displayed at the bottom of the interface automatically adapt to iPhone Duo? How will it be displayed?
Panel answer
The panel strongly recommends moving from a custom tab bar to the standard system tab bar. The response recorded here did not confirm whether a custom bottom bar adapts automatically or how it would be displayed.
The panel also shared that Apple had wanted to introduce vertical bars for a long time, but had not had a layout where they made sense until iPhone Duo.
Paraphrased from Marc’s live notes; not a verbatim quote.
04 / TOP PRIORITY
What is one thing you'd want all developers to adapt properly for the best experience?
Panel answer
Reuse the system’s vertical bar.
Use regions to arrange content for the pose—for example, moving video to the upper area when the device is seated like a laptop.
Design thoughtfully for each pose, looking for opportunities to create delightful moments.
Keep the experience adaptable: people will use the device differently depending on where they are and what they are doing.
Native Apple components, such as alerts, also adapt to the fold. The final panelist highlighted this as another reason to avoid unnecessary custom UI.
Paraphrased from Marc’s live notes; not a verbatim quote.
05 / ASPECT RATIO & FULL-SCREEN CONTENT
What is the recommended guidance for existing apps to adapt to the new aspect ratio during the Xcode 27 transition? How can we minimize letterboxing/pillarboxing and display content closer to full-screen on launch day?
Panel answer
A universal app that already supports iPhone and iPad is a good starting point.
Remove reliance on UIScreen.main.
The system can tell which Xcode version an app was built with. Compile with Xcode 27.1, when it becomes available later in September 2026, to get the full Duo experience.
Check that the app works on iPhone Duo and on other supported devices too.
Paraphrased from Marc’s live notes; not a verbatim quote.
06 / PORTRAIT LOCK & SIZE CLASSES
If an app locks its supported orientations to Portrait only, does it still get the compact/regular size-class changes as iPhone Duo folds and unfolds, or does that lock block adaptive layout completely?
Panel answer
The panel acknowledged the existing APIs for controlling supported orientations, but recommended moving away from those APIs toward newer approaches and using size classes to guide adaptation. They also mentioned a skill that could help with the transition; its name was not captured in these notes. The response recorded here does not explicitly confirm whether portrait locking prevents compact/regular size-class changes.
Paraphrased from Marc’s live notes; not a verbatim quote.
07 / ACCESSIBILITY
Are there accessibility nuances that should be considered with iPhone Duo?
Panel answer
Proper support for resizing is especially important for accessibility.
The panel highlighted VoiceOver working across two screens at once.
A term heard as “smart take” was also mentioned. The exact term and its meaning still need clarification.
Paraphrased from Marc’s live notes; not a verbatim quote.
08 / ONE CANVAS OR TWO DISPLAYS?
When designing for Duo, how does Apple want developers to think about the device conceptually: as one large adaptable canvas, or as two distinct displays that can cooperate?
Panel answer
The goal is one seamless experience. The panel pointed to the animations between opening and closing the foldable device as an illustration of that continuity.
Paraphrased from Marc’s live notes; not a verbatim quote.
09 / THREE-COLUMN LAYOUTS
How should apps that use a three-column layout on iPad adapt to iPhone Duo?
Panel answer
Present the sidebar as an overlay. The panel also recommends using NavigationSplitView, noting that adopting it gives you the 50/50 layout automatically.
Paraphrased from Marc’s live notes; not a verbatim quote.
Screenshot from Apple’s lab discussion about adapting three-column layouts, provided by Marc Laberge.
10 / APPS BUILT WITH THE iOS 26 SDK
How will apps which don’t yet support Duo, such as apps built with the iOS 26 SDK, be presented in the various poses?
Panel answer
The panel framed this as an opportunity to adapt existing apps. Otherwise, users may see black bars around the app’s content.
Paraphrased from Marc’s live notes; not a verbatim quote.
11 / ADOPTING EACH POSE
Does each pose need to be manually adopted, or is following best practices enough to likely look good in each pose?
Panel answer
Start by following best practices, then iterate. Don’t force a special layout for every pose: consider whether it adds real value, and think through the transitions between poses.
Paraphrased from Marc’s live notes; not a verbatim quote.
12 / USING BOTH SCREENS
Can apps utilise both screens at the same time to open up new features?
Panel answer
The panel answered yes, but said simultaneous use of both screens is limited to camera apps.
Paraphrased from Marc’s live notes; not a verbatim quote.
13 / INNER-DISPLAY LAYOUTS
The inner display has regular horizontal and vertical size classes. Our app currently supports only iPhone in portrait, with no iPad support, but we would like different landscape and portrait layouts on the inner display. What is the recommended way to distinguish between them?
Panel answer
Don’t rely solely on reading device orientation. Consider the regular/regular size-class context and use navigation layouts and grids that adapt to different screen sizes.
Paraphrased from Marc’s live notes; not a verbatim quote.
14 / OPTING OUT OF THE ADAPTED DISPLAY
My app will require some months of work to make it compatible with iPhone Duo. Is there a way to disable stretching the screen and keep the regular iPhone behavior on Xcode 27?
Panel answer
The panel said there is no such opt-out once the app is compiled with Xcode 27.1.
Paraphrased from Marc’s live notes; not a verbatim quote.
15 / SHEET PRESENTATION
How should sheet presentation adapt to Duo? On iPhone, we currently use a panel overlaid on content (like Find My, Flighty, etc.). Should it sit side by side on Duo?
Panel answer
Keep the experience consistent: the content stays in the sheet.
Paraphrased from Marc’s live notes; not a verbatim quote.
16 / PRELIMINARY TESTING & SAFE AREAS
Until the iPhone Duo simulator becomes available, we are using the Resizable iPhone in Device Hub for preliminary testing. Could you clarify which types of issues can be identified using this approach, and which issues can only be detected with the iPhone Duo simulator?
Panel answer
Don’t assume the safe-area insets are symmetrical on the left and right. Account for safe areas along the sides as well as the top and bottom. The response captured here does not specify which issues can be found with the Resizable iPhone versus only with the Duo simulator.
Paraphrased from Marc’s live notes; not a verbatim quote.
17 / FULL-SCREEN AR APPS
Is it possible to support a full-screen-only app for an immersive AR experience?
Panel answer
Yes, according to the panel.
Paraphrased from Marc’s live notes; not a verbatim quote.
18 / MULTIPLE INSTANCES & SHARED STATE
Can you clarify how multiple instances of the same app work on iPhone Duo? If both instances use UserDefaults or @AppStorage, do they share the same state, and will changes made in one instance automatically update the other?
Panel answer
The panel said the behavior is similar to iPad and confirmed that the instances share the same state when using UserDefaults or @AppStorage.
Paraphrased from Marc’s live notes; not a verbatim quote.
AFTER THE LAB
What I learned
Start with an adaptable app, prefer native components, respect safe areas, and design thoughtful transitions between poses. Test on Duo and other devices.
The panel has ended. This journal collects 18 questions and the answers captured during the session. Points still needing confirmation remain marked.
A final thank-you to GPT Astra for turning my rough live notes into clear English and Canadian French, in real time throughout the lab.