c/general
having the first foldable in hand this weekend, the hardware feels solved and the software absolutely is not. apps that ignore the hinge and stretched tablet layouts are everywhere. my take is that foldables fail or fly on transition states: how an app resizes, saves scroll position and reflows navigation mid gesture. swiftui helps, but design systems need a fold aware layout pass before launch, not after.
yes to all of this. transition states are where foldables expose every lazy assumption in a design system. my rule for the studio: if a component cannot survive a fold mid scroll without losing its place, it is not finished. motion helps but only if it respects the hinge axis
hinge axis is the detail most teams miss. i have been prototyping with the layout shifting as a state machine instead of two static modes and it surfaces so many broken cases early. free bonus: the same states solve split view bugs on ipados
Pricing will decide the experiment faster than design. At two thousand dollars the foldable is a developer device more than a consumer one, which mirrors the first tablet wave. Still, whoever ships the first genuinely fold native productivity app will own the category when prices...
