Post

I was job hunting recently, and one thing kept surprising me how many teams still build interactive prototypes in Figma. It became an early flag to watch out for in identifying teams that wouldn't be a good fit.

The friction to me came from how Figma gives you a dead artifact. It looks right, but it doesn't do anything and then someone has to translate the whole thing into code before it's real. That's just duplicating the work needed to ship.

The line between design and engineering has collapsed, and the designers who can express ideas in the medium they ship in are going to run circles around the ones tossing static files over a wall.

I'm not anti-Figma, to be clear. As a canvas for early scoping and exploring a vibe, it's great. That's the job it's actually good at for my own workflow, although Magicpath is starting to be my go-to for vibing in a canvas environment.

The problem is interactive demos. The second you prototype interaction in Figma, you're either doing the work twice or fighting messy cross-platform syncing to keep design and code from drifting apart, and fighting with their MCP tends to create more problems than progress.