Is Your App Ready for iPhone Duo? A Business Checklist

The 10-Point iPhone Duo Business Checklist 

The first six checks protect the experience you already have. The final four help you decide whether the larger, more flexible screen creates a worthwhile opportunity. 

1. Do you know what your current app is built with? 

Start with the production version, not the design files. Ask your development team which iOS SDK the live app uses and whether it has been rebuilt and tested with Xcode 27.1. Apple recommends recompiling existing apps with Xcode 27.1, which adds development support for iPhone Duo. 

What to check: Confirm the SDK and test build before discussing new features. If nobody can tell you when the app was last updated for a major iOS release, that is a maintenance issue worth investigating on its own. 

For a broader view of ongoing support, see our guide to mobile app maintenance costs. 

2. Does every key screen work at three widths? 

Do not test only the fully opened display. Check the outer screen, the full inner display and a narrower Split View. These three states quickly expose buttons that disappear, forms that stretch too far and layouts that only worked because the old screen size was predictable. 

What to check: Choose the five or ten screens tied most closely to revenue or operations, such as login, booking, checkout, job details or reporting. Test those first. 

3. Are any layouts tied to one fixed iPhone size? 

Apple specifically warns against hard-coded screen dimensions, fixed orientation assumptions and device-specific layout logic. Those shortcuts can leave content clipped, stretched or misplaced as Duo resizes. 

What to check: Ask whether the app sizes itself from the space available or from a list of known iPhone dimensions. Fixed layouts are the first place to investigate if a screen looks wrong. 

4. Does the app keep the user in the same place when the device opens or closes? 

A customer may unfold the phone halfway through checkout. A driver may open it while viewing a delivery. A member of staff may resize a record after entering notes. The device should change shape without the task resetting. 

What to check: Test text entered into forms, scroll position, selected filters, basket contents, media playback and unsaved data. Losing context is a functional problem, not a cosmetic one. 

5. Are the most important actions still obvious? 

More space is not automatically better design. A wide layout can leave actions stranded at the edge of the screen, while a narrow Split View can squeeze too much into too little space. 

What to check: At every size, can the user still find the next important action quickly? If checkout, submit, accept job, confirm booking or save becomes harder to find, the layout needs attention. 

6. Does the app still work properly beside another app? 

Split View matters because the user no longer has to give one app the whole iPhone screen. A logistics user might keep a route beside a delivery record. A student might keep learning content beside Notes. A team member might compare a rota with Calendar. 

What to check: Identify the one or two companion apps your users are most likely to open alongside yours, then test the real task at half width. The goal is not to invent a multitasking feature. It is to make sure your app remains useful when it shares the screen. 

7. Does the larger layout still respect permissions and sensitive information? 

A wider screen may tempt teams to place more records, profile details or status information on one page. That can improve efficiency, but it should not weaken the rules around who can see what. 

What to check: Review wider dashboards by role, especially in healthcare, education and employee management. The same permissions should apply regardless of screen size.  If your product serves several user types, our article on building a platform that works for all users explains why each role needs the right view of the same underlying system. 

8. Are you using the bigger screen to improve a task, or just to fill space? 

The inner display can support richer dashboards, side-by-side information and more detailed workspaces. That is useful only when it reduces steps, improves comparison or helps someone make a decision faster. 

What to check: For every proposed Duo-specific change, write the user benefit in one sentence. If you cannot explain what becomes faster, clearer or easier, leave it out of the first update. 

9. Is your App Store presentation ready? 

Readiness does not stop at the code. Apple has published iPhone Duo screenshot specifications, and from April 2027, apps and games submitted to the App Store will need to include Duo screenshots. 

What to check: Choose a screenshot that proves the app has adapted well, such as a clearer dashboard or useful wider workflow, rather than simply stretching a generic home screen. 

10. Have you separated essential fixes from optional ideas? 

This is the budget check. Broken layouts, lost progress and unusable controls are defects. Better use of the larger screen is an improvement. New fold-aware interactions are optional product work. Treating all three as one project is how a focused update turns into an unnecessary redesign. 

What to check: Create three columns: Fix now, Improve next, Explore later. Fund them in that order. 

What Should You Fix First? 

If the checklist produces a long list, prioritise by the effect on the user and the business, not by how novel the feature sounds.

THE BUSINESS TEST: If the app still lets users complete the same important task quickly and confidently at every relevant screen size, it is ready enough. If the device change interrupts that task, there is work to do.

What Should Different Businesses Test First? 

The checklist is the same for every app, but the highest-value test depends on what the product is there to do.

Does iPhone Duo Mean You Need a Full App Redesign? 

Usually, no. If your app already uses adaptive layouts and has been kept technically current, readiness may be mostly a testing and refinement exercise. Older apps built around fixed sizes, legacy components or years of workarounds are more likely to reveal deeper problems. 

Scope the work in stages: make the existing app reliable on Duo, improve the experience where the larger screen creates obvious value, then test new Duo-specific ideas separately. That keeps the budget tied to evidence rather than launch-day excitement. 

The same principle applies when planning and building a mobile app: define the problem and essential outcome before adding features.

When Should iPhone Duo Not Be a Priority Yet? 

There are sensible cases where the answer is "not yet". If your iOS audience is very small, the app has unresolved stability or security issues, or customers are dropping out because the core service is weak rather than the interface, those problems come first. 

The same applies if a device launch is becoming an excuse for a much larger technology project. A new form factor does not automatically justify a new product strategy. Our guide to digital transformation makes the same broader point: technology investment works best when it starts with a specific business problem. 

The Bottom Line 

iPhone Duo readiness is not about making your app look impressive on a foldable screen. It is about making sure the product still does its job when the screen gets smaller, larger or shared with something else. 

Start with the core journey. Test the screens that make or save your business money. Fix anything that interrupts those journeys. Then decide whether the larger canvas creates an opportunity worth investing in. 

A USEFUL RULE: If an iPhone Duo change cannot be tied to a user problem, a business outcome or a platform requirement, it probably does not belong in the first phase.

FAQs

Will my existing app work on iPhone Duo? 

Yes. Apple says all apps will run on iPhone Duo. The question is how well the app adapts as the available space changes, so testing is still necessary. 

Do I need to rebuild my app from scratch? 

Usually not. A well-maintained app may only need targeted layout or workflow changes. A larger redesign is more likely if the current app already relies on fixed dimensions or older components. 

How should developers test an app for iPhone Duo? 

Apple recommends recompiling with Xcode 27.1 and using Device Hub and Duo development support to check behaviour across poses and orientations. 

Should a small business optimise for iPhone Duo immediately? 

Only to the level justified by its users and product. Make the existing app stable and usable first. More ambitious Duo-specific work should follow only when there is a clear customer or operational benefit. 

Explore More

• Apple’s Human Interface Guidelines: Layout Guide

• Apple’s Liquid Glass Design from WWDC 25

• The Top Rules for Exceptional UX/UI Design in App Development

• Designer VS Developer Handoffs: What We Wish The Other One Knew

• How to Plan and Build a Mobile App in 2026 Cardiff App Developers

• Mobile App Maintenance Costs: What Every Business Should Know