Video hosted by Apple at devstreaming-cdn.apple.com

Configure player

Close

WWDC Index does not host video files

If you have access to video files, you can configure a URL pattern to be used in a video player.

URL pattern

preview

Use any of these variables in your URL pattern, the pattern is stored in your browsers' local storage.

$id
ID of session: meet-with-apple-288
$eventId
ID of event: meet-with-apple
$eventContentId
ID of session without event part: 288
$eventShortId
Shortened ID of event: meet-with-apple
$year
Year of session: 2026
$extension
Extension of original filename: mp4
$filenameAlmostEvery
Filename from "(Almost) Every..." gist: ...

Meet with Apple • Session 288

iPhone Duo Group Lab

2026-10-15 • iOS • 1:02:24

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.

Open in Apple Developer site

Transcript

Hello. Welcome to today’s iPhone Duo Group Lab. I’m Doug Lemoine, I’m a design evangelist on Apple’s Worldwide Developer Relations team. In the next hour, we’re taking your questions about updating your apps for iPhone Duo. If you’re watching on the Apple Developer site, you can ask your questions in the panel on your right. If you’re watching on YouTube and would like to ask questions or vote for your favorites, please hit the link in the description below the video.

Over the past few weeks, we’ve been hosting workshops around the world to help developers get their apps ready for iPhone Duo. We’ve seen especially great progress as people have been using updated SDKs in Xcode 27.1 and the Device Hub that supports poses and orientations on iPhone Duo. So it’s exciting to see everyone’s work so far. We’ve been answering questions throughout the fall, and we’re excited to get into yours this morning.

Okay, let’s get into it. So first, I think we should introduce ourselves. I introduced myself, I’m a design evangelist. Russell, would you like to introduce yourself? I’m Russell, I’m an engineer who worked on the project this year. I’m super excited to be here and see all the stuff y’all are already making.

Hi everyone. I’m Henry, I’m a software engineer on the app team for News, Stocks, and Weather apps, and I help drive iPhone Duo adoption for those apps. And I’m happy to be here to share my experience and answer questions. Hi, I’m Grant. I’m a human interface designer. I work on a number of apps for iPhone Duo, including things like Messages, Files, Preview, Measure, and a number of others as well. Hi, I’m Kurt, I’m a technology evangelist. I’ve been involved with producing the videos for iPhone Duo and lots of our workshops and, of course, Group Labs like this one. So happy to be in this chair instead of that one today.

Hi, I’m Mohammed, I’m a UI frameworks engineer working on UIKit and SwiftUI, and I was one of the folks working on bringing the platform up to speed for the Duo. Awesome. Yeah. You all come from a variety of roles around Apple, and it’s super exciting just to see how many people pull together to make this happen.

So before I jump into questions, I do want to just ask a big picture question, which is what’s one thing that you’d want all developers to adopt, to make the best experience for their app on iPhone. So I’d love to hear all of your answers. Maybe Mohammed, I’ll start on your side.

Sure. I think one thing that kind of became very clear to us is that really the best way to build an app for the Duo is to build a good app for iPhone and iPad, follow the best practices that we’ve been recommending for years when it comes to frameworks. Make sure that your app handles arbitrary sizes, that it properly respects things like size classes.

Just build a resizable app that follows platform conventions, pay special attention to things like layout margins, safe area insets. Make sure that you use the conveniences that you get from the framework for those sorts of things. The Duo is going to put your app in some interesting configurations that you haven’t seen before, especially when it comes to those areas, and it’ll be a lot easier and your app will feel much more consistent with the rest of the platform if you use the conveniences that we provide for you.

Yeah, I want to reinforce one of those points about safe areas. We see lots of people in the workshops who’ve built apps where they respect top and bottom safe areas, but they don’t think about safe areas on the sides because maybe they’ve been disabling landscape on the phone.

And so be cognizant that you might have code that’s not looking at safe areas on the sides, and you need to respect that. And maybe one of the most interesting things to pay attention to there is the asymmetry on this device. This is a, I believe, the first time that apps will be given asymmetric left and right safe area insets as well as Layout margins. That’s a brand new world for iOS apps. And we’ve made sure that those things work as expected from the framework side. And we’ve provided the conveniences to make that easy for you to adopt in your apps using APIs that you’ve been using for years.

Yeah. I’ll talk about the vertical bars. So we moved the controls that traditionally were along the top and the bottom of the screen to live on the right side of the screen. And that’s important for iPhone Duo, because it saves the vertical space of the screen to show the content.

And because of the shape of iPhone Duo, in order to have enough room to show all of the content that you want from your app, you’re going to need to free up some of that room. And the best way to do that is to follow those platform conventions and take those controls that were in the navigation bar, in the toolbar and have them show up on the side. So again, like everything else, that will happen automatically when you’re using the system framework components.

But there’s still a lot of things where if you do have custom components or if you’re using custom views, or if you have different types of layouts, it might still be worth looking at, like moving things out of the way or reducing the amount of even custom vertical bars that you have to save that vertical space for the content, because I think that’ll help the experience of apps on iPhone Duo.

Yeah. The nice thing about using the standard components and ensuring that your actions and navigation show up on the trailing edge when you’re in closed and landscape, they also will show up on the leading edge if you’re in Split View multitasking, right? So they’ll flip over to the left side or the leading side. So yeah, it’s another reason or another benefit of the standard controls.

