iPhone Duo apps: running is not the same as fitting the screen

A folding phone can give an app more room without making that app ready to use it well. Ahead of Apple's announced 23 October customer availability for iPhone Duo, the practical question is what happens to the tasks you already depend on. Apple's developer guidance distinguishes several app layouts. That is a more useful starting point than assuming a familiar app will automatically become a miniature desktop.

Three things to know

• Apple distinguishes apps running from apps adapting to more of the display.
• The developer's SDK version affects layout; it is not a user setting.
• A proposed check should follow your actual task through folding and unfolding.

Three app builds, three layout descriptions

Apple says apps built with the iOS 26 SDK or earlier can run, but do not adapt to every layout: on the open device they appear centrally with surrounding empty space. An iOS 27 SDK build fills most of the inner display while avoiding the right-edge status bar. With iOS 27.1 or later, Apple describes full-display use and vertically arranged toolbars and tab bars. It still tells developers to check that their content adapts.

SDK means software development kit: the tools used to build the app. It is not a display mode a buyer can enable. The modest reading of Apple's distinction is that an operating-system version alone does not tell you how a particular app was built. Nor does unused screen space prove that an app is unusable. Look at the function you need before deciding whether its presentation is a problem.

Ask for a task, not a sweeping demo

Make a short list of work that would justify the larger screen: reading a document while checking a message, reviewing a photograph, or completing a form. Then describe a small, repeatable sequence. Can you find the document, reach the relevant control and finish without losing your place? These are suggested questions for an authorised demonstration, not results PING has obtained.

If a demonstration is available, ask to repeat that sequence with the device open and closed. Watch whether the same content and controls remain usable rather than judging only a polished opening screen. Use sample material, not private messages, banking credentials or client files on a shared device. Record the app and software versions alongside any observation so a later update is not confused with the build you saw.

Treat the store badge as a starting point

Apple's 5 October submission announcement says submitting iPhone Duo screenshots produces an App Store product-page badge identifying optimisation. Use that as a reason to examine the app's current page, not proof that your own workflow has been tested. A screenshot cannot answer every question about a long form, a particular attachment or the account you use.

For developers, Apple lists simulator and resizing checks. For readers, the corresponding useful habit is a precise question to the app maker: which current release supports the layout you need? Keep an unresolved answer unresolved. Do not substitute a different app, a reviewer's result or a staged marketing sequence for evidence about your own essential task.

Keep the purchase decision separate

A reader in London, Lagos or Nairobi still needs separate answers about the actual seller, service access and local support. Those examples are not a confirmed country rollout. Apple's announced start date does not establish a particular order's arrival. This guide does not verify stock, prices or repair arrangements, and app-layout documentation cannot settle them.

The payoff is a narrower, answerable question: will the app and task you need benefit from this screen? Keep running, adapting and completing your workflow distinct. Read more source-led explainers on PING's Gadgets desk.