Design process

Why great design still starts in Figma (most of the time)

While AI and code-first approaches are on the rise, design tools remain essential for collaboration and iteration. However, not every project requires a design process. Here’s when Figma is worth it—and when jumping straight into code makes sense.
Jess Eddy 9 min read
Why great design still starts in Figma (most of the time)

Figma is essential in UI/UX design

Coding-first approaches also have their role.

We’re in the era of very hot takes on design—where, in an attempt to feed the algorithm, rack up likes, or sell courses, people are making bold, attention-grabbing claims about design, tooling, and the industry. Lately, the target has been Figma: “Figma is dead.” “There’s no reason to use Figma anymore.”

These short-sighted statements lack context and nuance, two qualities that make for meaningful discussions but seem to be in short supply these days.

If you’ve been reading everyday ux for a while, you know I’m all for designers using AI tools to code—no surprises there, but replacing design tools entirely with AI? We’re just not there yet.

AI tools are creating new opportunities and leveling the playing field for designers
AI coding assistants and no-code platforms unlock new opportunities for designers, making it easier to experiment, prototype, and step into technical roles. As design becomes a key differentiator in a crowded market, now is the perfect time for designers to expand their horizons and skills.
How o3 is shaping the future of work: opportunities for designers and beyond
o3, the latest iteration from OpenAI, builds on the success of earlier GPT models, with enhanced reasoning, coding, and problem-solving capabilities that are poised to transform design.

That said, we shouldn’t cling to tools or processes just because they’re familiar. Technology moves fast, and part of being a great designer is knowing when something has become outdated—or when a new approach is worth exploring.

The points in this article aren’t rules—they’re ideas and advice. The best way to find what works for you is to experiment. Try new things, challenge assumptions, and see for yourself.

There’s a time and place for code, and there’s a time and place for design tools.

I use Figma as the example in this article, but while it may be the industry leader, it’s not the only option. If you use something else, swap Figma out for your tool of choice—the point still stands.

With AI-generated code on the rise and more teams shifting toward code-first approaches, some argue that Figma is becoming obsolete. However, Figma remains a crucial tool for product design, especially when working with teams, defining new experiences, and maintaining alignment.

At the same time, design tools must evolve to stay relevant. The demand to go straight from Figma designs to production-ready code is growing fast, and the pressure to streamline this process is shaping the future of design tooling. New integrations, AI-powered automation, and developer-focused workflows are all pushing Figma—and other design tools—to bridge the gap between design and code more seamlessly than ever.


Here’s why design tools matter

Read the full story

Sign up now to read the full story and get access to all posts for subscribers only.

Subscribe
Already have an account? Sign in

Receive updates

Get updates delivered straight to your inbox, once every two weeks.

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to everyday ux.

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.