Henry, what about you? Yeah. So adopting standard system components, I feel is very important and a good starting point. So for example, in News we have this cooking view and we used to have this custom ingredient sidebar. And later on we migrate to the NavigationSplitView. And then suddenly in the iPhone Duo, when you open a post, we get this nice 50/50 layout for it and you just get it for free after we do the migration. Also, the horizontal safe area insets are also important in News. We see a lot of issues because of that. Before, we were only honoring the vertical-edge safe area. And now we start seeing issue like a text overlapping with the vertical bars. And then we started fixing those things. And once we get those out of hand, a lot of apps look pretty good on the iPhone Duo.

Awesome. I’ll build on what everybody else said. Reinforce using the standard framework components like as much as you can, because then you’ll get all of this behavior automatically and for free. And we’ve tried to provide a kind of a sliding scale. So the more customization you need, you can reach for it if you need, but adopting as much as you can. And we’ve added more and more things to try to make them as capable and more customizable so that you can use them. So try using the main containers like NavigationSplitView, NavigationStack, TabView.

And then we do have like APIs that you can drop down to for placing custom controls in a custom vertical bar if you have to do that. I really like that idea of a progression. And I think that the team did a great job on providing APIs like the standard components work. And then you can drop down to bar regions or corner regions if you need to do something custom.

And that applies to the folding the device also because the standard components adapt, but you can drop down to an ArrangementView, which is a little more control over what happens. Yeah. Or you can drop down to the hinge APIs if you really need to get there. And I guess I skipped reserved region on my way down the stack. Yeah.

But like, there are these, you can use the standard stuff. If you have to specialize, you can. I just think that’s really fun to have those tools available. But it’s a great job by the framework team. We use all of these things in all of our own apps and we make them better every year. As all of our own apps change and improve. And so if they didn’t work for you before, like give them a try again. Yeah.

And if they still don’t work, you can file. Yeah. Let us know. Yeah. Okay. Should we get to questions from the audience? All right. I’ll start at the top. We have an app that’s only for iPhone. We use NavigationStack and TabView, but for the iPhone Duo, NavigationSplitView seems better.

So Mohammed and Russell, I think this might be in your realm. However, using both tab and split view seems wrong. Is it or is it recommended to use a sidebar? Any advice? There’s so much. Oh, there’s a lot. I can take a first pass. Sure you can. I can tag you in. It’s not wrong.

You need to make the right decisions based on what you think provides the best user experience for your app. If you take a look at some of the system apps, you’ll see that different choices were made in different apps. For example, some of the media apps like Music, TV, Podcasts, whereas they have split views on iPad, they have a tab bar, a vertical tab bar in the open state on the Duo.

That all comes through the modern TabView API that we have that adapts automatically to the different devices, different modes that are supported. Whereas other apps like Mail, for example, has a split view that carries over across the Duo. And the decision point there was really based on what the teams, the design teams, engineering teams felt, what provided the most optimal experience for their users.

So these components exist. They can be combined in different ways. And that’s where you can express your creativity. And again, as Russell said, like if you hit situations where certain combinations aren’t working, let us know. Yeah. And I think from a design perspective, like TabViews, like when should you use like a tab, essentially a tab bar versus like a sidebar, right? And both of those can come from a TabView.

But I think on iPhone Duo, it depends on what content you have in your main area, right? If you’ve got a lot of different sections of your app, you’ve got like a very deep hierarchy, or especially something like Mail or Notes where you’ve got like almost like a content list that can be a great place to use a split view and to show two columns, right?

But if you’re something where it’s more about the content of your app and the tabs that you have on iPhone are really more about just major sections of the app, and you have really immersive or dynamic content, like those media apps Mohammed was talking about. Those are great examples of a place where a tab bar, even on iPhone Duo can be great because you let people focus more on the content and less on like a sidebar.

And oh yeah. I would say most of our own apps, it follows what the iPhone did. So it was a tab-based app on a standard phone. It’s a tab-based app on the Duo with a vertical tab bar. And then the exception is like some apps. Should I bring up Phone?

That I think there are some cases where you have a TabView app where it’s you. It’s not as clear. I think if you’re a split view app, it’s obvious that like, that’s great and you have a split view. And if you’re a TabView app, okay, cool. But then maybe my app, I still want to split for some reason, because my content doesn’t flow and fill the screen in the way that like our media apps do.

And I think Phone is an interesting example of that where it benefits from a split on the Duo on the inner screen specifically. And that is one place where we did put a split view inside of a TabView and it’s not the most common pattern, but it’s not that it’s not allowed.

I think the important thing is like one important principle that we had in mind throughout the development here is to maintain continuity between the inner and outer display. So as long as it makes sense for your UI and your app isn’t going through a very surprising and major transformation where there is no relationship between what folks are seeing on the Duo when it’s closed versus when it’s open, then you have a lot of freedom with what you can do, right?

Can we talk about the choices the developer makes in designing their fully open iPhone Duo experience versus like iPad and landscape? Because I think it’s interesting that the media apps, TV, just for example, uses a tab bar in fully open iPhone Duo. But there’s a sidebar on iPad. Grant, what’s the reasoning there? Yes. I think like from the baseline, like iPad apps are resizable. Right. And so at some point, like you can have an iPad app that’s exactly the same size as an app on the iPhone Duo. Right. And so the question is, what is the difference?

And I think there’s two main differences that we get into with it. One is the physical size and shape of the device, right? And that’s what drives things like having the controls laid out vertically along the right edge, right? And so from that perspective, when the controls are laid out in that way, it can push the device more towards focusing on content and the rest of the space, because you have this special space that’s dedicated for controls, but there’s not really a hard and fast rule, right? Like on the iPad, you can also have a TabView-based app. And I think, for example, TV has a TabView-based app on the iPad.

