Designers who code will always win

When I switched from Figma to code, everything about my workflow got better. Here's why.

1. Design tools always lag behind

Every design tool is a technology wrapper. Building that wrapper takes time, so design tools always trail years behind what's possible in the browser. You can't do innovative design if you fall that far behind.

FeatureReleasedAvailable in Figma
CSS flex-wrap20092023
CSS media queries20102023
CSS variables20122023

AI won't fix this. Figma is a large company with a massive user base. Every change gets debated, tested, and rolled out slowly. Innovation moves at the speed of bureaucracy.

Frontend is different. Solo developers build widely used libraries from scratch. And AI makes this even faster. The gap isn't closing. It's widening.

2. You and developers speak different languages

The lag creates a real communication problem. Designers reinvent solutions that developers stopped using years ago, while developers work with modern open-source libraries designers have never heard of.

Designers talk about "auto-layout" and "hug content." Developers talk about flex containers. Same thing, different words. When you know both, collaboration gets easier.

3. Vendor lock-in

Most design tools use proprietary file formats. You can't easily move your work between tools, and sometimes you can't even open files from a few years ago.

Code is universal — standard formats that stay readable and editable forever. When Cursor came out, I opened my projects directly — no export, no conversion. Compare that to the Sketch to Figma migration.

4. Figma prototypes don't feel real

Figma prototypes are presentation slides with hotspots. Code gives you actual drag-and-drop, real data, and complex interactions — things Figma simply can't do.

5. Figma lacks proper version control

Code has Git. Branch, merge, revert, collaborate — tried and tested for decades. Figma's versioning is limited to saved snapshots, which falls apart on large projects.

In Figma, you can't prototype the entire product — only isolated flows. With code, building a fully interactive product prototype is realistic.

6. Your data isn't even yours

Storing unreleased product designs on someone else's server is a risk. Code lets you keep everything local, private, and under your control.

    Designers who code will always win