iPhone Duo Apps Look Small? Check Before Resetting

An app can open a document, scroll normally, and still leave much of a folding display unused. That is a different support request from a button that never registers a tap. Calling both “black bars” makes the next step harder to choose.

Before changing settings, locate the boundary. Does the empty area surround the entire app, only the movie inside it, or a control that has stopped responding? Those observations lead to different next steps.

Start with what still works

Keep the affected screen open long enough to describe it. If the app’s text, menus, and buttons all sit within one smaller rectangle, record that as a window-size issue. If the menus reach across the display but the video has dark margins, record it as a media-viewing question. If a visible button does nothing, describe the failed action separately from the empty space.

A screenshot can show the first two patterns. A short recording may explain an unresponsive control better. Neither, by itself, establishes the underlying cause.

Why an app can run without using all the display

Apple’s developer preparation guide describes three build generations. Apps built with the iOS 26 SDK or earlier appear in a smaller central window when the Duo is open. An iOS 27 SDK build can use most of the inner display while leaving the right status-bar region clear. The iOS 27.1 SDK generation supports the full display and adapted bars.

The SDK is part of how a developer builds an app. It is different from the iOS version installed on your phone. Updating the operating system does not turn an existing download into a newly built app.

This also explains why “updated recently” and “adapted well” are different questions. Apple asks developers to check resizing and assumptions about window dimensions. A release date alone cannot tell you whether a particular screen has been checked.

For a stable, small app window, erasing the phone would not change the app’s existing build. That is a reason to check the developer’s information before treating a layout limitation as a device fault.

Read community reports with their version attached

An Acrobat report includes a useful paper trail

On October 28, an Adobe Community user reported that Acrobat occupied roughly one-third of the inner screen. The follow-up supplied version 26.09.50 (20261015.195651) and said changing orientation did not resolve the size problem. On October 29, an Adobe community manager said the report had been passed to the development team.

That establishes a dated report and an acknowledgement. It does not establish the behaviour of today’s newest build, a confirmed root cause, or a repair timetable. Before repeating the complaint, check whether your installed version matches the one discussed.

A video question needs a different answer

In a Reddit thread titled “Black bars,” an owner asked about filling the screen with video. That is a question about the media view, not evidence that every app is opening in a small window. The thread is useful for identifying the confusion; its replies are not an Apple specification.

A rectangular video and its player can have different proportions. Preserving the complete picture can leave unused space. Filling the container may instead crop part of the picture. If the player offers a fit or fill control, compare the edges of the scene as well as the amount of black space. Availability depends on the app.

A question on Apple’s forum is still a question

A September 16 Apple Support Community discussion asked whether Maps and Music could share a vertically held Duo. It predates retail availability, and some replies explicitly relied on event videos. It shows a real intended use, but should not be cited as proof of a current defect or definitive support for a feature.

Across these examples, the missing detail changes: app version, the boundary of the video, or whether anyone has verified the proposed workflow. Combining them into a single list of “Duo problems” loses that distinction.

Make one comparison, then record the result

Use the same task on the outer and inner displays. Open the same document, message, or app screen; avoid switching between unrelated views. Note whether opening the phone changes only the size, or also moves controls or prevents the task from finishing.

Next, try a comparable action in another app. One affected document viewer points you toward an app-specific investigation. A touch area that fails across unrelated apps deserves a broader support discussion. This comparison narrows the report; it is not a hardware diagnostic.

Change one thing at a time. After noting the original app and iOS versions, check for an app update and repeat the same task. Record the new version and what changed. Otherwise, an update can remove the evidence you need to explain an intermittent problem.

Give the developer something reproducible

“Please fix black bars” leaves the recipient guessing. A useful report names the exact task, view, and failure. You can copy this outline, replacing the prompts with your own observations:

Device: iPhone Duo
App and version: [name + exact version/build]
iOS version: [installed version]
Display and position: [inner/outer; open/closed; orientation]
Task: [what you were trying to do]
Steps: [short sequence that reaches the affected screen]
Expected: [what you expected to happen]
Observed: [window size, unused area, or failed control]
Repeatability: [every attempt / sometimes / once]
Comparison: [same task on other display or in another app]
After update/reopen: [version and result, if checked]
Evidence: [redacted screenshot or short recording]

Example wording, not a test result: “The document opens and scrolling works. On the inner display, the toolbar and page remain together inside a narrow central window. Rotating the phone leaves the window similarly narrow. The same document is readable on the outer display.”

That description separates an unfinished layout from lost document access. If tapping Export fails, add that as another observation rather than assuming the margins caused it.

Remove names, messages, account details, and confidential documents from attachments. Use the developer’s support channel linked from its App Store listing. A public forum post is optional.

When to move beyond layout troubleshooting

For an app that freezes, closes, or refuses to open, Apple’s app troubleshooting guidance covers reopening it, restarting the device, and checking app and system updates. These are checks for malfunction, not a guarantee of a redesigned interface. Apple also warns that deleting an app can remove locally stored data; verify what you need to keep before considering that step.

If an entire display stays black, use Apple’s Duo-specific black-screen guidance instead of an app-letterboxing tutorial. Persistent touch failure across apps, visible physical damage, or a display that remains unusable belongs with Apple Support.

A reset needs a defined purpose: which symptom should change, what evidence supports that expectation, and how will your information be protected? For a working app confined to a smaller window, the developer’s build information is a more useful first lead.

Finish with a sentence you can verify: “In this version, on this display, this action produces this result.” That gives the next person a starting point—and gives you a way to tell whether a later update actually helped.