And that can be a great thing to have on the iPad as well, when your app is about that immersive content. And so a lot of this is really about how relatively important are the sort of hierarchical elements of your app versus the content elements? And that’s something that only you can decide when you’re thinking about your app and what your app needs.

Yeah, I think Health is an interesting example here, right? Because it surfaces a lot of the deeper hierarchy in the sidebar when it’s open in landscape where it’s using the. And I think that’s a great example where it’s like, there’s so many different categories in Health and you’re probably looking for a very specific one, right?

Where surfacing that at the top level can be really valuable in a way where other types of experiences are more browsing experiences. And so it’s less important to have a really long list of categories or sections in your sidebar, because you can get to that right from the content, or maybe you’re jumping back into the last TV show you watched. You don’t have to browse at all.

Exactly. I think there’s a interesting connection between what Mohammed was saying, what Grant is saying. Grant is getting at like, what’s the navigation of your app? How are you moving through the content that you’re providing to the people using your app. And then Mohammed’s talking about the adaptation as you go from closed to open. And having this sort of consistency that people have in mind as they use your app helps them understand what’s going on as they move between open and closed. And so I think thinking about that data flow and that navigation and moving around like that really needs to come before the visual design.

So don’t get tempted to, oh, I got to make it pretty on this display. Think about how people are going to use it. Yeah. There’s not one right answer. Like in, I think in most cases, we decided it was better if you have a tab bar on the right and you open it, the tab bar should still be on the right.

But Health was another example of an exception where like for the reasons like Grant was saying that you want to be able to see more of your data and like see more of the categories that was more valuable. And we decided that breaking the continuity there was worth it. And that’s a specific option on TabView. It’s the .sidebarAdaptable style. It’s a way to like force that sidebar preference on duo specifically.

This is a rich topic, and I want to ask Henry, what about like Weather is interesting to me because I think that there wasn’t a landscape version of it before iPhone Duo. And I wonder how you all settled on it. Yeah. So for Weather, before Duo, we didn’t have landscape support and for iPhone Duo, we actually had a landscape support, which there’s a new two-column layout.

And the location header view is on the leading side and the location components on the trailing side. So this is a new layout we specifically built for iPhone Duo and resizability part. That’s great. Yeah. So this was, I guess, an opportunity to use that space. And you settled on the design that you thought was right for it. Okay. All right. So we’re 17 minutes in and got one question.

It’s a good question. Yeah. It was a great, great question. Okay. Let’s move on to another one. So I’ll take the next most popular one, which is how to detect when a widget is displayed in StandBy mode. Is there a way to do this? This is an API question I think for you all. Is this an answerable WidgetKit question?

Don’t know. It certainly is. If we had someone from widget. Yeah, I feel we’re lacking widget experts on this panel. I’m actually not sure. I think there is an API to tell because I think the rendering mode is different, but otherwise it’s the same as your home screen. So that’s. I think the thing to look at, the place that API would be, would be on EnvironmentValues. Okay. There would be a, there would be EnvironmentValues that widgets can read to understand the layout constraints.

And I don’t know, particularly if there is one for that case. But as an example, Live Activities can detect if they’re in a constrained horizontal environment, which is useful if you’re doing a Live Activity on the Duo, because instead of coming out to the side, it’s coming out at the bottom of the Dynamic Island.

And so it’s a little bit narrower, but look at EnvironmentValues for that. Digging deep in my brain, I’m pretty sure there is something because StandBy has been around for a while, and it has a more like immersive layout, like on the background. Yeah. On your home screen, the widgets are like in boxes because they have to sit with other stuff. But in StandBy, like we make the whole background black.

And so like we want you to fill the space more. So there’s definitely something. Yeah, yeah. One other thing to think about with widgets also is the extra large widget size. That’s another thing that can be great on the iPhone Duo a tangential thing here. But yeah, we’re taking a look at as well. Yeah, that’s an extra large in portrait. Is that right? Yeah. Awesome. Okay. Next.

I disabled the vertical bar in the root screen of my app. But while the app is launching, the launch screen shows the status bar vertically. Is there a new Info.plist config to change the bar axis on the launch screen? No. I want to go with. Probably not, but that’s a good piece of feedback to send us. Okay. Yeah.

Wow. That feedback, the look of oh, we should have done that. Curious what Calculator’s launch screen looks like? Yeah, yeah, yeah. I was trying to think of an app that would have encountered this. We have apps like that. Yeah. And again, I think this gets to the point is like users will expect a vertical bar and most of the controls to live along the right side in most of the apps they use. Right? Yeah. And so that is something that like, like you should only be turning that off if there is a specific reason to turn that off. Right? Right.

But there are, I think, a number of specific reasons that it might make sense to turn it off. Like Calculator is a great example where there aren’t a lot of controls that need to live over there, but you can use that area for like putting the calculator buttons right up to the edge, right?

Where also some like immersive type things like many games, I think will find that like, it’s unlikely that the sort of like side controls or even standard navigation bar and toolbar on an iPhone makes a lot of sense. And so that might be a place where you turn that off as well. So it really depends on your app.

All right. Moving on. My app has a custom side hamburger menu on the left with several levels. Menus have sublevels which are expandable. Would you recommend to move it to the right side for duo or leave it on the left? Grant, I’m looking at you because there’s a design angle for this one. I can’t migrate it to the tab bar navigation because of how our product is designed.

Yes, I think that, overall, we do recommend using the standard navigation components, things like navigation controllers, which can, at the top level of navigation controller, have a number of different sections of an app. If that doesn’t fit in, for example, a fixed number of tabs and a tab in a tab bar or a TabView. Right. So we do recommend that.

