When a new smartphone form factor hits the market, every specialist on the team looks at it through their own lens. Developers focus on APIs and technical constraints, while designers think about how to adapt interfaces to a new screen shape.
A project manager looks at the bigger picture. What does this mean for current and upcoming projects? How much extra time might adaptation require? What risks could it add to timelines, and when is the right moment to raise the topic with the client?
The iPhone Duo is a case in point. Apple unveiled it on September 9, 2026, and sales start on October 23 (MacRumors).
That does not mean every mobile project needs a dedicated plan for the new device tomorrow. It does mean the release belongs in planning now, before the first client asks, "How do you plan to support this, and will it be adapted into our project?"
This article keeps the specs short. It is a project manager's view of what changes in practice: the backlog, estimates, risk, adaptation work, QA, and client communication.
What the iPhone Duo changes for apps
The iPhone Duo pairs a 5.4-inch outer display with a 7.6-inch inner one and starts at $1,999. For app teams, the key change is movement: an app shifts between displays as the phone opens, closes, or stays partially folded.
Apple's guide for developers names three things to check. Layouts must resize to any container, content must avoid the fold, and navigation bars move to the side of the screen in some poses. Apps built with Xcode 26 or earlier also leave part of the screen unused, so any app that ships an update after launch should move to the latest Xcode.
Why the iPhone Duo matters even before launch
The foldable smartphone segment has been evolving for years. Samsung showed its first flexible display prototype at CES back in 2011, and in 2018 the Chinese company Royole released the FlexPai, one of the first foldable smartphones on sale. Huawei and other manufacturers have joined the segment since then.
So Apple is joining a market with an existing user base and proven use cases. What changes is scale: the iPhone Duo could bring a much larger iOS audience into foldables.
For companies building mobile apps, this is an important signal. Foldables have grown steadily for seven years, which makes them a maturing category with a track record. Apple's entry will likely make them far more visible to iPhone users.
Analysts expect that growth to continue. IDC projects foldable shipments to grow 30% in 2026, driven by the iPhone Duo (IDC), and Counterpoint expects the market to expand 37% in 2027 (9to5Mac). The estimates differ, but the direction is consistent: foldables are moving from a niche into an established part of the smartphone market.
For a PM, the key question is shifting. The segment clearly deserves attention. The open question is whether the iPhone Duo will catch on among iPhone users, and how quickly that will show up in mobile product requirements.
Until the iPhone Duo launches, there is no point carving out a separate scope for it. What a team can do now is assess its potential impact:
- How dependent is the product on an adaptive interface?
- Which scenarios might change on a different form factor?
- What does this mean for testing?
- How relevant is any of this for the product's audience?
Once the device is out, usage data can test these assumptions: whether users with the new device show up, which scenarios they use, and whether interface issues appear.
So right now, the PM's job is to set up a process that lets the team assess the iPhone Duo's impact quickly, before and after launch. Predicting demand can wait for the data.
The worst thing to do is stay quiet and wait for the client to bring it up on a call.
Where the iPhone Duo creates opportunities for app owners
Risk is only half of the planning picture. The other half is where early adaptation can pay off.
Device share. Counterpoint forecasts up to 6 million iPhone Duo shipments in 2026, about 25% of the foldable market in its first months on sale. For 2027, it expects Apple's volume to more than double and its share to reach 40% (9to5Mac). Foldables are still about 2% of all smartphones, so year one means a small audience with a steep growth curve.
A first-mover edge on the App Store. Apps that skip the update may run inside black bars on the inner display (9to5Mac), so a full-screen app stands out in the weeks when new owners explore what their phone can do. Apple has not announced an iPhone Duo label or App Store section yet (Gadget Hacks). Its editors have often promoted apps built for new hardware, and naming iPhone Duo support in your screenshots and release notes helps Duo owners find you in search.
Premium buyers. At $1,999 and up, early owners are people who pay for premium tools. No published study yet proves that foldable owners spend more in apps, so treat this as a hypothesis to check in your own analytics.
Products that gain most. A 7.6-inch screen fits more on one view. Marketplaces can show a list and a product page side by side. Wellness apps can play a workout video on one half of a partially folded phone and keep the controls on the other. Productivity and finance apps get room for dashboards and documents.
New markets from the same work. Apple's resizing tools for the Duo are the same ones used for iPad and Mac. A team that adapts an app for the Duo also gets most of the way to a solid iPad version. Adaptive layouts carry over to Samsung and Huawei foldables too, which hold about 60% of the segment between them.
What to do before the iPhone Duo launches on October 23
Only your own data can show how much the iPhone Duo matters for a product, and that data starts on October 23, when the device goes on sale. As a PM, I separate two things here: the iPhone Duo as a specific device, and foldable smartphones as a market segment. Preparation now should cover both.
First, analyze your own data. What share of the product's audience already comes from other manufacturers' foldable devices? Which models do they use? Are there issues with interface rendering, state transitions, or specific scenarios? This data shows how relevant the topic is for a given product, whether or not the iPhone Duo has launched.
Second, put the topic on the planning radar without acting on it yet. I would log it as a factor the team revisits during regular planning. As long as the impact stays low, monitoring is enough.
Once the iPhone Duo launches, check whether these devices show up among the product's users and whether the share of foldables in the audience is shifting. If the data shows real impact, or the client raises the requirement, that is the moment to revisit scope and estimates.
Third, sync with design, development, and QA ahead of time. A foldable brings more variables than a new screen size. The outer and inner displays, aspect ratios, state transitions, and Split View can all differ by device. So even before a formal requirement arrives, the team can identify which projects will likely need extra design or testing work.
Finally, look at the audience of each product. For some projects, foldable support is relevant already because of users on Samsung and Huawei devices. For others, the question may come up later, once it is clear whether the iPhone Duo affects their audience at all.
Until October 23, there is time to study the market and your foldable audience and to get the team ready. After that, iPhone Duo usage data can confirm those assumptions and, if needed, reopen scope. This approach saves resources early and means the assessment is ready when a real requirement shows up.
Three process changes that prepare a team for foldables
At this stage, the work goes beyond a single project. It is about setting up processes across the whole company.
There are at least three things I, as a PM, am factoring in right now.
1. Update the Definition of Done for new screens
Add a check for how the interface behaves when the device's form factor changes mid-session, on top of the usual screen-size checks.
2. Define a testing approach ahead of time
Together with QA, decide how the team will test support for foldable devices:
- Is a simulator enough? Apple's simulator supports the iPhone Duo, which covers most layout checks.
- When is a real device required?
- Which scenarios need separate tests?
- Does testing different device states fall within the standard QA scope?
3. Add a dedicated line item to the estimation template
The estimation template for new projects can include a "Foldable devices" line item. Even when it needs no extra hours, the team explicitly checks whether this factor affects design, development, QA, or support.
How Otrofy is preparing client projects for the iPhone Duo
We think now is the right time to get ready, calmly and before a client asks. Here is what we are already doing:
Assessing existing projects. We estimate the rough scope of work across current projects in three areas: design, development, and testing. The estimate rests on what we know today and gives a sense of the challenges each project could face.
Taking a data-driven approach. We look at our own data to assess the real need for this work. The first foldable smartphones appeared years ago, and many apps still have not adapted to them.
Monitoring. We keep the topic on the radar by tracking analytics, client requests, and new devices, so we know when it becomes relevant for a specific project.
Because the foldable market is not new, we log foldable devices as a factor we check during every project planning and estimation.
Monitor → collect data → assess impact → revisit scope once a real need shows up.
This approach avoids spending resources too early and keeps a new client requirement from catching us off guard.
Apple unveiled the iPhone Duo on September 9, 2026. Pre-orders open October 16, and sales start October 23 in the US and more than 70 other countries, with 28 more countries following on October 30.
Yes, existing apps run on the iPhone Duo, but their layouts may not fit well. Apps built with Xcode 26 or earlier leave part of the screen unused, and fixed-size layouts or custom navigation bars can break around the fold.
It depends on how the app handles layout today. An app that already supports iPad or uses Apple's standard layout containers needs mostly testing and small fixes. An app built on fixed iPhone dimensions needs design and development work screen by screen.
Check your analytics first. If Samsung and Huawei foldable users already make up a noticeable share of your audience, adapt now. Marketplaces, wellness, productivity, and media apps gain the most from the larger screen, so they have the strongest case for early support.
Start in Apple's simulator, which supports the iPhone Duo, and check every screen closed, fully open, and partially folded, in each orientation. Use a physical device for camera switching and the feel of opening and closing the phone.
Counterpoint forecasts up to 6 million iPhone Duo shipments in 2026, limited by supply, which would give Apple about 25% of the foldable market. It expects Apple's volume to more than double in 2027 and its share to reach around 40%. Foldables still make up about 2% of all smartphones, so the audience starts small but grows quickly.
