When Design Tools Become Development Platforms
Figma started as a browser-based alternative to Sketch. That positioning – lighter, collaborative, accessible without a Mac – was enough to pull designers away from Adobe’s orbit. But the company’s latest AI features are doing something more aggressive: they are making the gap between design mockup and shipped product narrow enough that entire job functions are starting to overlap. That is not a feature update. That is a market boundary question.
Adobe has spent decades building a creative ecosystem where each tool feeds into the next – Photoshop into Illustrator into InDesign into Premiere. The logic was that switching costs would keep professionals inside the suite indefinitely. Figma’s AI push is now targeting exactly that logic, not by replicating Adobe’s tools, but by making the design-to-production pipeline so fast that Adobe’s upstream tools become optional rather than essential.
What Figma’s AI Actually Does
Figma’s AI feature set, rolled out in stages through its Config conference updates, centers on a few capabilities that sound incremental until you watch them work. Auto-layout generation, AI-assisted component suggestions, and the ability to turn rough wireframes into polished UI elements are each useful on their own. Together, they compress what used to be a multi-hour design iteration cycle into something closer to a real-time conversation between the designer and the canvas.
The more pointed feature is Figma’s move into AI-generated design assets from text prompts. A designer can describe a UI state – a loading screen, an error message, a product card – and Figma will generate a design-ready version within the existing design system. This is where Adobe Stock, Adobe Firefly, and even Photoshop’s generative fill start to feel like parallel tools solving the same problem from a different entry point. When the generation happens inside Figma, where the actual production files live, the pull to jump to Adobe’s ecosystem weakens.
Figma also introduced Dev Mode, which translates design files directly into developer-readable specifications, CSS values, and even code snippets. That single feature collapses a handoff process that used to require Zeplin, InVision, or manual documentation. Adobe’s XD tried to solve this handoff problem and never gained enough traction to matter. Figma is solving it by building the bridge directly into a tool designers already use every day, which removes the persuasion problem entirely.
The compounding effect is what makes this more than a product story. Each AI feature Figma adds reduces one more reason to open a separate application. Removing friction is how tools win long-term adoption – not through feature superiority on any single dimension, but by making the alternative feel unnecessarily complicated by comparison.
Adobe’s Response and Its Limits
Adobe is not standing still. Firefly, its generative AI model, is genuinely capable – and it carries one advantage Figma cannot easily replicate, which is training on licensed content. Adobe’s pitch to risk-averse enterprise and agency clients is that Firefly-generated assets are commercially safe in a way that other AI image generators may not be. That matters in legal and regulated industries where IP provenance is scrutinized.
The problem is that this argument wins procurement conversations, not creative workflow decisions. Individual designers and small teams are not evaluating tools through legal compliance frameworks. They are evaluating tools by how fast they can move. And Figma’s AI integrations live directly inside the workflow rather than as a separate generation tool that requires asset downloading, format conversion, and re-importing. Adobe’s Creative Cloud integration story is improving, but the file-shuffling overhead is still real.
Who Feels This First
Product design teams at technology companies are the most immediate audience. They were already Figma-native, and Figma’s AI features deepen that commitment by reducing the need to pull in external tools for asset creation or prototyping. Marketing teams at those same companies, who historically lived in Adobe tools for print, social, and video assets, are a different question – Figma’s AI has not yet meaningfully addressed video or print production, which keeps Adobe’s Premiere and InDesign relevant.
Freelancers are a clearer case. A freelance UI/UX designer who can now handle asset generation, prototype production, and developer handoff inside Figma has little reason to maintain an Adobe Creative Cloud subscription that runs well over $50 per month. The economic math is simple even before the workflow argument kicks in. A growing number of solo designers are reporting – on forums, in design community newsletters – that their Adobe usage has dropped to Photoshop alone, and even that feels like a habit more than a necessity.
The Longer Strategic Pressure
The harder question for Adobe is where its creative suite sits in a world where AI generation is the primary source of raw visual material. Adobe built its dominance on the idea that creative professionals needed powerful manual editing tools because creating and editing images was technically demanding. AI generation does not eliminate editing, but it fundamentally changes what the editing is for. You are no longer correcting a photograph or cleaning up a vector – you are steering an output that was already 80% of the way there. That changes the kind of power a tool needs to offer.
Figma, by embedding generation into a collaboration-first, browser-native environment, is betting that the next generation of creative work happens in the browser, in real time, with teams. Adobe’s architecture – desktop-heavy, file-centric, subscription-stacked – is being retrofitted to fit that world rather than built for it. Retrofitting is slow. Figma’s advantage is not just AI capability; it is that AI features feel native to the tool rather than bolted on.
What keeps this tension unresolved is that Adobe’s installed base is enormous and institutionally sticky. Universities teach Photoshop. Agency workflows are built around InDesign. Video production pipelines depend on Premiere and After Effects. Figma’s AI is winning the design-to-development corridor, but the broader creative suite is a much larger geography. The question is whether Figma’s trajectory eventually points toward video, print, and motion – and whether Adobe can afford to wait and see before that answer becomes obvious.
