2026-09-16 • iOS • 59:28
Connect with Apple engineers and designers online to ask questions, get advice, and follow the discussion about creating and updating apps for iPhone Duo. In this one-hour event, you’ll learn how to adapt your layouts across displays and poses, work with the hinge, support Split View multitasking, and build great camera experiences.
Downloads from Apple
Transcript
Welcome to today’s iPhone Duo Group Lab. Thanks for joining. I’m Curt, a technology evangelist on Apple’s Worldwide Developer Relations team. My colleagues and I will be taking your questions for the next hour. If you’re watching on the Apple Developer site, please submit your questions in the panel on the right. If you’re watching on YouTube and would like to submit questions or vote for your favorites, please hit the link below. And remember, like and subscribe.
First, I’d like to share a bit about Xcode 27. The beta versions of the 27.2 operating systems are now available. Test your apps with the new Xcode 27.2 to get ready for future releases. Note, though, that when iPhone Duo becomes available on October 23rd, it will run iOS 27.1. iOS 27.1 introduces features that were purpose-built for the new foldable design.
As discussed in the Tech Talk videos released last week, Xcode 27.1 available later this month, will add development support for iPhone Duo, including updated SDKs and a new version of Device Hub that supports the all-new poses and orientations of iPhone Duo. In the meantime, the Figma and Sketch design kits are available from the Apple Developer website.
I’m super excited about our panel for this group lab. You all come from a variety of teams and roles, and one of the things that I find so cool about iPhone Duo was how so many teams pulled together to deliver this incredible experience. So before jumping to questions, I’d love to have each of you introduce yourself and say a little bit about what you worked on for iPhone Duo.
And I guess, Tommy, you’re sitting next to me. I’ll let you start. Awesome. I’m Tommy, I’m a UI frameworks engineer, and I worked on adapting many of our built in framework components in UIKit and SwiftUI to the various different pose layouts that you have on iPhone Duo. Awesome.
And I’m Nate, I’m on the human interface design team. I’m an interaction designer. So I work on kind of all things iPhone at the system level, how apps interact with one another, how all the different system spaces fit together, but then also how apps work as well. So framework patterns and so on. So if we have split view multitasking questions, you’re a guy. I’ll do my best. All right.
I’m Brandon. I’m on the human interface team. And yeah, I worked on the design of, you know, a bunch of different pieces of iPhone Duo, including multitasking, like you were talking about, you know, status bar and vertical bar and yeah, lots of other elements of it. Nice. Yeah.
So, hi, I’m Nina. I’m an engineer on the TV app team. I worked on adapting the TV app for the Duo, and also the Sports app and the TV and the Apple TV Remote app. Nice. Immanuel. And I’m Immanuel. I am an iOS engineer on the Maps team and I worked on getting Maps. Find My and Compass updated on the iPhone Duo. Awesome. Thanks all for the introductions. And if any of you have questions particularly suited to those particular areas, we’d love to hear those, but we’ll also take all the other questions you have to offer.
So appreciate that. So here’s our first question. And I think this is coming from someone in New Zealand based on their handle. Can non-camera apps display things on the outer screen while unfolded? And I said I’d direct questions in particular ways. But Nina, do you want to tell us a little bit about that one? Is that something you’re familiar with?
It’s actually not. Oh, so this I worked on, but. Yeah, yeah. Maybe this is more of a system UI handle that one. I think. I believe there is an API to do this to display content. For camera apps specifically. Yeah, yeah. There’s a system entitlement that, that you can adopt in your app.
So one thing to note there that’s important is the, the companion display for the camera is only available when there’s an active camera session. So it’s not enough just to have the entitlement. You actually have to be running a camera session to light up the inner and outer displays together. But thanks for that question.
The next one is a really interesting design question, but I think it also touches on a lot of the, the first-party apps that we shipped. So I think a lot of folks might have something to add here for an app that already supports iPhone and iPad. Actually, I’m going to start with you on this, Tommy, and then we’ll send it down the line. Should we treat iPhone Duo primarily as another adaptive size class environment, or are there scenarios where Apple recommends implementing duo specific layouts?
Yeah, I think we tried really hard to. We have a number of really concepts that we’ve developed over years, from iPhone to iPad for building adaptive layouts, right? If you think about the way that split view controller adapts on an iPhone versus an iPad, many of those same principles come automatically to iPhone Duo. So if you’re using built-in components, they work really well and adapt for you.
We have some new ones this year that we’ve added as APIs, but we really thought from the ground up, how could we make those complementary to experiences that you already may have created on, on iPhone, right? For instance, if you have like a, an AVPlayer where you’re playing some playing a movie. We have new API for you to adapt your content. So when you fold the controls, like move down to the bottom of the screen.
And so all of these concepts exist and, and kind of iPhone Duo is just another part of that seamless experience of, of, of layout in, from the framework side at least. Nate, do you have anything to share around how we think about iPhone Duo and iPad differently? And how do we think about them as sort of a similar kind of. Yeah. I mean, there’s a lot of overlap.
I think at the very foundation, you want to make sure your app is adaptable in size, and that’s applying to both from small phones to max size phones, from small iPads to large size iPads. Like every app should really be adapting to any size and expecting any size.
So all of that applies. But then as you get larger in size, some of those patents that Tommy mentioned, like split views and sidebars, they start to come in. So really, it’s about like making sure your app is adaptable. And then if there’s any particular conventions for the device you’re running on that are applicable, like then you start to layer those on to. And then for duo, that’s where the, the vertical controls start to come in. And yeah, so it’s more like layering in those APIs.
Curious how the ergonomics of the different-sized devices enter into it? Like I think of the duo as something I’m going to carry around. But my 13-inch iPad is something that, you know, usually sits on my desk. Is that something we should think about too? It does play a big role because you’re using this phone like out of your pocket closed quite a lot.
And so you all your muscle memory starts to develop around those vertical controls. So when you open it, a lot of the time, you’re going to reach for that same position on the screen. For those familiar controls, there’s, there’s a lot of places where we break from that convention where it makes sense, but I think starting there often is the right approach.
Yeah, we certainly tried to make it feel very consistent between the closed pose and the open landscape pose. And, you know, because you’re, you’re sort of used to the positions of those buttons, but, you know, when you rotate into portrait, you know, it’s, we feel like it’s more of a sort of two-handed mode where you’re going to be sort of, you know, using either hand to access controls, you know, so we, we’ve changed the layout there. Nina and Immanuel are there. Are there differences and similarities between the, the apps that you work on, on iPhone versus iPad? Is there, is there interesting pieces there that different choices were made for iPhone Duo.
So we did a lot of work to make the app TV, for example, adaptive to all sizes. So we do take advantage of the bigger screen. For example, if you look at the TV app enclosed, you would see a little less details than when you see when you look at it in open. And for that we just use the size classes.
So, you know, if you’re in a small screen versus a bigger screen and take advantage of that. Nice, Immanuel. Anything else? Yeah. And for Maps, I mean, it’s like a very similar thing. I think the main difference between phone and pad is like our sheets layout on the leading edge. So you can see a lot more map. But yeah, I mean, in terms of getting it run on iPhone Duo, it was just we already had it running on iPad and it just translated nicely and we didn’t really have to change much there.
We had to do a lot of work adopting the vertical bar, but that’s a different story. It worked well on the iPad. I’m sorry. On the on the Outer display Inner display. Inner display. Yeah. Great. Excellent. All right. The next question, I am afraid I don’t know the answer to at it all, or even who to throw to. So maybe I’ll start with Brandon just as our lucky.
So the question is, can the Duo be in seated mode with. And I’m not entirely sure there. But let’s see what we get from the question with the camera side face down on the table or only the outer screen down. So I, I think if we’re looking at Nina’s phone, can it be that way or that way? And then the question is, is it possible to detect which screen is on the table?
That’s a great question. Yeah, I believe it does lay out like you can place the device like that and the interface works and it’ll look the same as it does when it’s flipped 180. Whether it’s possible to detect that. That’s another question. Yeah. I’m not I’m not totally sure. This is actually a really good example because I don’t use the folio case with mine. So my preferred way of setting it down is with the screen down.
So it’s flush on the table. Someone that does have the folio case, they can set it down like this and open it. Yeah. Equally well and it’s flush on the table. So I think two different customers might do it one way or the other. Right. And so I think the expectation is that you can do it either way and get the same functionality that like one way doesn’t behave differently to the other. I’m imagining the developer might be asking this question because they want to provide some sort of notice to the user that the cameras are being covered, right? That they’re pointing at the table.
I wonder if it’s possible to detect that in some other way. You know. I mean, if you if you are using the cameras, they aren’t going to show you anything if they’re pointing at the table. So that’s one thing. Yeah. This actually gets at a really interesting point that came up while we were developing the technical videos.
Expect people to use this device in and through all of the different ways of holding it. Like you. If you’re designing for just one way of holding it, people aren’t just going to hold it that way. They’re going to hold it in lots of ways. And you need to meet, meet customers where they are, meet people where they are. And so you really need to be thinking about supporting all of the different ways that might be used. 100%.
All right. So we’ve got our first bar question and let’s see where to start. I’m gonna start with you, Tommy. Will a custom tab bar displayed at the bottom of the interface automatically adapt to the iPhone Duo? And if so, how will it be displayed? Well, if you are using a.
If you count your custom tab bar as just. You are creating a UITabBar and inserting that as a subview. It won’t automatically be placed in the vertical bar. If you’re using a tab bar controller or a TabView and SwiftUI, then that functionality you’ll get automatically. And you don’t have to do any work to do it. And so we really recommend that if you can use a tab bar controller here, then you should move over to that.
If you’ve already created an entirely custom tab bar, that’s even probably an experience where you’ll have to do even more work to get back into kind of the built in system components or use some of the, the lower-level APIs that we’ve exposed around aligning your custom bars to the vertical bar metrics. Yeah, I think it’s important to note there that it’s possible there are reserved regions and ways to do that alignment, but there are a lot of places that vertical bars can appear even on the.
When the device is closed, as you rotate it, the vertical bar always aligns with where the camera is, so it can be on the left. And if you’re in Split view multitasking, well, the device is the left-hand app will have a left-hand bar. And so there’s just a lot of asymmetry that you need to take care of. Immanuel in our conversations, you talked about moving to system standard components being a big part of your work.
Is there anything you want to add there? Yeah. So Maps and Find My both have this rich history of manually embedding like fake toolbars and bars into their view hierarchy. We did not use navigation controller, and this year we did a lot of work to migrate all our screens over to navigation controller and Tab bar controller in order to get the vertical bar, and we’re really happy about it.
We love the vertical bar. And this is something, you know, this is something we wanted to do for a long time, but there was never really like a user facing justification for it. So, you know, when the vertical bar came by and this was like the only way we could do it, it was, you know, it just worked out.
Yeah. That’s one thing we heard in the in the workshops actually starting last year on the new design workshops. And as people were adopting Liquid Glass was it was an excuse for engineering and design teams to clean up some things that felt like technical debt or design debt and move on to some system components.
And I know it’s a little bit self-serving, but it is also true. Yeah, I think there’s some like really cool aspects, especially on iPhone Duo to the tab bar, right? There’s all of these, like there’s obviously on iPhone and iPad, lots of great interactions, like the lens effect and things like that.
But there are even more really nuanced aspects to the design of the tab bar. So I noticed, and I know a lot of other users are going to notice when you press down on that tab bar, and it doesn’t feel the same way as the system experience, that’s going to be a really important thing that you can really make a great experience in your app if you kind of align with that actual system component. Yeah. I think a big thing we do is show the labels on touchdown.
Right? So when you touch down and start dragging, it’s like clear what all the tabs are. And so yeah, certainly if, if developers doing a custom tab bar, you know, ideally they would have some way to show labels, right? Yeah. There’s a lot of system functionality to mimic if you’re to do it yourself. Yeah. Excellent. Thanks very much.
So the next question I think I’ll do this a, a down the line question. We’re going to start with the manual and come back because it’s a more general one. And this is from Michaela. Hi, Michaela. What is one thing you’d want all developers to adapt properly for the best experience? Good question. I mean, could I reuse vertical bar? You know, like.
There is a reason I’m saying that is because, like someone who’s been like living on this for the past few months, like it is just like so intuitive to like have access to all my buttons. So I just want to see more of that. And yeah, it’s like a great pattern.
And I think, you know, making the changes to adopt the vertical bar would be something I’d to see a lot of developers doing that. And that doesn’t rule out vertical bars for the. Vertical bar is like my favorite thing. I can use it on one hand. All the button is in the same place. So yeah.
Yeah. I would go with ArrangementViews because you can do so many cool things with them, like TV is using AVKit, which uses it to, you know, move the video to the top and controls to the bottom in when you position the phone like a laptop. And that’s just, you know, taking advantage of these cool features that we have on this device, and with very little work because the system takes care of a lot of it. So yeah.
Yeah. I think at a high level, you know, just designing for each pose, I really appreciate as a user, you know, like from living on this for, for a little bit, you know, it’s really nice when you know, I think, oh, like, what is this app going to do when I place it on the table? Right. And you know, or maybe I partially fold it and place it the other way and the app just does something really special. And, you know, it’s often a very delightful moment. Nice.
Yeah. What do I, what do I pick? Yeah, I think just to echo Brandon’s comment and what you said earlier about people using it in different ways in different poses, like I’m finding myself placing it down in different ways depending on the context I’m in. Like when I’m at work, I might place it one way when I get home.
It’s a different way. And it’s just so it’s, it’s a very adaptable device in a way that the phone really hasn’t been like, you can prop it up in certain ways, hold it in many different ways. So having it just feel like it’s the right experience in that pose is like really critical.
And I think it’s very easy as a, as a designer or developer to see what it should feel like, because there’s like a pretty cohesive story in the first-party apps that I think will be apparent when you, when you start using it. Yeah, just kind of expecting that it’s going to be used in lots of different interesting ways. I think that’s what’s exciting about it.
Yeah. Tommy in the hard in the hard seat he’s. Got for him. I think one of the interesting things is we have a really broad spectrum of APIs in regards to information you can get about the fold right. From the lowest level we have, you can get the actual angle that you folded to.
And then we kind of built up from there where we’ll give you basically a rect on the screen when you’ve properly folded the device to a certain angle. And then on top of that, for when to, for developers who might be using lower level layout primitives like a HStack or a ZStack, we came up with this like ArrangementView concept where you can use those same layout primitives in a way that adapt to the folds.
And then obviously we have like our highest level, like the, all of the main system components from like alerts and sheets and split view controllers, all of those things adapt. And so I think the, the thing to, to me to get properly is to, to figure out for the experience that you’re trying to build, which is the proper API, right?
Like it’s fun to go down and like immediately say, I want the pure angle of the hinge and like, do some wild math to, to like try and create a UI, but the. The Reserved region API might be a better fit for that, or an ArrangementView or things like that.
And so I think getting that kind of that fit right with the API is going to really make sure that you have the easiest time to adapt for this, for this phone. I don’t have a horse in the race, as they say, but one thing I’m really looking forward to is actually extra large in standby mode on the device.
I think it is just so cool to have the have the phone standing there with a widget on one side and other stuff on the other side. So that’s probably not the one thing I want every developer to adapt but or adopt. But that’s one of the things I’m looking forward to. All right.
Actually, Tom, I’m going to come back to you with this one and then invite other folks to jump in. So the question is, what’s the recommended guidance for existing apps to adapt to the new aspect ratio during the Xcode 27 transition. How do we minimize letterboxing or Pillarboxing and display content closer to the full screen on launch day?
Yeah, I think there’s a few ways, right? Like we’ve talked about, if you have a universal app and that works well on iPad, you’re, you’re well on your way to getting started. An important tool that you can check out, right? Is resizing your app on iPhone Mirroring. You’re going to be able to get an aspect ratio that’s pretty close to that using that experience.
And, and because that experience also doesn’t change things like your and the type of device that the system thinks you’re on, you’re going to be able to take advantage of seeing how the experience on what we consider a phone from the frameworks actually looks. And so starting from there and seeing how you can, what the experience currently is of your app and then looking for things like, can I adapt to different size classes if I haven’t done that? Can I remove my usages of UIScreen.main and all of those things, I think.
Trying to figure out how those experiences look on those existing tools that we have is going to be really helpful. Yeah, and that’s been part of our story for really the last, last two years. Move controls out of the content area into the edges with the new design. Resizability over the summer, modernizing your app. So anything else folks want to add around letterboxing? Pillarboxing getting ready for launch day?
I think, yeah, I’ll second that. We did a lot of work to get TV up, to resize to any size on iPad, and all of this work paid off when we, you know, tried to run it on the duo. It basically just worked really well. So yeah, and there’s, there’s actually a technical progression there that, that we can bring up and it’s, it’s in the prepare your app for iPhone Duo video. But if you’re linking against Xcode 26 on the Inner display, you will be you’ll be Letterboxed. Your app will appear in iPhone regular on other iPhone aspect ratio with black bars on the sides. Once you build with Xcode 27 now you’ll end.
You support Resizability. You’ll use almost the full interior screen, but there’ll still be a black bar on the side underneath the status bar. And when it’s available later this month, you build with Xcode 27.1. Then you’ll go to full screen. And so that’s sort of the progression. And it sort of tells you if you look at the app, it tells you what it’s being built with. Like we can tell which version of the compiler and SDK you use based on how the app appears.
So anybody else want to jump on that? Yeah, I would say like something we’ve tried really hard with this phone for instance, to not do work that’s very specific to this phone because it’s part of a broader ecosystem. And so when we introduced App Resizability, that was setting us up not just for this phone, but the fact that there’s dozens of phone sizes that your app needs to support, similar to Live Activities as well, like some of the work we’ve done for iPhone 18 with showing multiple live activities. That work was in support of iPhone Duo as well.
You mentioned the four by six widgets that you like on iPhone Duo. They also work on other devices, so you can do a lot of this work across the ecosystem, and it’ll just play out nicely on the duo, and you’ll have very little work to do when the duo comes out. Excellent. Yeah. Great. Thanks all. So the next question, who do I throw this at?
Immanuel. I’ll take you. I’ll let you take a stab and then you can toss it to someone else if you if you don’t want it, will there be any new agentic coding skills released for Xcode to support developers to upgrade their apps using coding intelligence for their iPhone Duo layouts?
My understanding, I think I might need some help here, but my understanding is there is some. I am. We had used a little bit of it in Maps actually for like the main screen UI screen Main screen, and it worked really well. So I’m hoping that it shipped. So yeah, my, my understanding is that Xcode 27.1 and we mentioned this in, in the “Prepare your app for iPhone Duo” video that is going to have an updated version of the modernize your app skill that’s updated to support SwiftUI in addition to UIKit.
And that knows about iPhone Duo and can adapt to that. So that is coming and looking forward to feedback on that as people try it out. And it definitely just wanted to add kind of reduces a lot of the cognitive load. It was really helpful for us to, you know, kind of get modernized. So nice. Yeah. All right.
Interesting. Brandon. I’m going to start this one with you and you can throw it to someone else if you want. So suppose 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 it block adaptive layout completely?
Feel free to someone else. I imagine it would block it, but Tommy, I’m not sure if you are aware of that one. Yeah, I think obviously there are existing API’s to do this. And With this new phone. We haven’t stopped supporting all of those, all those APIs. There’s things like that. And like UIRequiresFullScreen and, and we strongly recommend that if you can get off of those as APIs and, and move to not and having your app be able to resize and reflect any orientation that’s going to be really important, especially because.
There are many different types of APIs, especially in UIKit around orientation and. And some of those may not reflect what you may naturally think on this new display. And so we, we really want you to go off of the size classes as, as your way of adapting to layout versus orientation here.
And my understanding from working with, with Harry on his, his technical video was that on the outer display, we will honor supported orientations, but on the inner display, we won’t. Yeah, and so it will adapt. And the size class will be regular, regular on the, on the inside. Yeah. I think that’s kind of a like part and parcel with supporting Resizability.
As soon as you go from a portrait aspect ratio to square, now it’s then a little bit wider. Like do you not support landscape? Like where do you draw the line? Right. Like it just becomes really hard once you’ve got a freeform window on a Mac, for example, to say like, I want to stop here.
So yeah, we decided that like when you support Resizability, we try to try our best to fill the screen and give you the best experience. Great. So the next one, I’ll start with you, Tommy, and you can throw it down the line if you want. Are there any accessibility nuances that we should be concerned with on iPhone Duo?
I think in general, right. There’s a lot of different Accessibility APIs, particularly Right? You’re you’re on a bigger screen. So you’re going to maybe have users who really rely on dynamic type and those things to really try and have an even better experience on this phone, right. Especially like the, these UIs at the largest accessibility sizes are going to look really good when they open their phone.
And so adapting your UI to things like and using APIs, like the readable content guide and those types of things are really going to be important to, to supporting Resizability with those kind of visual accessibility features. Obviously, VoiceOver, Voice Control, all of the other accessibility technologies are on the device.
And the team I know has worked really tirelessly to, to make sure those are those are great experiences. And it’s one of the first times where VoiceOver is, is working on two displays at once. And so there’s a whole lot of work there. But, but yeah, the experience is, is I’m excited for it.
Yeah. And then I’ll just add, there’s a feature called Reduce Transparency. And when you turn that on, it will basically draw like a opaque rectangle behind the vertical bar. And it’s a little bit narrower than the safe area for the vertical bar because you didn’t want it to just like, you know, directly touch content.
And so yeah, I would just recommend, you know, turning that on and making sure your app looks good with it on. Another feature that I don’t know if we would think of as an accessibility feature, but I think it kind of might be, is this feature that was in the announcement keynote where you can set the device down and basically tell it to take selfies and it just watches you.
And when you or your group pose or stop moving, it just it takes a photo. Smart Take. Yeah, Smart Take. Thank you. And as soon as I saw that announcement video, I went to our labs like, oh, I didn’t know about this. I’ve got to try it. It’s so good. Yeah, it’s pretty cool. So good.
All right. Oh, this is this is a great question. I’ll start with start with you, Nate. And then we’ll see if Brandon or others want to want to chime in. 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 or I guess, as something else?
I think we want it to be as cohesive as possible because some tasks will be started, closed and finished open. It’s very fluid, so we wanted to make sure it feels like one singular thing, not a phone when it’s closed and iPad when it’s open. It’s one thing you don’t have to like manage windows differently between the two states or have different settings for the different states of the device. So I think it’s It should feel like you can be open or closed. And it’s the same product. I think that’s the spirit of it.
And it’s an iPhone. It’s the it’s the device you carry with you everywhere. It’s. So that’s really important too, that it feels like it’s an extension of the phone you had before. And then it’s just way more adaptable and can be used for lots of different things. Yeah, I think at a high level, we just want to make it feel like, you know, when, when the phone is closed and you open it, you’re just resizing your app to be wider, right?
And you know, so it’s almost just like your whole app is a resizable window that you’re dragging, except you’re just unfolding this phone. Right? And I think the transition between, you know, closed and open really tries to emphasize that, that it’s all just this one experience. That’s seamless.
Thinking about the apps in particular. I’ll start with you, Immanuel. Like I haven’t got a chance to play with it. How does Maps adapt when you go from closed to open? What’s that experience like? Yeah, definitely. So when we’re portrait closed, we have like the sheet coming from the bottom. When you open it, the sheet gets deleting placement. So you see a lot more map on the right side. So it’s using the iPad app, sorry, the iPad layout on the inner display.
And then, you know, you close it. It goes back to like the standard iPhone portrait. Funny enough, it’s like similar to like closed landscape, right? We also have like the sidebar, I keep saying sidebar, but it’s a sheet that is a leading placement. Yeah, sorry, we call it internally sidebar where we’re bad.
But yeah, it’s like a similar thing when in landscape. And yeah, our map view also we do a little bit to like do some reframing to make sure that like, say, if you’re viewing a place card, it’s like centered in the, in the screen. Yeah. How about on TV? Is there anything interesting about that adaptation?
So yeah, when we open, we basically show more content. We would show more details. So for example, you know, in the homepage we have this hero header where we show trailers. So when we open, we can add the description of the trailer and some more info than you would get some more look ups of, you know, content. So it basically feel like you stretch the window and you can see more. Nice.
So another design question. Start with you on this one, Brandon. How should apps that use a three column layout on iPad adapt to the duo? And we might have a sample in on the. Screen we do. Yeah. Just follow this. But you can see what’s happening here, right?
Is you get two columns at a time, you know, so there’s a button in the top left that shows you the, the height, the root column as an overlay. But, but yeah, I mean, it’s, it’s worth considering the different orientations as well, right? So if you’re in portrait, for example, right, and you’re looking at the Mail app, you’ll see, you know, just the detail view. And if you, if you press the button in the top left, you’ll, you’ll get the sidebar as an overlay and you can pull it in and actually see those two root views next to each other.
Anything to add to that, Nate? No, I think that pretty much covers it. And the same is true on a like a pro Max in landscape. That same app kind of construction applies there, and you get the drill in drill outs that you’re familiar with on the smaller phone. And yeah. This is the point to say which system components people should be using for that effect. Tommy. If you’re in SwiftUI, you can go to NavigationSplitView. And if you’re in UIKit, you can use a UISplitViewController and you can make your own great Mail experience.
Excellent. Also, maybe interesting to point out that if you’re using a TabView or UITabBarController, you can configure that to show the the tabs as a sidebar when you’re in open wide. Right? So that’s another thing to think about that not quite the three column route of our question here, but it is another choice. Yes.
One other thing to add is if you do use those UI components that Tommy mentioned, then you get some nice features, like when you go like partially open, like a book, then the split view kind of automatically resizes and takes up 50/50 of the screen. So you kind of get that for free by adopting the UI frameworks. Nice. Excellent.
So this is a, a technical question that I think we address a little bit. But but let’s swing back to it. And Tommy, maybe I’ll let you start with this. But how will apps that don’t yet support duo. So they’ve been linked on 26. How will they be presented in the various poses.
So we talked about a little in general, but we didn’t talk about all the poses. Yeah. So on the cover display you will see basically the ratio of an iPhone mini for your for your application. So there will be a letter box on the, on the side with your where the vertical bar would be.
when you open up your app or open up your iPhone Duo on the Inner display, that same ratio will be in the middle of the screen. And so it will in both landscape and portrait. And you can expand that and kind of zoom it in, but it’s not, you don’t get any reactivity to any of the different poses. If you put it in like a seated pose or anything like that. Yeah.
I think as someone who used to be a third-party app developer, like I think this is going to be a great opportunity for some apps to stand apart because I think people who are getting the iPhone doing are excited about it, are going to be not excited about black bars. Around. Apps. And so they’re going to gravitate to the ones that are ready. So.
Here is a Safari WebKit question. I think, Tommy, you looked into this a little bit earlier. What new APIs will be available in Safari and WebKit for detecting poses and other new duo hardware and display features to adapt web pages. Yeah, so there’s some existing JavaScript standards around foldable devices. I would look to those for adopting any foldable content in your app.
I’m not an expert on WebKit, so I would stay tuned until the SDK comes out and, and you can try out those experiences in your own web applications. Yeah. We don’t have any WebKit experts on stage. On stage. But when the SDK is available later this month, please try it out and file feedback.
If there are things that don’t work and we can make sure that that gets seen by the right team. So appreciate the question. Brandon, maybe I’ll start with you on this one. Does each pose need to be manually adopted, or is following best practices enough to likely look good in each pose?
Yeah, I think if you follow the best practices, the app will look great. I think you could go a step further and really think about, you know, how to optimize your app for the specific pose. If there’s anything just contextual to what the app is doing, that would make a lot of sense, you know, so the example earlier, you know, the video player, the and the podcast player, the controls are, are at the bottom when it’s seated on a table, which is really nice, right? So you can just like tap the controls and the device is stationary. And so yeah, any, anything where you can kind of go the extra mile and make things a bit, a bit more, more fun and useful would, would be great. Yeah.
I, I think there may be a. a piece of sort of strategy there in adoption also. It’s like we’re not giving developers a huge window to get ready for this device to be available. And so following best practices to get a good experience out there on October 23rd.
And then there’s, there’s time to iterate, right? We’re always making things better, which is part of what makes this industry so fun, I think. Yeah, I think we learn one lesson ourselves. I think when we were designing for this, where we kind of had this overlay of all the different poses you could possibly be in, and by doing that, it almost created a goal out of like filling each pose with something exciting or something new and novel.
But as we got further along, we realized like, there’s some staples that if you support those, you get support across everything. And then you tend to know like for your given app, like, is there something that’s really valuable in a given pose? Like don’t force it. Like you’ll know if there’s a better way to make use of this display size.
Or there’s like a, some kind of situation where someone’s going to use a device, the device in a particular way, and your app would be great designed for that. But yeah, don’t feel stressed about having to sizzle up every single pose. You can get pretty far by supporting kind of the basics. Yeah, I think too, one of the things that, that we, we found too is thinking through what that transition, right?
Like for if you have one pose UI in seated pose and it’s entirely different than when you’re flat, you have to think about how that actually transitions. Can be disorienting, right? Yeah. And so, so if you think through those transitions, you, I know when we talked with a lot of app teams, we came to kind of some natural conclusions around what the right patterns actually were that you could smoothly animate to those different experiences. Yeah, I think, I think that last bit is super key, the smoothly animate too.
And one of the things I love about the TV app, when you’re watching something and then you go to partially folded. It’s not just that the controls separate from the, the video that’s playing, it’s that they slide apart. It’s like your eye follows to where the pieces are going. So it’s not jarring. It’s like, oh yeah, I see what happened. That’s pretty cool. And if you use ArrangementViews, you will just get that. On message. Thanks, Nina.
So this is a variant of a question we had earlier. And so maybe I’ll just take this one. Can apps use both screens at the same time to open up new features? It’s kind of a yes. And apps that have active camera sessions can use the inner and outer screens simultaneously. So an example of that that ships with iPhone Duo is Kid Cam so a parent or someone can be holding the phone looking at, you know, big picture on the inner display using one of the great rear-facing cameras.
And then Snoopy can show up on the outer display to get the kids attention. It works on me. I suspect it’ll work on kids. So I think that’s pretty cool. But it’s only camera apps that can use both displays at the same time, and only apps with an active camera session.
Nate, I think I’ll start. Start this one with you. The Inner display has regular horizontal and vertical size classes. Currently our app only supports iPhone portrait and we don’t have iPad support, but we’d like to have a different layout for landscape and portrait on the Inner display. What’s the recommended way to distinguish between them?
I guess from a design standpoint, would we want people to distinguish between the two orientations on the. Between portrait and landscape? On the inner. Yeah, I think it does make sense. I think there you start getting into kind of available width. So you might go to a two column like let’s say it’s a.
Like in the App Store, for example, like we might show two columns of things landscape and then a single column of things vertical. We do similar things in the Health app. So yeah, I think there are legitimate reasons to switch layouts, but it should still feel like the same content, just rearrange to make better use of the space. Sure. Yeah. And technically, and maybe this is where the question is coming from. And Tommy, you can correct me if I’m wrong here. I hope the although we don’t respect the supported orientations on the Inner display.
We do provide the current orientation in the environment and as a trait. So between the size classes and reading the orientation, technically you can differentiate between the two. Yeah, I do think there are better ways though on this on iPad and on duo to do that than just reading the orientation. Right? Like I think you can have, especially if you’re resizing all the way to iPad, right?
You can make a very thin window on iPad that is technically in landscape orientation. And so that’s where it goes back to, right? Like when you’re in regular, regular, really thinking about like, what is the width you have and the content that you’re trying to display in that? And right. If you look at like split view controller, that’s going to do something specific off of some size metrics. And so in a number of other framework components do that as well.
And so I think that’s where if you have these kind of like container level framework components, they’re going to do the heavy lifting for you. And then you can think about if you have grids or things or different things like that, adapting them to the actual space that you have. Great. Excellent. Thanks for thanks for clarifying that.
So Tommy, I’m going to stick with you for this one. 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? There is not. Once you link on iOS 27, you get iPhone Resizability.
I think thinking about right, going back to the conversation we had, though, is kind of more like a meta point is you don’t have to on day one, have the, The absolute perfect pose. Layout for every pose and things like that. Right. Thinking about kind of what are the things to get the ball rolling on Resizability is going to do a lot of the heavy lifting for you and, and be able to get your app into a state where it’s going to look good on iPhone Duo. And then and then you can iterate, right?
You can, you can look at some of the new APIs or things like that. So. Right. We definitely saw throughout the whole design and development process that app teams, even with just 1 or 2 engineers, we’re able to pretty quickly get something that looks great on the display. And then and then is the time where you put in the months of work where you try to perfect it and stuff like that. Speaking of app teams, I’ll start with you, Immanuel.
I know not all of the members of the app teams were working on. iPhone Duo. It was like a small group of y’all that were. Yeah. Is there is there anything that you you want to say about that and sort of that process? Or you know, how focusing like that helped to deliver the basics to be ready for day one?
Yeah, definitely. So I think like the limited disclosure was like actually pretty good because it meant that like, everyone could focus on like adopting the system components. And if we adopted those patterns to run on existing hardware, it’ll just like translate over to the duo. And we saw that like Find My before this had custom sheets, custom tab bars, custom nav bars, and they just adopted everything and they just got it all for free. I actually did not do that much coding on Find My this year.
And similar with Maps, we had already adopted the sheets a long time, but we had to adopt the bars and that also that also worked out like, yeah, I, I really think that we, we literally did not do anything specific for this. So it was really just me like monitoring that progress and like, you know, maybe helping them prioritize a few or a few feedbacks and.
But yeah, that, that was pretty much, I mean, it all just worked out well. Nice. Nina, do you have anything in that vein? Yeah. So I think supporting Resizability was a huge part of it. And basically with just supporting Resizability and, you know, implementing best practices about using layout guides and things like that, we got the app looking good on the duo.
I was basically testing and, you know, most of the bugs that I found I could reproduce with just resizability. So that was yeah, that really helped out. And then, you know, on top of that, we like the small team just added the features for folding and things like that. But best practices will basically get the app works really nice on, on the duo. Excellent. Great, glad to hear it. So the next question is actually a very good follow on Immanuel. And it mentions Find My in particular.
So on iPhone currently we use a panel overlaid on content like Find My. So I’m assuming it’s their bar with a sheet behind it. Should those sit side by side on duo? Should the tabs move away. What did Find My do for that look? Did you keep the current look?
I’m not sure if I’m understanding correctly actually, so I. I can also pull out my phone. Sure. The camera’s not gonna be good enough to pick it. Is the panel a sheet or. Yeah, so I dropped the initial part of their question, which was about a, an adapting sheet presentation.
Yeah. And so they’re, they’re wondering about separating the sheet from the tab bar because their current style is like Find My where they’re in one spot behind the tab bar and they’re wondering whether with the wider space, they should pull those apart or tab bar to the side or. Yeah. For Find My, I mean, we, you know, we viewed the inner display as like an extension of an iPad and the sheet, the tab bar was already embedded in the sheet. So we just kept that. We just wanted a consistent look and feel across devices.
I think it can also vary if the, if the tabs apply to all of the states of the sheet, then it makes sense for them to be together, which is the case with Find My, right? Any tab you go to is populating the sheet with the contents of that tab. So it’s keeping them together makes the most sense. Or you’d have these disconnected things that are related, right? But there might be a different app where like a tab has its own sheet. And maybe they do make sense to be separated. Separated. Yeah.
Yeah. That’s great. That’s a good way to think about it. I hadn’t thought about it that way. In a sense. Find My tab is selecting the content of the sheet. Yeah, exactly. Yeah. Like Find My and Maps are like very unique where like all our features are within the sheet. Like we have the map that provides the context and the backdrop, but like, you know, everything is in the sheet. Yeah. Nice.
Another interesting question. And Nina, this might be a good one for, for you to start with. It ties into the answer you had just been giving until the iPhone Duo simulator becomes available. We’re using resizable iPhone and Device Hub for preliminary testing. Could you clarify what types of issues can be identified using this approach, and maybe what issues can only really be detected once the iPhone Duo simulator is available?
Yeah, so… I think with Resizability you can detect things. I remember like the, you know, if you if you view, for example, interact with the corner of the window. This is things that you can identify, which means you’re not following the, the correct layout guides. You would. So on the Duo, you would find more things like the vertical bar, which makes the safe areas margin asymmetric.
So like, you know, one of the best practices is don’t assume that your safe areas are symmetric, right? But yeah, I would say most of these, most of the issues you would find with just iPhone Mirroring sure. The safe area things is interesting and made me think of something else, which is a lot of phone apps that have been locked to portrait have only worried about top and bottom safe areas. Yeah, safe areas are on, the unsafe areas are on the side often now. And so that’s another thing to watch for.
Yeah, exactly. And especially where, you know, the vertical bar can be on each side. So a lot of assumptions, assumptions that you would make, you need to basically not make them and just follow, follow the best practices and layout guides and. And often you don’t know that you made them, you got it, you got it working. And you discover that, oh, we made an assumption. Exactly. Yeah.
Yeah. I mean, it’s also worth noting that the content insets are also asymmetrical. And so, you know, it’s important to, you know, use the real content insights from the system and not, you know, assume that one side is equal to the other side. One side and then balance it. Yeah. Yeah. Great point.
All right. We have about four minutes left. But let’s see how many questions are the ones remaining we can knock off in our four minutes. So I’m just going to throw questions out. And if you know the answer grab it. So you all got to pay attention. Is it possible to support a full screen only app, for example an immersive AR app?
Yeah, I mean it, it’s would be the equivalent of just building an app like any other app and hiding the status bar. And you’ve got a full screen app. You don’t have to use the vertical controls if you’re if it doesn’t make sense, right? Yeah. Totally cool. All right. What are the biggest design mistakes you’re seeing or have seen in iPhone Duo apps?
That’s an interesting question. They would all be our mistakes. That’s true. I think this maybe gets back to what you mentioned earlier. It’s like trying to design for every pose and pulling back from that. All right. I’m not going to leave you on the hot seat. We’re trying to get through a bunch of questions quickly. This one might be a great one for you, Brandon. Can you clarify how multiple instances of the same app work on iPhone Duo? It works in a very similar way to iPad.
It’s it’s pretty much the same feature. So you can have multiple views of, of your app open at the same time. You know, they could be side by side with each other or they can be, you know, next to other apps, they can be paired with other apps.
Yeah. It’s yeah, the same feature. Right. And there’s, there’s a technical question buried in here which is if both instances and maybe Tommy, you can take this one, if both instances are using, for example, app storage, do they share the same state? Yes, the same app. Yep. And so the update there would be the same update mechanisms that SwiftUI or UIKit currently use. All right. I think we’ve got time for one more.
I have no idea what the answer to this one is. So maybe somebody else does. On iPhone Duo is the core motion device reference frame fixed to the chassis or normalized to the active display, i.e. is the accelerometer axis to screen mapping the same in folded portrait and unfolded portrait.
I think the answer is it’s magic you don’t need to worry about. All right, write that down. It is magic. Excellent. And I’m afraid that is going to bring us to the end of our questions for tonight. A huge thank you to Tommy, Nate, Brandon, Nina and Immanuel for being on the panel. I had a lot of fun. I hope you did too. And really appreciate your time. It was great chatting.
And to all of you watching around the world, thanks for tuning in. Your interest and enthusiasm for iPhone Duo have us all even more excited to see this new iPhone in people’s hands soon! If you have more questions, tune in at 8 a.m. Pacific Time tomorrow for more conversation with another panel. Catch you next time!