Typical upgrade sprint
Layout and SDK pass for a live iOS app that already works on today’s iPhones. Longer if the codebase is far behind or heavily custom UI.
iOS campaign
Apple’s foldable iPhone has a compact outer screen and a large inner display. Existing apps will run — without an update they can look letterboxed or stretched. We do the layout and SDK pass so yours uses both screens properly.
Why this matters
Closed and open are two different canvases. Most shipping apps were built for one.
Closed vs open
The outer screen is a phone. Unfolded, the inner display is much larger. Layouts that assume one width look sparse, letterboxed, or oddly scaled on the inside.
Fixed widths and orientation locks
Hard-coded frames, single-orientation flows, and modals sized for a classic iPhone do not reflow when the device opens, rotates, or is held partly folded.
A current SDK is what unlocks the inner display
Rebuilding against current Xcode and iOS APIs — size classes, flexible stacks, split views where they help — is what lets the app use the large screen instead of stretching a phone layout.
Delivery
A focused upgrade on the app you already ship — not a greenfield rebuild.
Audit layouts
We walk closed, open, and rotated states and list what breaks: letterboxing, clipped chrome, locked orientation, media that does not scale.
Adaptive UI
Size classes and flexible containers. Split or two-pane layouts where the inner display has room — not a stretched phone column.
Current Xcode / SDK
Rebuild on the current toolchain so the app can actually target the new device, not only run in compatibility mode.
Posture testing
Closed, open, and rotated. Scroll position, forms, and playback should survive the fold.
TestFlight
A build you can install and tap through on hardware or the latest simulator before review.
App Store update
Submission, listing notes, and screenshots that show the unfolded layout — not only the old phone frames.
Scope
A typical upgrade is a 1–2 week sprint after we see the app. Exact scope is set in the audit — we do not publish a fake fixed price.
Layout and SDK pass for a live iOS app that already works on today’s iPhones. Longer if the codebase is far behind or heavily custom UI.
Send the App Store link. We tell you what needs updating, what can wait, and whether React Native or Flutter needs extra layout work.
Fit
Owners, PMs, and founders of a shipping iOS app — especially fitness, health, and commerce — who want a fast pass before and around the October 2026 Duo window.
Fit
If you do not have a live app yet, this is the wrong page.
It will almost certainly launch. Without a layout pass it can look letterboxed, stretched, or locked to a phone-sized column on the inner display. “Runs” and “feels right” are different jobs.
Usually no. Most live apps need an adaptive-layout and current-SDK pass, not a new product. If the UI is a pile of magic numbers we will say so in the audit — before any sprint starts.
We still do the work. Native Swift/SwiftUI gets Apple’s adaptive APIs most directly. React Native and Flutter can support Duo; we verify how each reports size changes and fix layouts that assumed a fixed phone.
A typical upgrade is a 1–2 week sprint after the audit. Exact timing depends on how custom the UI is and how far behind the current SDK you are. We scope that from your App Store link, not a guess on this page.
This campaign is for iPhone Duo. If you also ship Android, we can include foldable layouts in the same engagement — say so on the audit call. The default scope here is iOS.
Book a Duo readiness audit. Paste the listing, tell us native / React Native / Flutter, and we will say what is shippable in a short sprint.
Book a Duo readiness audit. Paste the listing, tell us native / React Native / Flutter, and we will say what is shippable in a short sprint.