2026-09-17 • iOS • 1:01:29
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
Hi. 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 Apple’s developer website, please submit your questions in the panel on your 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’ll 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 today’s 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 all these teams pulled together to make it happen and deliver this incredible experience. So before I jump into questions, I’d love to have you each introduce yourself and say a little bit about what you worked on for iPhone Duo. And I will start with you.
Yeah. Hi, I’m Anna, I work on the UI frameworks team and for iPhone Duo, I worked on the controls that moved to the side. So that’s your navigation bar toolbar. Moving to the side on this device. So it’s really exciting. Hey, my name is Louka. I’m an engineer and I worked on Music, Podcasts, and iTunes Store.
Cool. Hi, I’m Ryan. I come from the communication apps team. And so I worked on things like phone and FaceTime modifications for iPhone Duo. And one of the features I’m personally hyped about Duo FaceTime, which I’ll totally use all the time with family. Yeah. And I know folks last night had camera questions, so we’re excited to have someone to share with us to, to take some of those today. Maria. Hi, I’m Maria. I’m a human interface designer and I specifically work on our design systems. So I’ve worked on many different parts of it, but a lot on bars. What Anna and a lot on adapting layouts to folding.
Excellent. Well, thanks for those introductions. And let’s jump into some questions. So the first question comes from Greg. If your app is oh let’s see. And I’m going to I’m going to start this one with you. Yeah. If your app is running full screen on the inner display and then the user closes the device, does that move to and continue running on the outer display or is it backgrounded?
It’ll continue moving on the outer display or it’ll move to the outer display. So as someone who’s using the device, it’s effectively you’re using it, you close the device and it’s just like the app has gotten smaller. That’s how it feels like. Okay. There are a few edge cases though, like with multitasking. Yeah, I’m not sure if you remember the details of those, but I know sometimes the app, like the app you were using, may get backgrounded or sorry, the app that you were using may move. Yeah, my understanding from Chris and Alex is that it depends.
Okay. So if you’re using Split View multitasking, you have two apps on the inner display. The system will try to promote whichever one you are interacting with to the outer display. And the other one will be backgrounded and something interesting and to test with. And we’re not sharing the exact timing.
If you then open the iPhone open iPhone Duo again, if it was rather recently that you closed it, they’ll both come back. But if it’s been a while. The thought is people using the device will expect the app they were using on the outer display to take the whole inner display. And so the system does a little bit of magic to try to decide what people will expect.
All right. I think this one is a question for me, but maybe I’ll can chime in. Is there an anticipated release date of Xcode 27.1 available? And all I can say today is coming later this month. But in the meantime, and this might be a question for Louka or Ryan in the meantime, are there any other methods that we can simulate or use to simulate how an app might show up on iPhone Duo?
Well, I think yeah, the best thing to do is just run your app on iPad and just turn on window resizing and just play with it and make sure that it reacts like adapts to different window sizes and make sure you follow best practices for window scenes usage. Of course, don’t use the main screen.
Like don’t, if you need to call into the main screen or screen, do it through the window scene. Right? Yeah. iPhone mirroring as well. I think if you have an iPhone only app right now, then that’s another great way to do it. Excellent. Thank you all. Let’s see.
I think this one might be a short answer, but maybe Maria will start with you. When iPhone Duo is partially folded in an L shape, can an app receive touch input from both the inner and outer displays at the same time? Great question. I think no. I think no.
I hope not. I hope not. But if there’s a great idea out there, we’d love to hear about it and then we can talk about it more. Yeah. Yeah for sure. That’s a that’s a that’s a great point. Feedback on use cases is super helpful. So love getting feedback reports.
If the feedback report isn’t just this is wrong or I need this, but it’s here’s what we’re trying to accomplish for people and here’s what we think would help. That is great feedback. That’s actionable. So appreciate. That. Me personally, I, one of the things I love is just seeing how creative developers are. And so I’m super excited to see what things they want to build that we haven’t thought of yet. Yeah, yeah.
We want to hear it. Excellent. And I’ll start this one out with you. On iPhone Duo, the tab bar becomes a vertical bar on the right. What happens if our tab items use text labels instead of icons? Is text supported there, or should we design for icons only?
Yeah. I mean, so in terms of if you’re only using text labels and you haven’t set an icon that will still be able to go vertical. However, I’m not entirely sure because by default the tab bar shows the icon representation, and when someone interacts with it, that’s when you’ll start seeing the labels. So I would say it might be a little bit confusing for people who use your app if you don’t have icons. Maria, what would be your guidance for an app that’s maybe in this boat?
Yeah, I think I would just think about making those icons happen and like finding the right ones. I think it’s good in general for like a number of different features that could help It helps recognition. There’s people that understand iconography faster. There’s people that also understand text faster. So like, I do think there’s benefit of having both available.
I’ve also not seen a lot of words that cannot be represented by some icon out there. We have a very big library of SF Symbols as well, so over 7,400. There we go. So hopefully, you know, some of them in their work. But yeah, I think my guidance would be to just try to get them in there, works better with the design that we’ve made.
Yeah. And I want to, I want to highlight a point you mentioned, Anna, which I actually learned about last night when you’re in this didn’t show up in any of the videos so far, but when you’re, when a person is, is scrubbing the tab icons in, in the bar on the side, the labels do appear, which is a different experience than on any of our other phones so far.
It’s really cool. Yeah. Nice. And something to be aware of to roll a custom, a custom bar, is that there are a lot of things here that an app would have to emulate in order to feel like it was a natural part of the device and so great time to reevaluate whether you want to use native components. Yes, but also one thing that I may add on that is if you are building custom bars, first consider if you can use the system one.
Speaking as someone who works on system bars, they are very You do not want to get into the business of building your own. But if there’s some reason that you absolutely can’t. One API we have that is new in 27.1 is the ability to grab out the region that the system bar would draw in, and that’s helpful for making sure that you’re putting it in the right place so you can request, hey, I want a bar that is, you know, like the trailing bar, and then you can know where you should put it. So at the very least, you’re not just like guessing.
Yeah, yeah. And speaking of that bar region, actually music uses it for now playing and so does podcast. Well, music specifically to place the lyrics, the voice attenuation button and to reduce the vocals and the translation button. Also, we do make use of that space specifically to just put two buttons Awesome.
All right, Maria, I’m going to start this question with you. How much should we differ between Duo landscape and iPad landscape in our UI? Great question. I think in general, the way we’ve been trying to think about this whole year, like with Resizability as well, is like space availability first, right? Like you are just going for more space. So like multi-column layouts, like sidebars show up. So like there’s a lot of similarity. Even if you rotate like a max phone and a small iPad, like you’re going to see a lot, a lot of similarities in layout.
So start definitely with designing for size classes and like just making sure the layout like feels good and it’s like using all the space and like nothing looks like overly stretched or like the opposite of like overly narrow. And then you kind of like layer on device specific.
So like, obviously the way you use an iPad and the way you use even a foldable phone is still different, just like contextually, like as you go on for your day. So I would say, yeah, start with size classes, design for that. And then what differs will be platform standards between iPad and iPhone, which are pretty much the same as they are today. Yeah, that contextual piece was a big learning for me as I was like coming to know the device because people are going to pull an iPhone Duo out of their pocket and open it up and do things with it.
Unless you have very large pockets, you’re not pulling an iPad out of your pocket typically. And so that’s just sort of very slightly different use cases there for sure. And I think we even like asked that ourselves, like as we were designing because a lot of our apps, maybe you guys can share, like have iPad apps, like a lot of people’s kind of like natural reaction was to pull those iPad designs. And we had to do a lot of work to like just look at it and be like, okay, this is now the iPad design, but this is a phone.
And I think we’ve said that probably like I was like, this is still a phone. This is still a phone. Like, let’s make sure it feels like a phone. So like for apps out there and developers that do have iPad apps, I think that is kind of still a good place to start, especially if you’ve not done Resizability work yet and just kind of start looking at what feels natural, what doesn’t feel natural, and then potentially strip out anything or like change it, guard it, maybe behind an idiom if it feels like it should belong only on iPad.
Yeah. That’s interesting. Ryan is there. What are some of the differences between FaceTime on the Duo versus FaceTime on iPad? That’s a great question. Actually. One thing that just came to mind for me was, so in iPadOS 26, we brought the phone app to the iPad for the first time.
And on the iPad phone app, we have the dialer in a popover because you’re not typically dialing up calls by a number on an iPad, but obviously this is a phone. And so we wanted to make sure even though we could, we could have just brought the exact phone app to their.
We wanted to make sure we actually promoted the dialer to its own tab, because this is a phone and people are going to be dialing. So, you know, making intentional decisions like that, like this is a phone. So how do people use your app differently because of that? One example that comes to mind. Yeah. Interesting. Interesting. Are there significant differences in music between iPhone and iPad or Duo?
Well, I would say the sidebar is probably the biggest difference, But we didn’t have, we weren’t making any assumption like in the rest of our UI about, is this an iPad or is this an iPhone? Like pretty much using system standard and not making, trying to distinguish between the two, which I think most of the apps want to do anyway. Now that’s great. I love those two contrasting examples. Yeah. You know, it’s maybe not immediately actionable. It’s it depends. And you have to think about your app and how people will use it. So all right.
And I think I’ll start this question with you, I think I know the answer. I’ll see if I’m right. Could we develop apps that work on the inner screen while in standing or tent mode, similar to the glowing alarm clock that was demonstrated? Oh goodness. I work on bars, Curt.
I think the answer is no. Yeah. Because if you want to have two displays on the same on at the same that is generally the camera accessory, which is really only for camera apps. So I, yeah, I think the answer for that would be no. I mean, I think we just want to hear the use case. Yeah. Again, feedback example. I do know that apps that use AlarmKit get that feature. It’s provided by AlarmKit. Right. So you can do sort of that glow when the alarm is going off. But beyond that I think that’s all we provide now.
I’m not sure who to give this one to, so I’m going to pick Maria. Is it possible to release an app that’s only available for iPhone Duo? I have no idea. But I would say why. Right. Going back to that, this is a phone type of situation and answer. This is a phone.
So like why would you want your app to run only on this device and not the rest of them? So I think just conceptually, I would hope that people the same way, like you don’t probably not run your app on like a smaller iPhone or a bigger iPhone. You just support the whole lineup. I would hope that duo just becomes like a natural addition to that.
Yeah, I think I’m interpolating a little bit here, but I would think I think this question might be also somewhat to is it okay to just design for one pose And. And you know, the answer there is no, probably not. People are going to use the device as they want to use the device. And so if you’re forcing people to use it a certain way, they’re going to look for a competing app that you that lets them use the phone the way they want to use it. Oh, here’s a friendly, a friendly question.
And maybe we’ll start with you on this one. Anna. I’m going to read the whole thing because it’s so charming. Hello. I hope you’re all doing well. Thank you so much for making this session possible. Will iPad apps be able to run directly on iPhone Duo in a compatibility mode, similar to how compatible iPad apps can run on Apple Vision Pro? Thank you cyan.
I’m actually also not sure of the answer to that question, but I would expect and also hope that if you are an iPad app, up. Can you support. You know, like if you if you’re supporting iPad, you’re having to support Resizability. You can resize your app to a size that’s really similar to an existing iPhone.
And also several of the different poses on iPhone Duo. So maybe consider also if your app can be available on phone. Yeah, I think, I think the guidance there is make the app universal and iPhone to the list of supported platforms. And that’s the first step to get your app onto iPhone Duo.
All right. Oh, this is this is another one I’m gonna throw your way. Anna. How should apps preserve navigation and UI state when users switch between the inner and outer displays on iPhone Duo? Yeah. I mean, I would say that in general, if you’re using system navigation controllers, they will adapt for you.
It’s not like your app is getting created on one display and then torn down and put on another display. It’s really that you’re getting resized. I’m actually curious. Louka and Ryan, how have you found that in your apps? Like what? Like when this transition has happened, has there been anything that you’ve really had to do? Or is it just like you’re. I don’t know, getting resized on iPad? Well, I think nothing except for now playing. I think there’s a tiny detail that is, if you open the device, we put you into the lyrics mode because of course we have more space. So you could be closed, not have lyrics up.
But when you open it, because we have more space, we want to use that space. That’s the only thing that we were like, the only thing we were checking that is very special to this device, like changing the layout because it’s wider can kick you into lyrics. And that’s what we do. What happens if you then close it. If you close it, we put you back to normal lyrics because you don’t want to disrupt that.
It’s so again, it’s interesting, but like it’s, I was playing with it and I was like, I think this is the right thing to do. And like, still to this day, I think this is still the right thing to do. But if you don’t, then please file feedback. Ryan, do you have anything to add on state management?
Not much, honestly, but I think, you know, using the system components, it was just cool to see how much we got for free. You know, like using split view and it just automatically adapting. So, you know, a great excuse to try and move over to as many as much system components as you can. Yeah, I appreciate that. And I didn’t pay our panelists to say that, but maybe we did.
I also appreciate that, you know, that came up with Maps moving to, to native toolbars was a big thing that they’d been looking to do and use this as an opportunity to make happen. I think the other thing I would say is, particularly for this device, one thing that I see SwiftUI apps sometimes do is in a complex size class, they will use one container on one side of an if statement, and then they’ll use a different container on the other side of an if statement.
So if you and oftentimes that if statement is guarded by size class. So if you were doing that, you will see state loss. If you haven’t raised everything up because of the fact you’re switching between the two branches of an if statement, or you could be when you’re going from the inner screen to be closed. So if you are seeing that, take a look.
Consider this as an opportunity to see if you actually need to be doing that. Yeah. That’s a great point. Yeah. Because it’s always it’s already been an issue on iPad and resizing. That’s something your app is probably running into, but this is a new way that you might be seeing it manifest. Awesome. Thanks for thanks for bringing that up. Let’s see. Ryan, I’m going to start with you on this one. What’s the one thing developers should start looking into today before the new Duo simulator is out in Xcode 27.1?
That’s a great question. I mean, I think obviously just making sure your app responds smoothly to being resized. And like we said earlier, I think iPad is a great way to do that. And, and honestly, just a great excuse to try and make your app as universal as possible, making sure it can flow between, you know, iPhone mirroring and, and iPhone and iPad seamlessly try and share the same code as much as possible. Yeah.
Another thing that that came up last night was asymmetric safe areas and, and content margins. And the fact that if you’ve got an app that has been, you know, locked in portrait mode, you might only be checking top and bottom safe areas, you probably want to turn that off and test your app in landscape and see how it works with leading and trailing safe areas, because that’s been a spot that some folks have made assumptions and maybe not tested those. And hopefully if you have a sidebar and your own iPad, you have an iPad app and you have a sidebar, then you’re already doing that kind of because of that leading safe area.
Oh, sure. But yeah, so I’ve seen, I’ve seen places in the code where like, it’s only in the leading edge or so that we honor it. So. Yeah. Or people will check one side and say, oh, the other side must be the same. Right. Yeah. Yeah. Look for a two x on a width. Dot left times two. Yep.
Do not. Ryan. I’m going to start this one with you also. And I think I might know the answer, so I’ll see if I. I’ll see if your answer matches the one I have in my head. Many camera apps use fake auto rotation so they. They lock in portrait and rotate their UI elements individually.
How best to adapt this to iPhone Duo? Yeah, that’s a that’s a great question. So actually there’s like two new APIs that our iPhone Duo specific. If you’re a camera app that you might be interested in one of those and I might get the name wrong, correct me, AVCaptureDevice rotation coordinator. I knew it, okay.
And so that will help you figure out the right rotation to do for your camera view in the UI. And, and believe me, coming from the FaceTime side, you don’t want to have to roll that you’re all by yourself and try and figure out, you know, where are you located on the iPhone Duo? Definitely try and make use of that API. And the other one that’s coming Am I getting that one right? Got that one right. Okay, cool.
And that will tell you If. Since there’s two front cams, you may have previously made assumptions that the front cam is the one facing you. But that’s not always true. And so that API will tell you basically you know, what direction the camera you’re using is facing. Is it facing towards the user or away from it? This is a great opportunity to use that device in front of you as a prop. Yeah. So when you’re, when you’re actually using the camera, you can flip it around and bring the camera apps to the front display.
And so yeah, because it’s so dynamic, you know, you have to, you have to make sure the front cam you’re using is, you know, you want to check the direction, maybe like flip the video if it’s facing the user, facing away from it to make, you know, the selfie feel more natural.
So yeah, all those, all those considerations come to mind. So both those APIs and the, a lot of great diagrams about how cameras can swing around in space are in the. Build a great camera experience for iPhone Duo video that we released last week. It’s a short watch, but a very important one if you have a camera in your app for sure.
This is an interesting question, and I think we may have to all chime in in order to get to an answer. I’m going to start with you, Anna, because you’re closest. I did not see a way to know which mode I think pose is what they mean. Here. The duo is in. How do we know if the user is in laptop or desktop mode?
It sounds like we need to manually use the hinge APIs. And how does AVPlayerViewController do this? Yeah, definitely. I mean, that’s a great question. Quite frankly, when I first saw the device, I thought, oh no, what am I going to have to do to support all of this? And honestly, I think some of the new APIs that we’re releasing really help with this. I think one of the things that I think so system containers will adapt if you want to support a particular pose.
So like laptop or book, I think my first question would be, what are you trying to do there? Because the guidance is you want your app to feel similar across poses. It’s adapting, but it’s not massively changing. And so one of the new APIs that I would think about is ArrangementViews, where it’s a little bit more semantic.
You specify your views in the relationship, and then the system uses all of the context in order to figure out where to put them. So I think that would be one of the starting things I would think about, but I would be curious to hear. Well, I know that AVKit does use ArrangementViews for Music. I’ve been using the reserved region to know where the division is and. And from there you can just, you know, arrange your layout whenever it is active or not. As simple as that.
Maria, are there any videos that might talk about what people should be doing here? I’m so glad you asked. I wonder why we do have a really great video that goes in depth into ArrangementViews and like some of the system component behaviors and like reserved regions and all of that. It’s called strike a pose with iPhone Duo. So yeah, I would go and watch that and see if it answers the question. But I think echoing what everyone just said, like, start with the system components.
Your layout probably in 90% of the cases, does not need to do anything special in those poses. If you are kind of like a streaming app or something and you want to do something fancy with your player, like think about that. Look into those APIs. But for the other 90% of use cases, I would just say your app just needs to work.
And also, we’re going to learn a lot about how people are using this device so I wouldn’t almost like overoptimize. Like straight out the gate. I think we even internally have been talking about like, for example, when it’s partially folded, like, is this going to be like a dominant way people use this phone? Or is this just going to be like a transient moment as they’re moving to the outer display? So we don’t know.
We’re all going to learn together, both at Apple and all of our third-party developers. And yeah, then I think once we know a little bit more would be more appropriate to kind of go all the way and like add some sparkle and some special sauce to your app. Yeah, that’s a, that’s a great point.
And we’re not giving folks a lot of time between now and October 23rd. So getting the solid basics in place first is clearly the right move from a business standpoint to. Yeah, get be resizable. Yeah. And then maybe tune for the device. But also if you’re trying to tune and you’re finding, hey, there’s this other information or these other use cases that I’m running into that I can’t build right now. File a feedback, let us know.
Yeah. As always, on a new format, a new device, we’re very much looking to, to adapt because we know we don’t know everything about it. And we’ve got, you know, a few hundred people carrying I’m sitting with four of them and I’m not one of them. But, you know, once we have it in the hands of, of thousands or millions of people in the world, we’re going to learn a lot. So.
I really like this question. Louka, I’m going to start with you on this one. What was the biggest technical challenge when adapting system apps to iPhone Duo? And, and I don’t know if this is going to be throwing shade on anyone, but which app required the most work or was the hardest to write? iTunes Store was the hardest.
This is some a lot of legacy code here that wasn’t really modernized, but to be honest, like it took me probably just a week to move to window scenes, since it wasn’t using window scenes yet. And to adopt liquid glass, as you know, it wasn’t using liquid glass until very recently. And just those two actually helped a lot with iPhone Duo experience by itself. We didn’t do any specific, any pose specific stuff for, for, for that app. And it’s just working nice.
Yeah. Ryan. Do you have have any any input on that too? Yeah, I would think for FaceTime specifically, there were just challenges and, and trying to figure out how people are going to take video calls and trying to optimize for that. Like one of the things that I think of is around specifically the FaceTime camera on, on the inner screen.
And one thing we realized is that people are probably, we want to like direct them towards looking at that camera because it is kind of in a unique location on the right side of the And so we tried to put, you know, the, the most gravity in the UI towards that area so that people are looking at the inner camera.
And so I think video apps specifically are going to want to figure all those things out with their UI as well. And also dodging the inner camera, which you learned the API from, I think. Is it your. Yeah, your talk has the API that you’ll need to adopt to do that.
And so yeah, we’re, we’re using that in FaceTime to dodge, for example, the, your PiP that you can drag around. And we want to make sure, you know, it’s not overlapping the camera on the inner screen and that can come and go, right? Because when the camera turns off, it’s not there anymore. And so you want to make sure you’re properly dodging it when the camera is So yeah, if you’re a video app, definitely start thinking about those things. And today I learned that the self view is called the Me PiP internally. And I love About that. That’s awesome.
Let’s see. I think I will actually take this question and then maybe y’all can correct me if I get it wrong. How can I make an app that works like the alarm clock where the Duo is open in tent mode, but I want my main interface to be on the outside screen, and my understanding is that the main interface will be on the outside screen in tent mode. And so the feature of the alarm clock, where it does the glow on the inside, that’s provided by AlarmKit. I think that’s the whole story there. Yeah.
Technically tent is for most cases, just like your closed landscape view, outdoor display landscape view, just kind of propped up on a table for glanceability. So again, kind of similar to our other poses. Yes, we have really cool use cases like alarms and AlarmKit where you can do a little bit more fancy things. But for most of the apps, it would just be your standard layout and you don’t really have to do anything else. Yeah, I totally understand the question because when I saw that that glow thing, oh, that’s super cool.
Oh, this is this is interesting. I’m not sure we have the right folks here to answer it. But but maybe, and I’ll start with you, as I seem to do when I don’t know who’s going to answer it. Are there any restrictions on animations or update rates for scenic accessories on the outer display?
I’m not aware of any, but that’s a very good question. I don’t know if anyone else knows the answer. Yeah we have. So yeah, we use scene accessories in FaceTime and obviously we’re showing video on on both displays at the same time when you’re using Duo FaceTime. So you can definitely just use it like you would any other apps and you get a full scene.
It’s not like it’s not like widgets where you have to be careful about what you what content you can put in them. You get a full UI scene and you can toss whatever you want in there. Yeah. Yeah. And to be clear, you have to have an active camera session in order to light up displays on both sides of the device. So all right. Great. We did have the right people here. Should have known.
Oh, this one’s fascinating. And Ryan I’ll stick with you on this on iPhone Duo. How does audio mixing work? In particular, let’s say I’m in split view multitasking with two instances of my app open. Can I independently control the volume of each instance? That’s fascinating. I don’t actually know. I don’t know the answer to that, but that’s a really good question. So they do share. It is two scenes of a single app. And I think the audio interface is sort of disjoint from the UI.
And so I would expect it to not be possible to control them separately. Yeah, I guess they could if they’re doing their own mixing themselves through, you know, some audio API that allows that, but you don’t get like two volume sliders, right? You know, in Control Center or something like that. I guess I’d suggest you can run two scenes of a single app on iPad now, and I would expect the behavior to be the same. So, so maybe that’s the right move is to try it in iPad and see what you can do there. Great.
All right, Maria, I’m going to throw this one in your direction. What’s the recommended way to keep important content away from the hinge without hard coding duo specific dimensions. Great question. Please don’t hard code layout specific dimensions or things specifically for iPhone Duo. So I think for a lot of kind of system components. We’ve said this like a million times. I’m going to say it once more. We have done the work for you. So alerts is a great example. You don’t want your alert to kind of be smack in the center when you’re partially folding like a book.
You don’t want it to kind of be in the center. If you have it propped up like I do on the table, we want those things to kind of stay tappable and also stay glanceable, you know, if it is propped up like this and alert is at the bottom, like it doesn’t really read as well as it does if it’s at the top. So we’ve done a lot of that for you. However, if you do have also components that sit in the fold that are in the content area. So something like a UIButton is actually one of my favorite examples. Like if some apps have revenue driving actions, right?
You might have like a buy now there or like an add to cart or like a start free trial or anything like that. Those things do need to move. So those are perfect ones to use reserved regions. If you ever want to move, like just a single element, that’s the perfect API to use, and then you pretty much will know if the fold region is active, and then you can move it to the side of your choice. All right. Great. Another one I don’t know the answer to, but I’m going to mix things up and not ask Anna first. I’m going to go to Louka.
I have no idea about this one. How does iPhone Duo handle an external monitor? Oh, I haven’t tried that one. Well, yeah. I would expect like a regular phone would if I mean, I don’t do that myself. So that would be my guess as well. We don’t have an external monitor here to try it right now. But it does work.
I remember Tommy, who was actually on the panel last night, That worked. Okay, great. Okay, great. The question actually continues. Will it support iPad style Stage Manager multitasking? I think the answer there is going to be no. But I do like the observation that the Duo is more powerful than my M3 MacBook Air anyway. So the march of progress.
Let’s see. Ryan, I’m going to throw this one in your direction. Can an app control when its scene accessory appears on the outer display, adjusting it freely regardless of camera state. The second part, not so much because you do have to have an active camera session in order to turn on the scene accessory.
But when the camera is on, you can freely control that and Chris and Alex have a session you can go watch in the developer app specifically about this. So you can add like a button in your UI that toggles the accessory off and on. And you can also observe like when the accessory is available. So, you know, the camera is just one condition for one accessory is available.
But you might want to observe that because there’s also things like if you’re in split view, when the iPhone Duo is open, then you also can’t use scene accessories then. And so you want to observe the state and you can like, you know, disable the button you have in your UI when it says scene accessories are not available, but you can freely toggle them off and on.
Yeah, cool. Great info. Appreciate, appreciate the shout out to that talk. Also the talk with using the hinge as a whammy bar and a guitar app. That was so cool. So actually I had a teleprompter. Yeah, yeah. What a guitar. App. One fun thing I was thinking of was like an accordion, you know? Oh my God. And so I really hope that if, if someone has a music app that they build, I just think that would be like, so fun. I think we should start a whole band. Yeah, we have a guitar with a whammy bar. Yeah.
So watch out. James Dempsey and the breakpoints. We’re coming for you with our duos. Yeah. Let this be a call out to anyone here. If you have an instrument kind of thing in your app to try and build a fun thing, because I would just love to use that. So I was thinking about a piano app in laptop pose. Oh, that’d be so cool to. See bands forming. Yeah, yeah. You just need, just need a drum kit and we’re set. All right.
Oh, fascinating. And I’m going to start with you on this one. And maybe we’ll throw to Maria to how does the iOS SDK handle asymmetric safe area insets when an app is in split view and right against the hinge on the main display. So I think they’re thinking what happens when it’s on the left? Are there recommended SwiftUI layout guides to keep the interactive UI elements out of the crease zone? Sort of a little bit different there.
But yeah. Yeah. I mean, like, so I guess the first thing is when you’re on the left, like, do you have to do anything for the hinge? And the answer is, I mean, there’s like, if you’re folded in book, you would have that. I would expect that region to be present. Yeah.
But like in general, the system will just move it for you. But then in terms of the asymmetric margins and how you would handle that in SwiftUI, there is a new API for that. I am blanking on the exact name, but it is a modifier that you can put on. Yeah. And then that’ll apply the margins for you so that you can handle that. And that’s really exciting because SwiftUI hadn’t had that before. So I would definitely check it out.
But then in terms of like other things for handling it, I would say like what we’ve said before, don’t make assumptions about them being the same on both sides, right? And if it’s also a question about like moving like the vertical bars kind of moving to the left and like, do you have to like, listen and like swap out the margin values. Like if you are rolling your own.
Yes. Right. But if you’re not rolling your own. No, then it’s just magic that you don’t have to worry about. Yeah. So when it moves to the left, what you’re going to see is there will be a left safe area, but then you won’t see it on the right.
Kind of the reverse of what you saw when it was on the right. Yeah. So in SwiftUI, it’s the, you know, safe area or ignore safe area in UIKit. There are layout guides that you can attach to. And so just make sure you’re doing that on all four edges.
Yeah. The other thing I will say is, because this is a question that we’ve gotten for apps that may not necessarily have a bar, and they don’t necessarily want to respect the whole safe area. They really just want to know if there’s a camera there or if they need to respect the status bar.
You can look at the corner adaptation and so that then you can just respect that specific region and then you can draw everywhere else. So this is something, for example, if you’re a full screen game app that you might consider looking at. Yeah. And that that corner adaptation is a good point. That is one area where the Duo is, is different because if you look at the outer display, the corners don’t have the same radius. You know, the ones away from the the hinge are rounder.
Well, it’s also you have a corner in places that you may not have had to handle a corner before. So it’s also checking in your app. If you maybe did do adaptations for iPad, did you handle all of the cases or do you potentially need to support a few more for Duo? And it’s also the only place that we have a bidirectional status bar. Right? Yeah. That, that actually didn’t come up last night, but we were talking about it after the workshop last night.
And we have examples behind us. If you look at the open, all that is horizontal bars, and it has a horizontal status bar in the top right corner, whereas the one to the left of it, which is open and wide, it has the vertical status bar in the in the sidebar. So that’s another thing to watch for.
All right. I think this question’s for me. Will there be locations for developers to test their apps on real devices before it’s released? So if you go to the developer website, the Apple developer website, the sort of promo page for iPhone Duo has a box for global workshops coming soon. I’d keep watching that space. And we’re looking forward to to seeing you in workshops over the next few weeks.
And I’m going to ask this one of you on the simulator for Xcode. How should we test different hinge poses for our apps? Will there be advanced simulations for people who can’t get a physical Duo? Yeah, I mean, so and also, folks, please make sure that I cover all the features that we need to, but you can change the hinge angle, and then you can also put it into the different poses. So like. Book, open, closed laptop tent, all of those. And I would also say one thing to take a look at is the transitions between poses.
Just making sure that everything looks good when you’re doing that. Yeah. And I would just add to that, the device hub team has done some really cool work too. So you can actually see, you know, in 3D, the device as it’s going through all these different poses. And so I think it’s going to be like super fun for developers to just fiddle around with their apps in the simulator. Yeah. If, if you haven’t seen it yet, the, the video bring your app to iPhone duo has a short demo of device hub and the ways you can change the hinge angle and rotate it and everything.
And it’s neat that basically the hinge angle and the rotation in 3D space is all you need to get into pretty much every pose except for inner and outer displays lit at the same time in a camera app. You can’t do that. But the simulator doesn’t have cameras available to it anyway.
So I actually, I should mention that though new in 27.1, the simulator will launch apps that use the camera. It won’t show anything in the camera view. It will detect that there are no cameras available, but you can actually test Chrome and other things in your app that way, which is a new thing that we we did alongside iPhone Duo. All right.
I’m going to start this question with you. How do apps with bottom controls section above the main content like Find My. So I think this is a sheet with a tab bar inside it. I think that’s the UI they’re talking about. How does that behave in landscape on the outer screen?
Maybe we’re going to have to launch Find My on one of those devices and see what the behavior. I’m trying to like, visualize. Well, but the thing is, there she. Okay, I’m forgetting what size the sheet would be, but if it’s a full size sheet, then like on the display. Yeah, it’ll be pretty big. Yes, I think so.
All right, Louka, testing. We’re gonna we’re gonna come back to that question after Louka finds an answer. But let’s keep moving forward. I think maybe something to say about like sheets in general is like when they get kind of like vertical controls and not right. So like there’s situations where they do situations where they don’t like, we’ve also looked at a bunch of kind of not edge cases, but like more specific use cases where the sheet has a lot of kind of controls when itself, right?
It’s not kind of you’re looking at content in the sheet. The sheet has controls, kind of like for writing tools, I believe was one example. Notes. Yeah, that those are great ones for like a vertical bar kind of felt like Distracting almost, and limiting the space of the controls that you actually will be interfacing with.
But the point is, whether your sheet has or does not have controls laid out to the side, the controls kind of stay with the sheet. So there’s nothing special when you rotate in closed out or display landscape with the bar. So if you have it, you’ll probably continue to have it.
If you don’t, you’ll probably continue having it horizontal. I think that’s like a good blanket case. Yeah. And like a lot of things, you need to know what the, you need to think about what the content of your sheet is and what behavior feels right for continuity between poses. Yeah. So do we learn anything Louka.
Can show you. Maria. Yeah. How wrong did I get it? This is what happens in landscape, okay? For the people at home. What’s happening? So I have so I have find my open right and portrait. You get the tab bar on the side and the sheet like is half open, right? And when you rotate, you get the tab bar at the bottom and the sheet on the on the leading side. So you don’t want to cover the map.
Yeah. I think this is like also like a specific maps use case that the map is such a big part of the experience that like a traditional sheet will actually like what we were saying, like take up the entire display, but in this case, Find My has chosen to like opt in to like a different width. And that kind of comes with like different choices on your bars. Yeah. All right.
I’ll take this one, give you all a break. We’ll Xcode include a new skill that will help developers to do the changes for the iPhone Duo. Yes it will. So we talk about it near the end of Bring Your app to iPhone Duo video. The modernization skill that we introduced in Xcode 27.0 has been expanded for 27.1 to include support for SwiftUI and support for transitioning apps to iPhone Duo. So when the when the Xcode 27.1 and the SDK is available later this month, check that out.
Oh, interesting. And I’m definitely right in starting this question. If an app uses a custom tab bar instead of the system provided UITabBar, are there APIs that the custom tab bar behave like a UITabBar? I would say. In general, no. But. The API that I mentioned previously about the ability to get the region where the system would put the bar is one hook that if you’re doing something more custom, you might be able to use if you need to it to continue to be custom, but I would also consider if using the system like containers is an option, just because then it saves you a lot of work.
Yeah. And I think the other thing to point out there is even if you’re using UITabBar, you’re also not going to get the adaptation to the vertical axis. Yeah. So if you’re using UI tab bar, UIToolbar, UINavigationBar, that is just going to stay horizontal. It will never go vertical, right? And so you need to use the containers in order to get to those. And Maria and Anna’s video talks about that quite a bit. And maybe something to add is like, we generally have APIs to like place things in the correct axis, right?
But we don’t necessarily have APIs to make them behave the same. Because maybe I’m reading too much into the question, but to me, behave also means like showing the labels on tap and like having the like lensing when you’re scrubbing between, like, we don’t have APIs to kind of like dissect that and like put it on someone else’s tab bar.
So if you do want to get like all the bells and whistles of a native controller, your best bet is the native controller itself. There’s also a lot of complexity in like the compression logic for 100%. Yeah, that’s a great point. Yeah, yeah, yeah. The, that, that was one of the things that seemed obvious in retrospect, but surprised me at first.
The height of the bar, vertical bar on the edge can change so much. Yeah. Rotating the outer display showing a video PiP above the display internally moving to split view multitasking. There’s just so many ways that the height of that can change and you have to adapt to it.
Well, we’ve also never had like bars sitting together, right? Like even like you would never have a, I’ve seen probably apps that I can count on, like my one hand that have a bottom bar and a tab bar sitting on top of each other on a regular shipping iPhone, right? Versus like now everything’s pretty much on top of each other.
You can have like a top bar and a tab bar, like top and bottom. Like there’s so many permutations that like, even on a regular height, will just now start compressing because we’re not used to having them coexist like that. Yeah. And so if your app maybe hasn’t had to handle compression or overflow menus before, I would consider as part of the work to get ready for iPhone Duo that you can do right now.
How does it behave when items move into the overflow? Because making sure that they have representations that you have set priorities so that the system can preserve the things that are most important for the longest amount of time. That’s really good to tailor the experience. Yeah, yeah. And recognizing that for some larger companies that that may be a political debate whose button gets to gets to stay and who goes into the overflow. Whose tab gets to stay? Yeah, yeah. So and in the talk, Maria has a very good section that explains how to think about that. It’s almost like I spent six months of this year ordering buttons.
So you don’t have to. This is a short question. I don’t know who to throw it to. So I’m gonna throw it to all of you and see if someone can grab it. Does iPhone Duo have its own idiom? It is a phone. It’s a phone. Yeah, it is a phone. So it responds to a phone idiom. Yeah, yeah.
It does have its own unique combination of size classes on the inner display. Yeah. It’s regular, regular, which is the first time a phone has had that. Yeah. And I would say too that this, you know, this is a great time to stop making assumptions. Maybe if you were, if you had something that’s like iPad idiom. So I’m going to show the iPad UI versus phone idiom. So I’m never going to show the iPad UI.
So definitely start looking at size classes now and thinking about how to adapt to that. Yeah. And that comes a little bit back to the ergonomics of it, like the idiom is going to tell you a little bit about how people are carrying the device and what circumstances they’re using it in. It’s not so much about the size of the display.
Right, right. We got a widgets question. I’m not sure we’ve got the the right folks here to answer it, but I’m gonna start with you, Maria. Oh, didn’t I just tell you I order buttons? But we’re just gonna have buttons. Sure. Let’s see which widget families and how many widgets are supported on the lock screen of iPhone Duo, and is it different between the outside and inner screens?
I don’t know. I would expect that it’s different because we have the new extra large ones on the inner display. I do not believe that those can exist on the outer display. I have not tried. So correct me if I’m wrong. They’re six by four. I don’t think they could. Yeah, I don’t think they could. So I would assume there are some differences, but I don’t know about how many you can fit.
All right. Anyone a heavy user? I also don’t have a lot of widgets, so. I. Use it more because of StandBy though, because StandBy is a great feature on this device I use. But yeah, I the fact that you can go into StandBy when you’re not on a charger. Yeah, yeah.
Changes everything. Yeah. I, I said last night, I’m super excited about extra large widgets and it’s because of StandBy like my calendar will fit and I can see all the stuff I have going on during the day, which is maybe a sad testament that I need an extra large widget for that.
Let’s see, Maria, I’m going to throw this one your way. This will be the last one we do slow. And then we’re going to go into a speed round to take us out. But Maria, are there new APIs in iOS 27 specifically designed for foldable layouts. And I have a follow up.
Yes. My favorite API ArrangementViews, which we already talked about, but we’re going to talk about it again. ArrangementViews is a is a great kind of container that can help you achieve like a. Lot of these like two column layouts and also kind of swap them between the different displays and.
Like the different available space like as appropriate, which I think is really great. So you’re not having to like endlessly do like if statements and like switch between like HStack and ZStack and ZStack and like all the stacks and grids that we provide, we’ve adopted it internally. Like so much. Like I think almost every single app has an ArrangementView. So I think that would be like the one that I would recommend to developers to check out as anyone. And yeah, I think. What happens if I have this on a normal phone?
Will it just like not do anything? Will it do something? Great question. It does actually work on our other hardware as well. As long as like the conditions that you’ve kind of set up the ArrangementView are true on the device that it’s running on. So like if you still have space for two columns, it will render as two columns.
If you don’t, it will kind of move towards a single view, which is exactly what happens when you move between inner and outer display. Yeah. And Anna either has really great eyesight or anticipated the next question. Exactly that. Perfect. E Clausen thanks for your question. That Anna intuited.
Well, that was one of the things that I thought about because like we’re saying, you’re not just building for Duo. Yeah. For sure. And you want to make sure that any of iPhone Duo specific APIs that you’re adopting will also still behave well when your phone is run on a non foldable device. And maybe that’s kind of where they’re like, that’s where the questions of like, does it have its own idiom?
Or like, how can I like specifically check if it’s like this device, like a lot of the APIs and like layouts and like general behavior APIs, like compression, like do end up working on other devices. And I think they are helpful in other devices because like, who knows, like even for compression, like it’s not something like not a lot of people use. I think regular iPhones in landscape, right?
But like, as they start using this, like maybe that pattern changes and like more and more apps start supporting it. And then surprise, surprise, you have a little bit more compression to deal with. So I think they’re helpful and useful and they should not be kind of like good functionality should not be behind idioms and like all sorts of other tricks. Right. All right, let’s, let’s do a little bit of a speed round.
I accidentally hit the wrong button and cleared this question, but I’m going to ask it anyway if I can remember it. How can we tell the difference between portrait and landscape on the outer display? Well, the first question to ask is why do you need to know that? And then the second is like, I think if you need to do something special, I think size is something you could check.
On the outer display. The size classes are different in the two axes. Yeah. Do we have access to the angle that the Duo is currently folded at? Yeah we do. I don’t know what unit it’s in, honestly, off the top of my head, but with the hinge interaction you can get the angle.
I hope it’s a strongly typed angle, but I don’t know. But but then I my background is type theory, so I would think that for a web app would be any way to check if layout or device is an iPhone Duo. I think I can take that from last night. You can’t specifically check whether it’s a Duo. We wouldn’t ask you to do that, but there is standard web API for checking whether a device has a fold and is folded.
So. So look into that when the SDK is available. One more. What will be the best way to support the new device and APIs while also maintaining support for older iOS versions? Back to iOS 16, I think the answer I would give and that I give in workshops is it kind of depends on your app, but essentially you have to do an availability check and so make the stuff that is duo specific or iPhone 18 specific, have an iOS 27 availability check, and then other things can be outside of that check. You can tighten or loosen the scope of that depending on what you’re doing. Like some developers will sort of freeze dry their UI and make a new UI going forward, and then they can delete the old UI once it’s aged out.
Other developers need to be shipping features across all the device families. We get that. Then you maybe want to scope those conditions a little smaller. Yeah. For ArrangementViews specifically, if you’re using an existing layout, then, you know, maintain using that existing layout. And then perhaps when you know, ArrangementViews are available on those operating systems, switch to using that. Yep, great. And I’m going to take one more because I like the question, does iPhone Duo support multi-window? It does. We call it split view multitasking. And and check out Chris and Alex’s talk on on adapting to scenes on iPhone Duo. For more information on that.
But that brings us to the end of our group lab for today. So a huge thank you to Anna, Louka, Ryan and Maria for joining me. Great chatting with you all. And to all of you watching around the world. Thanks for tuning in. Your enthusiasm for iPhone Duo has us all even more excited to get this new iPhone in people’s hands soon.
If you have more questions or we didn’t get to yours. Next week, we’re hosting several Q&A sessions on the Apple Developer forums covering photos and cameras, SwiftUI and UIKit for iPhone Duo, and you can register for those at developer.apple.com. And as I said, we’ll be hosting workshops around the world. Details on those are coming soon. I hope to see you there. Bye.