But getting into the specific question, I think it’s worth looking at what the system components here are. Right. So if you look at, for example, the sidebar arrangement of a TabView, when the device is open and you opened it up and you’re in that open state, the tab bar shows up in the sidebar on the left.

Right. Yeah. And so for that principle of continuity, when the device is open and closed, I don’t think it would make sense to have a tab bar showing up in the sidebar on the left, or a split view showing the top level on the left. And then when you close it, having that start showing up on the right. Right. I think users will expect that continuity. And so you probably keep it showing up on the left on the outer display as well. Yeah.

I’m wondering if they’re also asking where the actual button should go versus where, like the, whether the view should slide to the right or left when the hamburger menu comes in. Yeah, that’s a great question as well. And I think that one for that perspective, like when we do have those kind of buttons, I think that’s a question that you can look at in your app, what makes sense. But I think a lot of users will expect from using things like tab bar or NavigationStack, for example, that the back button that they use to go up one level in the hierarchy does live in that bar on the right.

And so people will expect that that will be the place that in every single app on the iPhone Duo, when you press the back button to go up a level, you do that with the button, right, right in the vertical bar underneath the status bar. And I think people expect that regardless of how you’re going up a level in the hierarchy. Yeah. Yeah.

And if an app is doing its own custom overflow menu and is using a vertical bar. Because of all the different configurations, the device can be in, the vertical bar can get its own overflow menu. And so I’d be really careful of having two overflow menus effectively with different hierarchies in them.

And so we talked about it in the “Raise the bar” video about how to put your own items inside the system overflow item. And so one thing to think about is moving your context menus that are currently in your own hamburger menu into the system overflow menu, so that hierarchy lives with the other things that overflow.

Yeah, yeah. I think we’ve seen that the kernel of this question, we’ve seen a lot in the workshops, which is an app has an element that is fixed in a location. I think that’s common on iPhones now, which is the top left or top center or something. And there are questions there’s some trepidation about like moving that anywhere, right?

Just because it’s such a common location for those things to have been, but I just want to double down or plus one on something that Grant mentioned, which is controls are migrating, navigation is migrating to the vertical axis on the edge. And people are going to expect app navigation to be there.

And so just from like a basic approach, I would first consider moving it. And then if that somehow is breaking things, then maybe you consider alternatives. But I think that moving it is ultimately the right thing. Another reason to move it is that standard navigation bars scroll away on iPhone Duo by default to, again, give back more vertical space.

So if your navigational element, if you have any navigational elements in the navigation bar and it’s a standard navigation bar, then that will, they’ll disappear when you scroll. And there’s a benefit to the persistence of them, even if you’re like halfway down a view. That’s a great point. Yeah.

All right. So sidebar question. Since the sidebar with its items, always stay on the right side of the display. I think maybe this is the control bar. Yeah. Yeah. Toolbars and tab bars. Yeah. What shall I consider for right-to-left language apps specifically for NavigationSplitView-like views that depend on leading and trailing views. I think this is a question of how does iPhone Duo account for right-to-left usage.

I love this question, but go yeah. Maybe we can. We can both provide different perspectives on it. It’s, again, this is another, not to keep belaboring the point on using the system components here, but you’ll find that, you know, the behavior of, of the vertical bar on the Duo isn’t necessarily as like immediately obvious as other bars. We don’t just immediately flip it to the left side in right-to-left languages. And that’s based on a number of factors. Part of it is the harmony with the status bar and some aspects of the hardware, like the shape of the display, the outer display’s camera.

So again, you adopt the APIs that either give you those signals or that handle that for you. So if you’re using the system vertical bar or some of the kind of lower level APIs that provide those regions for you, like SwiftUI safeAreaBar, you’ll be set in both left-to-right and right-to-left languages. And if you’re doing your own custom vertical bar, you’re trying to decide which side to put your safeAreaBar on.

We have an environment key for that. And it’s not necessarily what you might expect, it stays anchored to the hardware for like that continuity reason. So even though a lot of other UI elements might flip in right-to-left, like split views and navigation, generally, because that bar is hardware-anchored on the front screen, we want it to stay on the right on the inner screen. So you definitely want to like check all these things to flip the right things and not other things. Yeah.

But again, note that in some cases, like for example, in multitasking, if you have a split view and your app is on the left side of that split view, the toolbars and tab bars and stuff will move to the left side of the display as well. Right. Regardless of right-to-left languages as well. So. Right. And so that’s why it’s really useful to use those system ways to either place controls in there or to read out those regions, because the rules can be very complicated to try and replicate. Exactly. Yeah. I have a follow-up question for y’all.

So, and we have Mail showing on the screen behind us. Yes. If I’m using my iPhone Duo in a right-to-left language, the toolbar controls will be on the right edge. Right. But what order do the components of the split view go in on the inner display when open? Is the message list on the iOS leading edge? Is it on the right? And then the detail is on the left. Or do those.

Okay, the vertical bar is always on the right and the message list is always on the leading edge, which means it would also be on the right. On the right. And then the message, it’s like flipped from here. So the message will be on the left. And then another. Critically, this doesn’t change what controls are in the vertical bar. So the controls in the vertical bar still always come from the content column of the split view. The message. So now the sidebar, the message list is in between the controls and the message.

But this is another reason to use our components because we handle all of that for you. Yeah. All of this would be great if we had a device, we could put it into Arabic or something. And just,, just show it. But yeah, you’ll see a version of this background. So you can change it. Flip it over. Because this question keeps coming up.

It does. It’s a good question. It’s a great question. Good question. Okay. So we have another question. Could we see the standard camera app interface to get an idea of how controls are placed, both with the screen open and closed? We can’t show it to you in this moment.

