Guidelines
Human Interface Guidelines
Short and opinionated. Three rules cover most of what makes an app feel right on a phone that folds; the rest is iOS.
Design for the cover first
The cover display is 387 points wide; the inner display is 790, a little more than two covers. A layout that reads on the cover has room to breathe unfolded: a list becomes a list beside its detail, a toolbar spreads out, a chart gets its axis labels back. The reverse never works: an inner-first layout squeezed onto the cover loses controls or text.
Lay out in boxes and let width decide. The kit's components collapse themselves at cover width; yours should too. Never hide a feature on the cover: the person may never unfold the phone for it.
Your app runs twice
While the phone is in use, the other display holds a running copy of your app so the fold hands over without a remount or a flash. The copy draws everything and starts nothing: no sound, no network request, no timer of its own. State that both copies must agree on lives in shared storage, not in a component.
Test it: open your app, fold the phone all the way, unfold it. The same note, the same scroll position, the same playback, once.
Tokens only
Every colour, font size, radius and easing comes from the kit's tokens. No hex, no pixel font sizes. This is not taste: the two displays have different densities and the shell tunes the palette for both, and an app with literals looks wrong on one of them and inherits no fix.
And the iOS rules still hold
- Navigation is a stack with a back button on the left; Escape goes home.
- Text input works on the cover: a note, a search, a message, at 387 points.
- Timings are iOS timings. Pushes take about 380 ms; nothing bounces twice.
- A widget is a snapshot the shell draws, with its age shown. It is not a live view of your app.
Every component: UI kit. The fold's mechanics: Displays and the fold.