State of AI Assisted Design
Our opinion on the current state of AI-assisted design. Author - Amarneethi Ranganathan
Info
Everything below is my opinion based on my experience building with AI. I don't claim to have all the answers — this is what I've observed so far.
What I've built
I have developed multiple prototypes and some production applications with AI. This site — the learn section, the blog section — was built entirely with AI without touching Figma for any of the UI design. I have also developed CRM applications, a mobile app, an MVP of a design tool like Figma all without using Figma.
Design systems in code make AI shine
Code and screen generation for design purposes works best when you have a design system in code. Without one, AI produces inconsistent output that becomes impossible to maintain or handoff in the near term and long term. With one, it produces output that's consistent and on-brand. This is the single biggest lever for getting good design work out of AI. Of course this means, you need to learn to read and modify code to get the best results.
Figma becomes optional
Figma becomes optional in most cases once you learn a bit of code. We're not saying learn to be a software engineer — we're saying learn enough to read, modify, and prompt effectively.
Imagine a roadmap of about a year, spending 8–10 hours a week. Preferably spread out over 3 or 4 days a week rather than one long session. I've found that retaining what you learn works best when you code or learn code every day or every 2 days, instead of cramming 8+ hours into a single weekly session. I don't have research to back this up — this is purely from personal experience.
Code to Figma is still manual
Making code into a design system compatible design in Figma is a fully manual process. I have not come across anything that genuinely automates this. Even if some tool claims to automate it, I'm skeptical of those claims. The fidelity required for a proper Figma design system — with variants, auto-layout constraints, component properties, and documentation — is far beyond what any code-to-Figma tool handles today.
The future of design roles
My long-term prediction is that designers will have to learn to code to continue with their career, we understand this is a harsh reality. Alternatively, developers who build an understanding of design and UX principles will take on work that was traditionally done by designers. There are and have been great talent in this front who have been successful by being a designer and developer. The tools are accelerating learning skills, and the people who take advantage of them will have the edge.
One niche we believe will endure is the UX consultant — someone whose job is not producing outputs or artifacts, but applying deeply learned UX principles to deliver business outcomes. If your value is in the thinking and the strategy rather than the production of screens, AI doesn't replace you. It might even make you more effective.