And coming soon. I don’t know if there’s anything more to say on, can they see the Camera app? I don’t know if you can open a like the capture view controller inside of the simulator, but that might be something to try. You cannot. All right. Never mind. Idea, though. Yeah. Coming soon, coming soon. Preorders start tomorrow. And devices are available next Friday. Eight days.

All right. When an app moves between different screens, how do you keep your collection view scrolled to the expected location? This question has come up, I think, in every Group Lab in some form. Henry was actually talking about this for News before we came out. Yeah. This is a detail I really like about the News app as well.

It just deliver the reading experience seamlessly across different poses. So for example, if you scroll through the news feed and let’s say you scroll to the technology channel section and you decide to open iPhone Duo to see more articles in the section, you will see the same section is persisted between the closed pose and open pose.

And the same continuity applies to the article view as well. So for example, you are reading an article view and in the middle you try to open iPhone Duo to get a bigger screen so you can read more comfortably. And the text position is also persisted between closed and open poses.

So for News Feed, the foundation is actually a UICollectionView. And there’s already some sort of customization optimization for UICollectionView between transition poses. So what you get is actually for free when you use UICollectionView, UICollectionView will store your visible cell index path. And once you go to the iPhone Duo open pose, the same index path will be showing on the same screen. So you pretty much get it for free via adopting the UICollectionView.

And for a news article, for example, in the News app, we actually have to create something called a text anchor. Before the transition, we store the text anchor. And after you go to, for example, open pose, we’ll restore this text anchor by scrolling to the text position. So that’s how we keep the the reading experience consistent between open and closed poses.

I think one thing to add on that is that the transition between the outer and inner display is not as large of a transition as it actually seems for your app. It should be largely no different than going between compact and regular size class on an iPad. It’s still the same instance of your app. It’s the same instance of your scene. Even all your UI is there. It’s adapting to the larger size, essentially. So any sort of state that you’re storing for this, any, you know, your instance of your UICollectionView, whatever it may be, it’s all the same.

So it’s like the same as you could test this by resizing your app on iPad and making sure that like the way the ScrollView responds to resizing, if you scroll to the middle article, like makes sense. And like critically, you can’t just keep the same Y offset because if you store the Y offset, that is going to change drastically as like your content changes. Your semantic position.

Yeah. And so it sounds like you had to come up with one for news articles because it’s like your own custom text rendering is, I think what you were telling me earlier, right? Yeah. That’s right. Okay. And for collection view, does it do it automatically with the index path? I didn’t know that. We have to do a little something to optimize how we restore, but it’s actually automatically happens.

So you can see the similar thing in TV app as well. Wow. Okay. That’s cool. So there is a part two in this question. Which is maybe speaking to what you were asking. Russell. And so maybe it was answered, but I’ll ask it anyway because I’m not technical, and this seems related.

when I scroll to grid item 100 on the outer display, then unfold item 225 is shown due to more cells fitting in the large width of the inner screen. Is there an API to preserve visible items? So we’re talking about collection view here, so I’m not sure if that clarifies things. Or did they specifically say collection view because it could be a SwiftUI grid also. It says collection view, but not in title caps.

Yeah. So sounds like if it’s a UICollectionView, so like a SwiftUI List or a UICollectionView list, we’ll keep track of whatever the index path is in the. I’m guessing that’s like the top left. And then keep that stationary or keep that cell visible as the collection view width changes.

And if it’s SwiftUI lazy layout, I don’t know if we do that. Yeah, it sounds like a feedback with a sample project might be in order because it’s supposed to maintain position. And if it’s not and you have a small project that shows it, we’d love to see that. Yeah, yeah.

Great. Let’s see. Since the sidebar with its items always stays on the right. Oh, sorry. We answered that one. Moving on. Let’s see. Okay. I’ll go ahead and address this. Since it’s at the top of the list and sadly unanswerable. But since Apple Pencil isn’t supported at launch, is there a rough timeline for when it will come to iPhone Duo? We’re building a sketching app and want to plan for it. Totally understandable question. Love that you’re thinking about it. But we can’t talk about the future, sadly. future timelines or milestones here today.

How do you handle orientation on the inner display? Given that standard orientation locks are ignored on the inner display falling back to a regular/regular environment? How should developers switch from portrait locks to width-based decisions? Sorry I landed on you there. I’m not sure if any others. I think Mohammed has opinions. I can say something about that. I think that this device really lends itself well to being used in a lot of different orientations.

And I think in a lot of ways, while there still might be valid reasons to think about things in terms of orientation for most apps, you really want to move your mindset to thinking in terms of size. And that scales really well across all devices, from everything from the smallest iPhone to a Mac.

If you’re writing an app in SwiftUI or taking advantage of Mac Catalyst. So really, start thinking about your app’s layout in those terms. Think about it in terms of size classes, in terms of all the various traits that you’re getting from or EnvironmentValues that you’re getting from the frameworks.

Think about it in terms of the experience that you’re trying to provide to your users for a given size or set of capabilities, rather than a portrait or landscape aspect ratio. Because even with this device, a portrait aspect ratio on the outer display, for example, is actually wider than most other iPhones and shorter in the vertical height than most other ones.

So again, watch for those signals and think about, rather than thinking of orientation as a state or mode that your app is in, think about as best as you can each axis of your layout independently. And you know the size and space that you have available to you.

Two other things I think might be worth mentioning here. One is on the inner display. Specifically, when you rotate from a landscape pose to a portrait pose, the controls that were placed along the right edge of the display moved back to being placed at the top and the bottom, right? And so because they do that, that’s something to think about in terms of like your overall app’s layout is going to be more like a traditional iPhone layout that you might have had before in your app.

