For a guided flow on iPhone Duo, should the navigation state be modeled independently from how the flow is presented across the two displays? For example, if a flow can move from Screen 13 back to Screen 8, how should we think about the navigation path when the user changes between different Duo arrangements?
Hi @Angelica_Riddle,
When developing a guided flow on iPhone Duo, model the navigation path independently from how the flow is presented across the two displays. The device supports dynamic resizing, multiple poses, and transitions between the compact outer display and the expansive inner display. Maintaining a decoupled navigation state ensures that users can seamlessly move back and forth—such as navigating from Screen 13 back to Screen 8—regardless of whether the device is open, closed, or partially folded.
Use system-provided navigation containers like NavigationStack (or UINavigationController) and NavigationSplitView (or UISplitViewController) to handle resizing and display transitions automatically. These containers manage the navigation path state robustly, allowing your app to adapt its layout across the outer and inner displays without losing the user's place in the guided flow.
As users change between different iPhone Duo arrangements and poses, the app layout transitions from a single pane on the outer display to dual panes or expanded layouts on the inner display. By keeping the navigation model separate from the presentation layer, you prevent unexpected state resets when the device folds, unfolds, or rotates.
Lastly, use Xcode and Device Hub to preview your guided flow in all supported poses and orientations. Verify that navigating backward through your custom step sequence functions correctly as the app dynamically adjusts its layout to available space and reserved regions.
For more information, see Designing for iPhone Duo and Preparing your app for iPhone Duo.
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
