Designers are shipping code now
The tools changed, and the handoff is next
Designers are shipping code now. Not “learning to code” in the old sense, where you’d spend six months on freeCodeCamp and still not build anything real. This is different.
At Intercom, every designer ships directly to production. One of their designers spotted a line-height issue on the messenger buttons and fixed it himself. Took less time than writing a Jira ticket to explain the problem to an engineer. At LinkedIn, Tomer Cohen killed their Associate Product Manager program and replaced it with an Associate Product Builder program, where people learn coding, design, and PM together. Designers there push actual pull requests.
A CollabSoft survey found that 68% of designers think they should know how to code. But here’s the part that stuck with me: 91% of developers said designers should code. Developers want this more than designers do.
The tools are what changed
Figma keeps inching toward code. At Config 2025 they announced Figma Make, which turns prompts or Figma files into working apps. They launched Figma Sites so designers can publish websites without leaving the tool. Their MCP server connects Figma context straight to code editors. Two-thirds of Figma’s 13 million monthly users aren’t even designers anymore. The tool crossed over a while ago.
And then AI blew the door open. Benhur Senabathi wrote about building 15 working prototypes with Claude Code and Cursor, and shipping 3 real apps in 2025 with basic Swift knowledge. Another designer he mentioned shipped production frontend in one week using Windsurf. Built reusable components, handled the UI, passed off code ready to plug into the backend. A week. From a designer.
The money follows
You can see it in the funding too. Framer raised $100 million at a $2 billion valuation. 40% of YC’s latest batch uses it. Lovable went from zero to $200 million ARR in 12 months. Bolt.new generated over a million websites in five months. People are building things, and they’re not all engineers.
The handoff is dying
The old workflow: designer makes mockup, writes specs, hands off to engineer, engineer interprets specs wrong, designer files QA bugs, two weeks gone. That whole cycle is getting shorter or disappearing entirely. 91% of developers and 92% of designers say the handoff process needs work. When you can fix a button’s padding in the codebase faster than you can document it in Figma, the handoff stops making sense.
What stays human
This doesn’t mean design is turning into engineering though. The mechanical stuff, the pixel-pushing, component assembly, handoff docs, that’s what’s getting automated. What’s left is the hard part. Knowing which of three variations actually solves the problem. Thinking through what happens downstream. Making trade-offs with incomplete information.
Nielsen Norman Group said it plainly: if you’re just assembling components from a design system, AI can do that. What it can’t do is have taste, or the kind of judgment that comes from watching real people struggle with your product.
I’ve been on both sides. I designed products at Wolt and Yousician for years, and now I build my own app with Claude Code and Cursor. A year ago I would’ve needed an engineer to ship what I can do in an afternoon. That’s not an exaggeration, it’s just what the tools allow now.
The “should designers code” debate is done. It’s been done for a while. The only question left is whether you’re going to pick up the tools or wait until everyone else already has.