The other thing to think about though, when you’re going on the inner display between the poses is how it works with ArrangementViews. ArrangementViews are a great way to have like different parts of your app either laid out side by side or above and below each other, or stacked on top of each other. And then also when it’s both folded and then also when it is flat as well, right?

And so one of the things to think about there is that those ArrangementViews, depending on your configuration, this is all very configurable. So you can set up exactly how you want it. But they have the opportunity to be able to place different content stacked vertically when it’s in portrait and stacked horizontally when it’s in landscape. And so that can be a great opportunity to create a semantic layout using the ArrangementViews. That covers a lot of those cases automatically.

Do we have examples Do we have examples in our apps of good uses of ArrangementViews? Yeah, yeah. The video player in the TV app is a great example. It, I believe, makes use of multiple ArrangementViews with different arrangements depending on the orientation. So for example, in more compact layouts like on the outer display, it looks no different than it does on any iPhone you might be using today. And the ArrangementView giving that layout is accounting for that.

that size class, the lack of a fold on the display there, and is placing itself in that layout. On the inner display, you get two different adaptations depending on whether you’re holding the device in landscape versus portrait. So when you’re in landscape and fold it into more of a book-style layout, the video fills the entire display, but the controls shift to one side so you can more easily interact with them without having to place your finger in the middle of the screen. When you hold it in a folded portrait orientation, more like a laptop, the controls move to the bottom so they’re closer to you and the video moves up to the top.

And again, as Grant said, that’s something that is all from using a combination of ArrangementViews with a couple of different configurations. And you can do things like choose the axis on your ArrangementView. You can nest ArrangementViews for some interesting combinations. So there’s a lot to play with there. But Now Playing UIs in the Music app and inside of the Podcasts app are also examples of where we used ArrangementView. Right?

Those might be ArrangementViews, or they might be the slightly lower-level API, reserved region. So if you’re working with a more custom layout where you’re already doing a lot of manual work, we also have an API that allows you to get some information about things like the location of the fold or other kind of interesting regions on the display.

That kind of speaks to Kurt’s earlier point about like tiered APIs. And this one was a premier example of that, where we built the lower-level building blocks and then built our functionality on top. And you can slot in your adoption where it makes the most sense for you. Yeah. And since ArrangementViews came up, I want to shout out one of our community contributors, part of our community program. Natalie Panfilova posted a great blog post on using ArrangementView this morning.

And so she did a really nice job of covering the pieces and how they work together with some beautiful lunar state examples. Reminded me a little bit of the Weather app when I was looking at her examples. Well, to tie it back to the Weather app, I want to throw it to you, Henry, for a second that we. But first I want to say about ArrangementViews. We. When we looked at all the designs for Now Playing and a bunch of different designs and supporting like landscape to the original question that I think was asked that started this whole conversation.

We were trying to think of what are a bunch of tools that we can add that helps you adapt your app to think in terms, just in terms of size, so that you can support landscape more easily. And ArrangementView was one of those things. And then we created this spectrum of things so that we could adapt all of our apps. And Weather is an example of an app that didn’t support landscape before. And now that’s right. Which I think we said earlier, and I don’t it does not use ArrangementView. It does not use ArrangementView.

So the way we have is we use this two-column layout in the closed pose, and in the leading side, location. And the trailing side is a location component view. So once you’re in the open pose, it actually goes to the sidebar and the location component layout. So we don’t really have to use an ArrangementView for that purpose. What about,, landscape on the cover screen?

Yeah, that’s a two-column layout. Yeah, yeah. Yeah. If there’s an ArrangementView we can use, there’ll be probably a good use for that in closed pose as well. Yeah. But it’s a place where like Weather didn’t historically support this. And we looked at iPad and phone and well, how can we adapt this app for landscape because we want you to be able to hold the device in any way. And we did find a way. And so like, you can look at all of our apps and take inspiration for how did we adapt apps that previously didn’t support landscape, but now do.

Yeah. This is a rich area because it’s we’re talking about ArrangementView. We’re talking about laying out content on all the different poses and orientations. ArrangementView, reserved regions, scrolling. There’s all these things to account for. Grant. I wonder if you can talk or share information your experience with deciding whether to look for those reserved regions when you’re in the open pose, to move content out of the way versus just let it let it ride where it is.

Yeah, this is a really rich area to, I think, to think about with iPhone Duo. I think there’s two main rules that we take a look at one of them and this, I think this is something that we talked about in the earlier one of these group sessions, but I think is interesting. One is the axis of scrolling and the axis of motion of your content relative to the axis of the device hinge.

And so a great example of this is like, for example, in Messages, we have message bubbles, right, that are on the left and the right, anchored to the conversation. But the way that the message bubble scrolls is they scroll up and down, right? And so when you’re in a situation where the device is posed like a book, what we want there is for those message bubbles to not be on top of the hinge area because if they were, even when you scroll, they’re still on top of the hinge area because their axis of scrolling is the same direction that the hinge is moving in, right? And so what we did there was we had them shift out of the way in order to make sure that they never cover up the hinge.

And so you can always read those messages, right? A different example of this is the Preview app. So in the Preview app and in Quick Look, when you open a PDF when it’s flat, you have vertical scrolling as you’ve had on any kind of iPhone or iPad in the past, right?

But when you fold it into a layout like a book, we switch to horizontal scrolling with a two page layout, because then the scrolling is the opposite axis of the way that the hinge is displayed. And what that enables is that if something is underneath the hinge, you can keep scrolling and move it out of the way, or you can have the reverse of that, for example, in Safari. So in Safari, when I’m holding the device like a pose, almost like a laptop or on a surface.

