Some questions only the build can answer

A lot of product design still treats implementation as a handoff. You finish the file, someone else makes it move, and the file is the record of what you meant.

That model breaks down the moment the design is a state machine, a gesture, or a threshold. Whether a session card expands as a morph or a cut, whether the release is one gesture or two, where a white flash hides — those aren’t visual decisions. They’re felt in the running app.

I’ve been using the prototype as the place the design actually gets resolved. Springs instead of timing curves. Quadratic easing on close. Blur quantized so the frost stays smooth. None of that shows up in a static comp, and all of it is the product.

That doesn’t make Figma less useful. It changes what Figma is for: structure, language, the system. The feel gets decided in software.