UX Tools Survey · Spring 2026
State of Prototyping:
Spring 2026
The most-used design tool after Figma is now an AI.
The profession split into three camps, and most people haven't noticed yet.
We surveyed 1,478 designers and builders across 18 regions on how they actually work right now. What they use every week. How much they're vibe coding. Whether they trust AI to ship. And what they're investing in next.
This is an open data project. The full de-identified dataset is available under CC BY 4.0. You can download the raw data, query it through the open API, or connect it to your AI tools via the MCP server.
Spring 2026 Sponsors
This survey was independently run by Tommy Geoco and UX Tools. This report exists as a free, open dataset because these sponsors believed in making design research accessible to everyone.
Stop screenshotting apps. Browse the largest curated library of real product UI - search by flow, pattern, or screen.
Ship real sites without writing code. Full design freedom, built-in CMS, and the performance your clients actually need.
Describe what you want, get clickable prototypes on an infinite canvas. Design and code in one place.
Run user research from recruit to insight - video diaries, interviews, and surveys in one AI-powered platform.
AI prototyping that matches your existing product. Import your design system, generate on-brand UI, export to Figma or code.
Dazl is the AI platform that takes your product from ideation to hand-off. Visually edit and collaborate with your team in real time at every step of the product journey.
1. Who took this survey
State of Prototyping is part of our ongoing survey initiative to understand how design and software are changing. This Spring 2026 edition is the first snapshot, built for designers and builders who work across the design-to-code spectrum.
61.4% of respondents are outside North America. Western Europe (16.2%), South Asia (8.1%), and Southeast Asia (3.8%) are the largest non-NA regions. This is a global sample.
2. The stack right now
Five of the ten most-used weekly tools are now AI. That sentence did not make sense two years ago.
Figma holds its seat. But Claude, ChatGPT, Claude Code, Figma Make, and Gemini now sit alongside it in the weekly rotation. The traditional design tool stack has been restructured from the inside.
Editor's note
An AI coding terminal is now more embedded in designer workflows than any canvas-first tool. That shift happened quietly, and it happened fast.
3. The vibe coding split
This was the centerpiece question: how much of your building time is actually vibe coding, using AI to generate code you may not fully understand, but that works?
The profession split into thirds.
43.8% spend more than half their time vibe coding. 31.1% say it's most or nearly all of how they build. And 37.7% do zero.
The hype has outpaced adoption at the tail, but the more surprising number is the 37.7% who haven't started. Not “a little.” Zero.
Editor's note
37.7% of designers do zero vibe coding. 31.1% say it's most or all of how they build. These are not different generations. They work in the same orgs, on the same products, in the same Slack channels.
4. Vibe coding by role
Same profession. Different reality.
The vibe coding split is not random. It maps almost perfectly to role type.
The managers-at-46.6% number is telling. Vibe coding didn't just serve engineers. It gave managers and non-designers an exit from prototyping constraints they've always had.
5. Who's building their own tools
More than half of designers are now builders. Not for their company. For themselves.
59.1% of designers have built their own tool, app, or utility with AI in the last 6 months. One in four does it regularly.
That number would have been in the low single digits two years ago. The ability to build something for yourself, not a product, just a thing that solves your own problem, has unlocked a new kind of creative leverage.
59.1% have built something. 30.5% want to but haven't yet. Only 10.4% have no plans to.
The intent-to-try cohort is bigger than the never-will cohort by 3x. The builder instinct is spreading across the design org.
6. The trust line
Nearly 1 in 3 designers trust AI output for production with review. That is a bigger number than most people would have guessed.
Only 1.4% trust it without any oversight. But 32.8% trust it enough to ship, with a review pass. We are in the “first drafts I heavily edit” era. The trust line is not whether AI works. It is how much cleanup it takes before it is usable.
7. What's blocking everyone
The #1 thing blocking designers from AI isn't the quality of the output. It's time.
The top 3 blockers are within 3.5 percentage points of each other: time to learn tools (55.7%), too many tools to evaluate (53.0%), and AI output quality (52.2%). That's not noise. That's signal. Three simultaneous problems, nearly identical in size.
The industry built a hundred AI tools and forgot to give anyone time to learn them. The blocker isn't capability. It's bandwidth.
8. How workflows changed in 6 months
71.1% have added AI or gone AI-central in the last 6 months. Only 9.9% say “mostly the same.”
The shift already happened. The question is how far you've gone.
The gap is 4.1 points. Much narrower than most people expect.
9. How designers feel about their role
Your confidence tracks with your seat. And the gap between the most optimistic and most anxious groups is the sharpest finding in this survey.
Same industry. Same wave of change. Opposite experience.
Editor's note
IC designers and researchers are the most exposed. They are also the largest groups in most design orgs. If your org isn't talking about this openly, it's not because the problem isn't there. It's because no one wants to say it first.
10. Where designers are investing next
Two of the top 3 investment areas are AI. Design systems is the only holdout in the top tier, and that's not an accident.
64.0% say AI-assisted coding is their top investment. Agent workflows at 46.3%. Design systems at 40.2%.
Systems work is how you stay relevant when the output layer gets automated. The designers investing in systems aren't ignoring AI. They're building the layer AI can't replace yet.
11. The satisfaction gap
1.5 points separate the floor from the ceiling. Both are people with the same job title. The difference is how much of their workflow runs on AI.
No vibe coding: 5.93/10. Heavy vibe coders: 7.39/10. The satisfaction gradient is nearly linear across adoption levels.
This is not proof that vibe coding causes satisfaction. Cross-sectional surveys can't prove causation. People who adopt new tools faster may also be more satisfied by temperament. But the correlation is strong enough, and linear enough, that dismissing it requires an explanation too.
12. The story in summary
Six findings that capture what this data actually says.
1. Claude is the #2 weekly tool in design, after Figma.
50.8% of designers use it every week. Claude Code sits at #4, ahead of FigJam. An AI terminal outranks every canvas-first and collaboration tool in the stack.
2. The profession split into thirds, and they barely recognize each other.
No vibe coding: 37.7%. Some: 18.5%. Majority AI-generated code: 43.8%. Design engineers at 80.9% vs. IC designers at 35.0%.
3. More than half of designers are building for themselves.
59.1% have built their own tool with AI in the last 6 months. One in four does it regularly. Only 10.4% have no plans to.
4. The biggest blocker isn’t AI quality. It’s time.
Time to learn tools (55.7%), Too many tools (53.0%), and AI output quality (52.2%) are within 3.5 points. The industry shipped a hundred tools and forgot to give anyone time to learn them.
5. Design engineers feel more valuable. Researchers feel most at risk.
Design Engineer: 50.0% more valuable, 10.6% less secure. Researcher: 17.4% more valuable, 39.1% less secure. Same industry. Opposite experience.
6. Vibe coders are measurably more satisfied.
No vibe coding: 5.93/10. Heavy vibe coders: 7.39/10. The gradient is nearly linear. Correlation, not causation, but strong enough to take seriously.
If this is you
If you're a design engineer:
You're in the most optimistic seat in the industry right now. 80.9% of your peers are majority vibe coding. Your investment in code + AI fluency is paying off. The data says: keep going.
If you're an IC designer:
35.0% of your peers are majority vibe coding, which means 65% aren't. You're not behind. But the gap between you and design engineers is the widest split in the data. The question is whether you want to close it.
If you're a manager:
46.6% of managers are vibe coding. You're not watching from the sidelines anymore. The blocker data says your team needs time, not more tools. Protect their learning bandwidth.
If you're a researcher:
This data is hard to read. 39.1% of researchers feel less secure. That's the highest anxiety in any role. But 17.4% feel more valuable, which means the path exists. The researchers who are thriving are the ones integrating AI into their practice, not waiting for permission.
Methodology
The State of Prototyping Spring 2026 survey ran from March 14 to April 6, 2026 and collected 1,478 responses from designers and builders across 18 world regions. Distribution was via UX Tools newsletter, social channels, and sponsor networks.
Published charts use aggregated data, and the full de-identified microdata is also available for download. One malformed role response in the raw CSV is excluded from role-based breakdown tables. The “Researcher” role (n=23) should be treated as directional only due to small sample size. Region breakdowns use n=1476 because two respondents did not provide a region. Multi-select questions sum to more than 100%. Cross-tab percentages are calculated within each role's n.
The full dataset is available under CC BY 4.0. Citation: UX Tools. (2026). State of Prototyping Spring 2026. https://survey.uxtools.co.
Have a question about the methodology? Want to run your own analysis? The full dataset and API are open. Prove us wrong.