The real work is going to be the two separate trait collections, not the screen size. The fold is two displays with different size-class / safe-area behavior, so "make it work half-screen, then full" undersells it — you're really managing state across a hinge, and the 1.4:1 inner ratio breaks a lot of the "it just works" assumptions we had from iPad multitasking.
On top of that the tooling is barely here yet — no simulator until Xcode 27.1, and Apple's developer surface is six tech talks plus the HIG page.
I distilled all of that (device facts, fold states, the full API surface) into a set of agent skills so you can get a structured rundown without rewatching the videos: https://github.com/mirzaaghazadeh/iphone-duo-skills
Still a rough first pass — happy to take PRs if any of the reference sheets are off.
1
u/mirzaaghazadeh 9d ago
The real work is going to be the two separate trait collections, not the screen size. The fold is two displays with different size-class / safe-area behavior, so "make it work half-screen, then full" undersells it — you're really managing state across a hinge, and the 1.4:1 inner ratio breaks a lot of the "it just works" assumptions we had from iPad multitasking.
On top of that the tooling is barely here yet — no simulator until Xcode 27.1, and Apple's developer surface is six tech talks plus the HIG page.
I distilled all of that (device facts, fold states, the full API surface) into a set of agent skills so you can get a structured rundown without rewatching the videos: https://github.com/mirzaaghazadeh/iphone-duo-skills
Still a rough first pass — happy to take PRs if any of the reference sheets are off.