Hello

Let's work together.
Have a Project in mind? Contact Us
13 Nov 2026

The iPhone Duo is here. Is your app ready for phones that fold?

Apple's first folding phone went on sale on 23 October, and within days some owners were reporting cracks along the fold. Apple says a small number of units are affected and is replacing them.

Screens can be replaced. The more lasting question for any business with an iPhone app is what that app looks like when the phone opens into a 7.6-inch tablet.

For most apps today, the answer is: small, centred, with empty space on both sides.

One phone, two very different screens

The iPhone Duo has a 5.4-inch outer screen and a 7.6-inch inner one. Both are much squarer than a normal iPhone, so a layout designed for a tall, narrow phone does not simply stretch to fit.

Your app will still run without changes. How it looks depends on how it was last built:

App last built with On the open (inner) screen
iOS 26 SDK or older A smaller window in the middle, empty space on both sides
iOS 27 SDK Fills most of the screen, with a gap on the right edge
iOS 27.1 SDK, adapted Fills the screen; eligible for the "Made for iPhone Duo" App Store label

That label matters. Users who just paid around $2,000 for a phone will notice which apps use the big screen and which look like they were left behind.

What changes in April 2027

Apple has already set two deadlines that apply to every iPhone app, whether or not you plan to adapt for the iPhone Duo:

  • A newer build is required. From April 2027, every new app and every update uploaded to the App Store must be built with the iOS 27 SDK or later. Apps built with older versions keep working, shown in a smaller window, but you can't ship an update until the app moves to the newer version.
  • iPhone Duo screenshots are required. From April 2027, every new app and every update must include App Store screenshots for the iPhone Duo.

Apps already on the App Store stay live and keep working if you do nothing. The rules apply as soon as you submit your next update, even a small bug fix. And once your App Store page has to show your app on the iPhone Duo, it needs to look like it belongs there.

What adapting an app actually involves

For a well-built app this is an update, not a rebuild. These are the areas we look at:

  1. Layouts that adapt, not layouts for one phone. Fixed widths and "if it's this iPhone model" logic have to go. The app should respond to the space it has.
  2. A real tablet layout for the inner screen. Stretching the phone layout wastes the screen. A list with details beside it, a map with results, a dashboard with more on view: that is what users expect when they open the phone.
  3. Keeping the user's place. Opening or closing the phone must not lose a half-filled form, a basket or a scroll position.
  4. Toolbars and navigation. On the inner screen Apple moves bars to a vertical strip. Custom-built bars and hard-coded positions need checking.
  5. Small details that break. The iPhone Duo uses Touch ID, not Face ID, so text that says "Face ID" is wrong. Images, video and charts need checking at the new proportions.
  6. New App Store screenshots for both screens (required from April 2027), and testing on the device itself or Apple's simulator.
Do you need to move now?

Not every app needs a full adaptation today. The iPhone Duo is expensive, stock is limited, and most of your users will be on a normal iPhone for years. But every app with an update planned after April 2027 needs at least the newer build and the iPhone Duo screenshots.

Worth planning now if your app is one where people browse, compare or work: shopping and catalogues, booking, dashboards and reports, field and staff apps, media and reading. These gain the most from a bigger screen.

Can wait for the next regular update if your app is short and simple: a loyalty card, a quick payment, a check-in. Make sure that update happens before April, or at least that you're ready for the new requirements when it does.

Either way, the work behind it is the same: an app that adapts to the screen rather than one designed for a single phone. That also pays off on iPads and on Android foldables, which have been around for years.

Where to start

Start with a short review: how your app was built, how it behaves on both screens today, and what it would take to adapt it. That gives you a clear choice between "now" and "next update", with a cost attached.

Do it well before April. The worst time to find out your app isn't ready is when you need to push an urgent fix and the App Store won't accept it.

We are starting these conversations with our clients now. If you have an app, with us or with someone else, and want to know where it stands, get in touch.

We talked about the iPhone Duo's rocky start on The Breakroom #70.