In that case, the content scrolls across perpendicular to the axis of the hinge, right? And so in that case, you don’t actually need to move any content out of the way. Or you’ll see this in like Mail or any other list. You don’t really need to move content out of the way, because the user has the opportunity to move that content out of the way, and it’ll happen naturally as they scroll. Yeah. So that’s a good thing and important thing to think about when you’re coming up with your layouts for all the different poses.

But one other thing I think to think about is like this idea of avoiding too much motion. Yeah. So this is a important one as well. Like we do think that it’s really valuable to move controls, especially fixed placement controls that don’t scroll out of the way of the hinge.

But we also don’t want that to involve like a lot of like things sliding around and feeling like a completely different layout. Yeah. We want it to feel like the same app layout when it’s, when you’re in a sort of a pose like this or a flat pose or you’re in a pose where you’re holding it like a book, as it does when the device is placed flat as well.

And so it’s about shifting it, the minimal amount to take those controls out of that reserved region rather than about radically reflowing everything or making it feel like a totally unique layout in those cases. Yeah. So it’s really all about like the minimal shift you can do to make sure those controls are still accessible and still easy to interact with.

Yeah, I think it’s, I mean, it’s interesting to me that like Music and Podcasts and TV, they don’t, for the horizontal carousels, they don’t bump those individual items out of the way. They just let them go through the fold because even like a small amount of motion, I think would feel potentially a little. Yeah. And also when they are those horizontal carousels like that, if something is right over the fold and you want to get out of the way, you can scroll it out of the way, right?

Yeah. A good counterpoint to that is the App Store, where on the Today view of the App Store, it does shift over slightly in the grid layout into moving those two columns so that they’re not over the fold. Yeah. And that’s a case where you’re not scrolling horizontally. It’s a pure vertical layout. And so you want to avoid that horizontal fold in the middle.

Yeah. so that like something is not stuck over there. And then regardless of how much you scroll vertically, the fold is not going to move, right? Yeah. That’s a lot like the Messages bubbles. Exactly. Yeah. They have to get out of the way because the scrolling direction is aligned with the axis of the fold. So that’s a good like design thing to think about as you’re looking at that.

All right. Did we explore this one enough? We can talk more. Okay. Let’s see. All right. For independent developers or small teams, what would be the best way to identify genuinely valuable use cases for a new form factor like iPhone Duo rather than adding features just to use the extra screen space?

I think this is yeah, this is generally updating your app for iPhone Duo. Like what’s the best way to do it? We talk about like, don’t just stretch your UI for the internal display. Are there other kind of bits of guidance that you all got from updating? One thing I would say is that like for an independent developer, when you’re trying to work, like with a smaller team. Yeah. Using a lot of the standard components can help here because it can take your effort away from like updating the position of controls and updating like trying to recreate system elements.

It can focus like your effort onto what it is that makes your app unique and what makes your app really great. Yeah, I think there was a bit of a sort of what’s the business strategy in this question? And we can’t give a… you need to know your business. We can’t totally know that.

But I think this is an opportunity. Every time there’s a new device, there’s an opportunity for the nimble indie developers to get apps that shine on the new platform first, because there are fewer obstacles in the way of shipping. Not that management is the obstacle, but that you have to convince fewer people, like it’s your app, it’s your team’s app, and you can push forward and be there on day one with something that looks right on the device. And that’s a huge leg up versus more entrenched apps. Yeah. I would also say that prioritize having your app be ready for the device first before looking at the nice-to-haves, the interesting design flourishes that you might add.

Not to say that you shouldn’t do those. We absolutely love those when we see them in apps and try to take advantage of some of the accelerators that we have, like we’ve… Take a look at some of the videos we have about updating your app for iPhone Duo.

Take advantage of the agentic coding skills for the UI frameworks that we provided to help you clean out some of the common pitfalls that might make your app behave less in a less than ideal way on the device, and take your time to think about a great experience after that. Take some inspiration from some of the design videos and, see where your creativity strikes. I think I’m sensing this question might be coming from someone who only has an iPhone app but hasn’t brought that app to iPad before.

And so I think there’s some like general guidance there that is the same as what we’ve been giving for people bringing an app to iPad for the first time for years, which is like your app probably has more than one screen’s worth of stuff in it, and now you have room to display more of it all at once and use some of the tools that we have. We provided like NavigationSplitView multi-column and like new things like ArrangementViews this year to display more of that information that users might have to like scroll or like tap around to see.

And now they can see all of it like at the same time. And that has a lot of utility. I want to add a little about this as well. So if your app is an iPhone app and it has similar hierarchy as, let’s say Stocks and Weather, which is you have this content as well as detailed content, you can easily actually adopt the UISplitViewController.

So once you do that, on iPhone, when you are in the closed pose, it looks like just iPhone app. But when you open it because the split view controller automatically arrange the view hierarchy for you, you will end up get a two-level information hierarchy together at the same time. So it will be an easier adoption for you if you are this kind of app.

Yeah, I think it’s interesting in the workshops I’m looking at you, Kurt. We see a lot of enthusiasm around a new or novel case. Like people are excited to use the different poses for unique things that they can display in their app. And it seems like the general guidance from this group has been like, love the enthusiasm. But first look at just kind of being what like predictable, familiar, you know, in the various poses.

I feel like that’s one of the things. So one of the most fun things about the workshops is like the beginning of the first day we get to hand out hardware for people to work on. And so it’s like Christmas moment, but people immediately start moving the device through all the various ways to hold it and fold it and unfold it and so on.

