# iPhone Duo app readiness: layout testing and App Store screenshots > Prepare for iPhone Duo with an app-layout audit, resize tests, and a checklist for App Store screenshots ahead of the 2027 requirement. > By Dave · 2026-10-09 > Source: https://otf-kit.dev/blog/iphone-duo-app-store-readiness Apple’s iPhone Duo is scheduled to reach customers on October 23, 2026. If your iPhone app is already in the App Store, the practical question is whether its interface adapts when the available window changes—and whether your next release will include the new device’s screenshots. Apple says optimized apps can be submitted now. Starting in April 2027, submissions using the iOS 27.1 SDK or later must include iPhone Duo screenshots. That gives teams two separate workstreams: make the app behave well across changing window sizes, then prepare the product page assets that show the result. This checklist turns Apple’s launch guidance into a sequence you can verify before scheduling a release. Apple’s preparation page and screenshot specifications were checked on October 9, 2026. ## Start with the submission dates Put three dates in your release plan: - **October 23, 2026:** Apple says iPhone Duo becomes available to customers. An app does not have to be optimized to run, but Apple says apps built with older SDKs will not adapt to every layout. - **Now:** Apple says teams can submit apps optimized for iPhone Duo today. You can start testing and prepare updated screenshots before customers receive the device. - **April 2027:** Apple’s news announcement says screenshots for iPhone Duo will be required for any app or game submission. The current App Store Connect screenshot specification page phrases the requirement as applying to apps using the iOS 27.1 SDK or later. Check the current requirement in App Store Connect when you plan a submission; do not assume that one phrasing overrides the other. The release date is not the only milestone. A team that waits until the next major feature release may have little time to inspect its layouts, capture assets, and get an updated build through its usual review process. ## Decide which SDK behavior you are targeting Apple describes three relevant states. Apps built with iOS 26 or earlier run on iPhone Duo, but may not adapt to all layouts. With the device open, the app appears centered with surrounding empty space; on the outer display, content sits to the left of the status bar and camera. Apps built with the iOS 27 SDK resize to fill most of the inner display while still avoiding the status bar on the right. Apps built with iOS 27.1 or later are optimized to use the full display, with toolbars and tab bars appearing vertically below the status bar. This is a product decision as much as a compile setting. If you intend to ship an optimized build, verify that every screen remains usable when those bars move and the app window changes shape. Apple specifically warns that content must adapt to vertical bars before shipping with the iOS 27.1 SDK. If you use a managed build service, check its current build-image documentation for Xcode 27.1 before committing to a release date. The documentation should identify the Xcode version available to your selected build profile; a general statement that the service supports iOS builds is not enough. If the provider does not state that Xcode 27.1 is available for your build, record support as **not confirmed** and ask the provider or choose a documented build environment. Then run a real build and verify the resulting SDK and toolchain. ## Audit layout assumptions before testing Folding and unfolding changes the space available to the app. Apple’s preparation guide recommends reviewing code that assumes the screen is fixed, that orientation identifies the layout, or that device type can be inferred from a size class. Search for fixed screen dimensions and one-time measurements. Layout based on a screen’s bounds can become stale when the app window resizes mid-session. Prefer the active view or window’s available bounds, and update size-dependent work when those bounds change. If the app stores a screen object or reads the size only at launch, check whether that value remains correct after a resize. Review orientation branches as well. Apple advises against using orientation properties to decide layout on this device. Compare the width and height actually available to the view instead. Likewise, avoid assuming that a “regular” width means the app is running on a tablet, or that a particular idiom always corresponds to one layout. Resizable windows can break those assumptions. Finally, inspect full-bleed images and video. A wider canvas can crop the subject when media uses a fill mode. Check that the important content remains visible in both display states, using the current aspect ratio or a deliberate focal point where needed. ## Use the resizability skill as a first pass Apple recommends asking the coding assistant in Xcode to get the app ready for iPhone Duo. The resizability skill scans for patterns described in Apple’s guide, explains findings, and suggests fixes. Teams using a different coding agent can export the skill from Terminal with `xcrun agent skills export`. Treat the scan as triage, not sign-off. Apple says it finds most issues but not all of them. Compare its findings with your own search for screen-bound sizing, orientation checks, device assumptions, exact dimension comparisons, and full-bleed media. Turn each finding into a test case or a code review item, and record which screens or components it affects. ## Test at changing sizes, not just on one simulator preset Apple names three testing options: the resizable iOS simulator in Device Hub, iPhone Mirroring on macOS 27, and the iPhone Duo simulator in Xcode 27.1. For mirroring, Apple recommends resizing the window to extreme dimensions in both directions. The Duo simulator is described as the best way to test the full native experience. Build a small test matrix around the screens that carry your app’s main tasks. For each, inspect a narrow outer-display layout and a wide inner-display layout. Then resize through intermediate shapes rather than jumping between two presets. Watch navigation, forms, data tables, dialogs, media, and any control that depends on a toolbar or tab bar. Try the key task from start to finish after each major resize; a screen that looks correct can still leave an action hidden or difficult to reach. Keep a record of the build’s SDK and Xcode version alongside screenshots or short recordings of failures. This makes it easier to distinguish a layout defect from a build that has not adopted the intended SDK behavior. Re-test fixed issues on both displays and at an intermediate size before calling them done. ![A developer and robot inspect an app journey in narrow, folded, and wide layouts during iPhone Duo resize testing](https://cdn.otf-kit.dev/blog/iphone-duo-app-store-readiness/inbody-layout-resize-test-20261009b.png) ## Prepare screenshots and preview assets Apple’s current screenshot specification lists four iPhone Duo dimensions: 1398 × 2034 and 2034 × 1398 pixels for the outer display, and 2007 × 2853 and 2853 × 2007 pixels for the inner display. The screenshot page says submissions can include at least one screenshot and up to ten per device size. Follow the dimensions and accepted formats shown in App Store Connect when you upload; specifications can change. Choose screens that show the app’s core task, not just a set of empty states. Apple recommends showing support across orientations and using the new App Store Connect preview tool to inspect how screenshots and app previews appear on iPhone Duo. Check that labels, key controls, and important image content remain visible after the asset is fitted to each display. If the screenshot is taken from a build that does not adapt to the inner display, it may communicate the wrong experience even if the image technically meets the dimensions. Before submission, review the product page assets on both displays in the preview tool, then confirm the required device sizes and localizations in App Store Connect. Apple also invites teams to submit a featuring nomination and note support across device poses; treat that as an optional discovery step, separate from the build and screenshot requirements. ![Two app builders review how the same app screenshots appear on narrow and wide iPhone Duo displays](https://cdn.otf-kit.dev/blog/iphone-duo-app-store-readiness/inbody-screenshot-preview-20261009b.png) ## A release checklist for app teams Before you schedule the optimized release, confirm each item: 1. The project builds with the intended iOS SDK and a verified Xcode 27.1 environment. 2. The app uses available view or window dimensions and responds after resizing. 3. Layout logic does not rely on orientation, fixed device dimensions, or device-type assumptions. 4. Full-bleed media keeps its important subject visible across aspect ratios. 5. The coding assistant’s scan has been reviewed, and its blind spots have been checked manually. 6. The core journeys work in the resizable simulator, extreme mirrored window sizes, and the Duo simulator. 7. Toolbars and tab bars remain usable when they appear vertically below the status bar. 8. Screenshots use the dimensions currently specified in App Store Connect and show the real app across the relevant displays. 9. The product-page preview has been checked before submission. 10. Your release notes and support material describe only behavior tested in the release build. For a broader submission workflow, see the [AI-built app App Store submission checklist](/blog/app-store-submission-checklist-ai-built-app). If your app also needs to account for upcoming iOS scene behavior, see the [SDK 58 beta upgrade checklist](/blog/expo-sdk-58-beta-upgrade-gate); it covers that separate migration question rather than iPhone Duo’s asset requirements. ## Sources - Apple Developer News, [Prepare and submit your apps for iPhone Duo](https://developer.apple.com/news/?id=kkphp5qo), published October 5, 2026; checked October 9, 2026. - Apple Developer, [Prepare your app for iPhone Duo](https://developer.apple.com/iphone-duo/prepare/), checked October 9, 2026. - App Store Connect Help, [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications), checked October 9, 2026.