©Code byMilanParmar

Should you rebuild your iOS app for the iPhone Duo?

Apple showed a foldable. The brief says rebuild. I only change the layout if people already work in two panes. If the app already runs, leave it.

Updated 6 min read

A whole walnut lying on a desk

The email landed the morning after Apple showed the iPhone Duo. Support foldables. Rebuild for the inner display. Should you rebuild your iOS app for the iPhone Duo? Almost never. A new hinge is not a reason to start over.

I already wrote do you need a mobile app, or is the website enough. Duo is not a second yes. I build this as mobile apps, usually the same product as the SaaS, not a second team for a second shape. The first version cutstill applies. Name the person. Name the job they finish. A 7.6-inch screen doesn't invent a job you didn't have last week.

What an iPhone Duo rebuild brief actually means

It means someone watched the keynote. Closed, Duo is a short, wide phone. Open, it is 7.6 inches, the largest iPhone display Apple has shipped. They keep comparing it to iPad. Side-by-side apps. Your current screens will look empty if you only ever designed for a tall six inches. The brief still says make it look like that.

Looking like that is not a product. The local news app is a phone job because readers check nearby stories, with location and push. Not because a new phone showed up. That work sits in selected work. A foldable doesn't turn a brochure into that. It also doesn't turn a one-column dashboard into a two-pane app you now have to staff. The App Store listing is how people find it. It's not the reason to rebuild it.

When you should not rebuild for the iPhone Duo

Skip it. Duo starts at $1,999. I won't spend your autumn making the inner screen look busy for people who bought one to unfold at lunch. Apple says existing iPhone software already runs there. I'll believe that until I see a real session. Someone quoting a rebuild the week of the announcement is how you pay first-version moneyfor a hardware news cycle. I'd be embarrassed to take that job.

  1. 01

    You don't have an app yet

    A foldable iPhone doesn't create a phone job. If people finish the useful thing once in a browser, you wanted a website. If they come back on a URL, you wanted a first version of a web product. Starting in a Duo-shaped Figma is how you pay app money because Apple had a keynote. I won't open a store listing so the inner screen has somewhere to go.

  2. 02

    Nobody works in the open phone

    Duo starts at $1,999. Closed it is a 5.4-inch phone. Open it is 7.6 inches, a small iPad that fits in a jacket. People will unfold it at lunch to show someone. That's not a product requirement. Name who keeps it open and what they finish there. If you can't, you're reacting to the announcement.

  3. 03

    The app you have already runs

    Apple put the existing App Store on Duo. About 300,000 apps just run. Stretching a list to fill more pixels isn't a rebuild. Your screens will look empty on day one. Empty is a week of layout. I won't quote a rewrite because the inner screen looks sparse.

  4. 04

    You already ignored Android foldables

    Samsung has sold book-style phones for years. If you didn't build for those buyers, you had a reason, or you were waiting for Apple. Apple showing up late doesn't make the wait a strategy. Name who pays. Then decide. I won't start a Duo project as an apology for skipping Galaxy.

If you needed a site, make the site excellent on a small screen. That's the website work. A slow page on a 7.6-inch inner screen is still a slow page. A slow website is a product problem, and a foldable won't forgive it. Fix the wait. Then ask about Duo.

When a foldable iPhone is a real product change

People have to work in the open phone, not flip it open in a meeting and close it. Apple said Duo was inspired by iPad. That is the useful part of the keynote. If a slice of your users already work in the iPad app, or in a wide browser tab, you inherited most of the inner screen. The work is to stop hiding the second pane behind a menu when the phone is 7.6 inches wide. It isn't a new backend.

  1. 01

    People already work on two things at once

    Inbox and thread. Map and list. They already hunt for a second window, or they already live in the iPad app. The inner screen is that layout without a second device. If your product is one column of cards, two panes is decoration. If two objects have to stay on screen together, you already owed people that layout. Duo is just where it showed up.

  2. 02

    They leave it open and work

    A demo that opens once in a meeting is not a session. A dispatcher with the map and the job list parked on a counter is. If that is already how the job happens on a tablet, Duo is a tablet they also put in a pocket. If they fold it shut and never open it at work, you put a party trick on the roadmap.

iOS and Android from one codebase, same accounts as the web product, Duo as another size of the same app. That's what I own on this kind of job. I don't start a Duo-only app so someone can put foldable on the roadmap. If the web product isn't a product yet, the inner screen won't invent one. Same rule as what belongs in a first version. Name the job. The phone size is not the job.

What to ship instead of an iPhone Duo rewrite

Pretending every live app needs a foldable edition is how you burn September to December before anyone uses the thing open. The honest first move is a layout pass, taking over what already runs, or waiting until November has numbers. When the job uses the open phone, I change the existing app. I will not rebuild the company because the phone now bends.

  1. 01

    One layout that doesn't look lost at 7.6 inches

    The inner and outer screens are the same shape, so the same screens scale. What breaks is density. Type that looked fine on a tall phone looks lost on a small tablet. A one-column form becomes a desert. Fix the wide layout you already owe a tablet or an iPad. If you already ship two panes on iPad, copy that. Don't invent a Duo-only set of screens, and don't start a third app named foldable.

  2. 02

    Watch who actually unfolds it

    Duo ships October 23. Pre-order is October 16. You won't have honest sessions on announcement day. After it is in pockets, look at who keeps it open, on which screen, longer than a novelty unfold. If that number is a rounding error, you saved the autumn. If it is the job, I price two panes as a pass, not a restart.

If a normal iPhone already finishes the job, I stretch the layout and wait. I don't start a rewrite until you can name who stays in the open phone and why the tall one fails.

If the brief is just the word Duo, send me the job they do today. Tell me what you're building.

FAQs

Will my existing App Store app work on iPhone Duo?

Yes. Apple put the existing store on it. Your listing doesn't need a rebuild to appear on the device. You may owe a layout pass later if people actually work in the open phone. That's a follow-up, not a day-one rewrite.

Do I need a separate iPad app and a Duo layout?

No. If the job is two panes, one layout that grows should cover iPad and the inner screen. A Duo-only app is a third product. If nobody uses a tablet today, don't start an iPad project so Duo has a matching screen.

An investor asked about iPhone Duo support. What do I say?

Say existing apps already run on it. You'll look at unfolded use after people you care about have one. A slide that says foldable-native is not a build. If they want a date, November, after you can see a session that stays open.

Should the website get a two-pane layout for Duo's browser?

If the site is a brochure, no. A wider phone is still a phone. If the site is the product, and people already work in a wide browser tab, the same wide layout you owe a laptop will mostly cover it. Don't design a marketing page for a foldable.

When should I even look, if it ships in October?

After people you care about have one, and you can see a session that stays open. Announcement week is for gadget sites. A brief written the morning after the keynote is a wish list. Put it on the list for November. Build what already has users until then.