And I think people realize once they’re hands on with it, that that’s how people are going to use this device. They’re going to open it when they want to see more content, to Russell’s point, they’re going to flip it to a shape like a book when they’re on the bus and they’re holding on to the overhead bar, because then you can hold the device with your thumb in the middle. Like I think all this sort of motion is going to happen.

And so having a sense of place as you move between those poses is actually even more important than you might think at first. Yeah, yeah. And I think that one design principle along with that is to try and avoid limiting features or capabilities or designs to any specific pose. Now, there are certainly some things where it’s like, all right, this thing makes sense because you’re taking advantage of the fact that like it’s propped up or like some other physical layout or physical hardware element of the device, right?

But when you have an iPhone Duo app that doesn’t have to be tied into anything, making sure your app is adaptable and does work when people like use the device and all the different ways as they will, right? As they will learn to do when they’re using the iPhone Duo.

Like I think that’s important as well, that the iPhone Duo is a very flexible and adaptable device, and your app should be pretty flexible as well to how the user wants to use it, rather than asking them to use it in some very specific way. Unless there’s like a real physical reason that it needs to be like that. Yeah.

Another specific API I want to call out while we’re on this topic, like NavigationSplitView is if you’re a sheet-based app, we added a new where you have like a bottom sheet on iPhone. And maybe when you expand, you want to move that sheet to the side. That was previously a little tricky. And we added a new API just this year called presentationPlacement, I think, is a SwiftUI API to move the sheet to the leading or trailing side to make that if you’re.

So if you’re that app, it makes it easier. That was a result of developer feedback that we got at WWDC in June. So that’s an example of feedback that we get from you guys, from all of you. Like we hear it incorporating. So glad, by the way, that we get to sheets. I feel like that’s been really missing from this discussion. So I have to talk about sheets a little bit.

With three minutes to go. Yeah. So speaking of, I want to do a speed round and I’d like to I’m going to ask a question. I’d love to hear each of your perspectives on it. And then we’ll wrap up. But the question is, or the prompt is what was the biggest design or technical challenge you encountered when adapting system apps for iPhone Duo? And Kurt, yeah, you can talk about the workshops.

Grant, do you have a can I start with you? What? I don’t know if this point of view… I worked on a lot of different things for iPhone Duo, so it’s hard to pull out exactly one. But yeah. One really fun one was the level portion of the Measure app.

Okay. It’s and it seems like a very simple thing, but the level is something, you hold it level, it tells you when your phone is level and it works in portrait and landscape. And that was traditionally how you would use it. But the iPhone Duo has so many more poses that you can hold an iPhone Duo in. Right? And what does it mean to be deciding what is level when the device no longer has a fixed orientation?

Right? It could be folded. It could be like looking at it. You could be placing the device almost like a tent, right? Like what does that mean to be level? And so that’s a very specific answer. But that was a very more difficult than it sounds problem on the iPhone Duo.

Nice. I can do a workshop thing. Yeah. And it actually ties back to the last question before people have a chance to hold the device. There’s a strong tendency to want to design something different for all like six poses that we see here. And while that’s fun, It’s a bit of a design playground.

It doesn’t have the stability, that presence that people are going to want when they use the apps. So that’s been a challenge. It’s like to enjoy and experience that, but then move to the best design for the people. Yeah. Yeah. Can I do two quick ones? Yeah. Yeah. So I think one general thing was finding the right balance between doing things for the novelty of the device, because it’s such a new form factor versus things that like actually add value and are like really useful, interesting designs. And maybe the other one that you probably wouldn’t expect is adapting to the sidebar and sorry, the status bar and oh yeah, the camera.

We’ve almost never had to deal with rectangular areas that are unavailable to an app before. So it was an interesting design question and engineering challenge. We’ve just been used to like in the past insetting things from one edge pretty uniformly. And this opened up quite a few challenges, as you can see up here. It’s different in the different poses. Yeah. And just getting all the bars, all the kind of standard system components to do that out of the box was an interesting challenge. And now it’s all available for you. Yeah. Yeah. You can benefit from our pain. Yeah. Fun.

Yeah. Henry, what about you? There’s actually not much technical challenge by adopting iPhone Duo. And I think I have to thank the framework team. Really good job. Our apps adopting the standard navigation bar. Those tab bar and everything just happened automatically into the vertical bar. That’s a really good sign. We do have a lot like safe area issues or handling the camera using a corner adaptation API or the reserved region API.

We do have a lot of those that we need to handle, but we also have a nice skill, from the skills shipping with Xcode, about the App Resizability skill. I encourage everybody just using that skill and run through your apps and you can quickly speed up your adoption on iPhone Duo.

Wrap it up. There’s so many. But also I’ll just do a quick shout-out to search because then I can point out that as you, because there’s so many different places and ways that search can appear. And this device is no exception. As you can see, search is still on the bottom as part of our continuity principle because search is on the bottom on phones.

And so you’d expect it to be on the bottom on the front screen. But on the inner screen, it’s still on the bottom. And so just getting. Whereas on an iPad, it would be on the top right. So just getting search to look well across all the other thing you should reuse is our search components. Awesome. All right. Well, that brings us to the conclusion of this Group Lab.

So I want to give a huge thank you to Mohammed, Kurt, Grant, Henry and Russell. It was great chatting with you all today and for everyone who joined us, thank you for tuning in. If you have more questions or if we didn’t get to yours. I did see a lot of questions in the list, so apologies to those who we didn’t get to.

You can check out the previous Group Labs. There’s a lot of questions that were asked in there. Those are available to stream. You can also check out the updated developer docs, forums, and Human Interface Guidelines. So thanks again and we’re really excited to see what you do with iPhone Duo.