Map behavior
Document the states, decisions, and transitions users should be able to understand.
[ SYSTEMS ]
I design product behavior as a coherent system, then shape visuals around that logic.
The process starts with structure: interaction maps, motion hierarchy, and mathematical rules for spatial change. Aesthetic decisions follow system intent, resulting in interfaces that feel alive but controlled.
Encode rules
Translate those expectations into motion hierarchy, layout constraints, and runtime contracts.
Tune feel
Shape the visual system so the interface feels alive without becoming ambiguous or noisy.
[ Motion Language ]
Camera-led transitions
Depth and camera movement communicate hierarchy and context better than decorative effects. Motion is paced to help users reason about change.
[ Visual Logic ]
Deterministic geometry
Procedural forms are generated by explicit constraints, not visual noise. That gives repeatability, performance predictability, and consistent product identity.