← ClaudeAtlas

iphone-duo-adaptationlisted

Adapt iOS apps (SwiftUI and UIKit) for iPhone Duo, Apple's folding iPhone: two displays, a hinge, toolbars and tab bars that move to the side, reserved regions, and the iOS 27.1 layout APIs (ArrangementView, UIArrangementViewController, reservedRegions, onHingeChange, axisBehavior, toolbarVerticalBehavior). Use this skill whenever the user mentions iPhone Duo, a foldable or folding iPhone, the hinge or fold, book or laptop pose, inner or outer display, Device Hub, vertical bars, or ArrangementView. Use it too when an iOS layout looks stretched, centred with dead space, squeezed or clipped on a wide or short screen, when toolbar items overflow or jump to the side, or when auditing an app for iOS 27 / Xcode 27 readiness, even if nobody says "Duo". Provides API spellings verified against the shipping SDK, measured device metrics, the traps that cost real debugging time, compile-checked samples, and scripts that audit a project and verify the SDK.
sven-ericmolzahn/iphone-duo-skill · ★ 18 · Code & Development · score 82
Install: claude install-skill sven-ericmolzahn/iphone-duo-skill
# Adapting an app for iPhone Duo iPhone Duo is Apple's folding iPhone: a compact outer display, a large inner display, a hinge between the halves, and a front camera on each side. Three consequences break real apps: 1. **The screen got wide and short.** A layout that centres a phone-width column — or stretches one — ends up with dead paper or 600-point-wide controls. 2. **The bars moved to the side.** Status bar, Dynamic Island, toolbar and tab bar share one *vertical bar* on the outer display and on the inner display in landscape. Safe areas become asymmetric. 3. **The display folds while the app is running.** A 40-point hinge band becomes a reserved region and the layout must re-flow live, with no scene-phase change to hang it on. Apple's position is the spine of this skill: **adapt to size classes and container size — never to the device, the pose, or the orientation.** An app that already resizes well gets most of this for free. The skill is about the part that isn't free. ## Ground truth first These APIs were days old when this was written, so there is little to check a spelling against except the SDK itself. The traps survive a plausibility check: the reserved-region kinds are singular (`.division`, `.occlusion`) where prose pluralises them naturally, and a name that compiles can still be the wrong one. A wrong name costs a build cycle; a wrong mental model costs an afternoon. So before writing code: ```bash scripts/check-sdk.sh # which Duo APIs does the in