Is Your iOS App Ready for iPhone Duo? A Practical Readiness Checklist

A plain-language checklist for app owners to find out whether their iOS app is ready for iPhone Duo: build status, layouts, resizing, screenshots and the April 2027 App Store requirements, with what each finding means.

iPhone DuoiOSChecklistApp StoreMobile Apps

Is Your iOS App Ready for iPhone Duo? A Practical Readiness Checklist

You do not need to read code to find out whether your app is ready for iPhone Duo. Most of the answers come from five questions you can put to your developer, or to a freelancer who built the app years ago, and two things you can check yourself on a device. This checklist is ordered from cheapest check to most expensive.

It is based on Apple's published requirements for iPhone Duo, which take effect for App Store submissions in April 2027. The sources are linked at the end.

How do I know if my iOS app is ready for iPhone Duo?

Your app is ready when four things are true: it builds with a current Xcode, it uses layouts that resize instead of fixed screen sizes, it does not depend on opting out of resizing, and you have iPhone Duo screenshots for the App Store. If any one is missing, the app can still run, but you cannot ship an update after April 2027.

Use the sections below to check each one.

Which Xcode and SDK version built my current release?

Apple's baseline guidance is to recompile existing apps with Xcode 27.1, which adds development support for iPhone Duo. From April 2027, uploads must also be built with the iOS and iPadOS 27 SDK or later, targeting iOS 15 or later.

Ask your developer for the Xcode version used for the last release and the minimum iOS version the app supports. Three outcomes are common:

What you hear	What it means
"Latest Xcode, builds fine"	Best case. Recompile, test, screenshots.
"An older Xcode, but it builds"	Likely a dependency update and a round of testing.
"Nobody has built it in a while"	Treat as a recovery job. Budget an audit first.

Can my app still be compiled by a current Xcode?

Often not without work. Apps that have not been updated in a few years commonly depend on libraries that have since changed or been abandoned, and a current Xcode will refuse to build them until those dependencies are replaced. This is the single most common source of surprise cost in an update.

The check is simple: have someone open the project and attempt a clean build with the current Xcode. The result, success or a list of errors, is the best predictor of effort you can get for the price of an hour.

Does my app use layouts that resize?

Apple's Human Interface Guidelines state that if your app uses standard system components and is designed to support resizing, it adapts to iPhone Duo's poses with little adjustment. iPhone Duo has two displays, each with its own front camera, and a center hinge that affects the space available to content.

The owner-level test: run the app on an iPad or in a resizable simulator window and watch what happens when the window changes size. Screens that stretch badly, clip content, or leave controls stranded are the ones that need layout work.

Does my app rely on UIRequiresFullScreen?

This is the one that catches apps by surprise. Before iOS 27, the UIRequiresFullScreen setting was ignored on iPhone and only affected iPad. Under the iOS 27 and iPadOS 27 SDK, per Apple's Technical Note TN3192, it no longer opts an app out of resizing on either platform.

If your developer says the app "locks" its size or orientation that way, it needs real engineering work rather than a rebuild. Apple points developers to its WWDC26 material on discrete scene resizing for the migration.

Do I have iPhone Duo screenshots?

From April 2027, every submission must include them, and apps that do get a badge on their product page showing they are optimized for the device. Screenshots are not an afterthought: they need the app running on a Duo-sized canvas, which means the layout work above has to be far enough along to photograph.

Plan for them as a deliverable with its own owner and its own date.

What does each result mean for budget and timing?

Your situation	Typical shape of the work
Builds, standard layouts	Rebuild, test on Duo sizes, screenshots
Builds, fixed or custom layouts	Layout rework on affected screens, then the above
Does not build	Dependency recovery first, then layouts, then the above
No source code or no one with access	Recovery of the project or a rebuild decision

We deliberately do not put dollar figures on the middle rows here. The spread between "rebuild and screenshots" and "recover and rework" is wide, and an honest number needs someone to look at the actual project. Our fixed prices for new builds are on the pricing page.

Where Cuanto Labs fits

We are a founder-led studio: Eliran Yihye scopes and leads every engagement, working with a small, vetted network of senior contractors. For apps we did not build, we start with a paid audit rather than a guess, because the answer to "does it build, and do the layouts hold up" decides the whole scope.

If you would like a straight answer on where your app stands, begin with our free audit, or read about our mobile app services. If you are still weighing whether to patch or start over, see update or rebuild your iOS app.