You might have seen a lot of angry posts on LinkedIn lately.

Figma Sites? Poor accessibility, they say.

Buzz? A Canva clone in disguise.

Dev Mode? A dangerous oversimplification.

Figma Make? More shiny features, less focus on users.

‍

They claim it’s the end of design. That Figma is killing Webflow. That Adobe has infected the product with its all-in-one virus. That it’s chaos wrapped in a shiny UI.
But if you only see that; you’re missing the point.
Because under the noise, there’s something huge happening. Something we’ve been craving for years:
‍

Let us do our job. And let us do it well.

Because product designers aren’t illustrators or decorators. We’re systems thinkers, problem solvers, engineers of experience.
Because developers shouldn’t have to guess what to build.
Because marketers and product managers should work hand in hand with UX researchers, not playing catch-up 3 sprints later.
Figma 2025 is not perfect, but it’s not noise. It’s signal.

‍

Dev Mode: real alignment between design and code

Dev Mode gives developers a dedicated interface to inspect design files - with live access to CSS, code snippets, variables, and design tokens. It links directly to the codebase via Code Connect, bridging design and development like never before.

No back-and-forth. No guesswork. Just clarity.

And designers? They need to speak code without writing it. Think in tokens. Structure in components. Design in systems. Everything reusable. Everything aligned.Figma now nudges you toward good practice: if your button uses the Primary/Blue-600 token, the dev sees it instantly. No more hex codes in the wild.

‍

If you’ve got a solid design system and the right people (ours is Alicia, she’s a legend), Dev Mode unlocks efficiency of the team:

• Design are free from unending annotations
• Devs stop guessing
• No more ambiguity, everyone speaks the same language
  ‍

It’s not just about handoff. It’s about real-time, side-by-side creation. A designer polishing UI. A dev checking token mappings. Same file. Same source of truth. That old wall between design and dev? Gone.

‍

Figma Make: logic without the dev dependency

Figma Make lets you describe interactions in plain English… and turns them into functional prototypes. Want a modal to appear on click? Type it. Make does the wiring.

Yes, it’s still awkward. No, it’s not ready. But the idea is brilliant.
It lets product designers test logic inside the design file - before writing a single line of code.
It’s not about replacing developers. It’s about unblocking exploration.
Let the PM try a flow. Let the designer simulate conditions. Let us fail faster and smarter.

‍

Figma Sites: from design to deployment, in context

Figma Sites is still in beta, but the promise is bold: publish real websites directly from your Figma designs. Responsive layouts, built-in grids, content editing, and interactivity included.

‍

No more "Figma to Webflow" plugins. No more mismatches between mockup and live.
Accessibility? Still patchy. SEO? Needs work. But it’s a shift.
Now designers can ship. And iterate. Inside the same tool.

‍

Figma Draw: real creativity meets real constraints

Figma Draw adds expressive drawing tools inside your design canvas. Think sketching, doodling, illustrating - all directly within Figma.
‍

Before? We had to bounce to Illustrator for creative work.
Now? We stay in one space. Draw mode respects components, layout, and constraints. And yes - it’s dev-reusable.
A fluid space to explore ideas, with the structure to ship them.

‍

Buzz: the end of comma-fueled export hell

Figma Buzz lets teams generate visuals from locked templates based on your design system. That means marketing can tweak content, resize assets, and build variants - without touching a pixel.

‍

We’re tired of re-exporting banners because someone forgot a comma. Tired of updating 20 formats because a CTA changed. Tired of ping-pong.
Buzz stops the nonsense. It lets non-designers create - safely.
And designers get to do what they do best: systems, not specs.

‍
New tools, new questions

When everyone can publish, who’s accountable?
When files are shared across disciplines, who owns what?The lines are blurrier, but not gone.
‍New roles emerge: DesignOps, creative devs, brand guardians, systems owners.
We see teams setting up permissions, review loops, branching strategies. A new kind of collaboration that’s more open but also more disciplined!

Now a growth PM can ship a landing page without waiting on dev. A content lead can launch a seasonal campaign without pinging a designer for every variant.
Of course, they’re not starting from scratch: they’re working within templates, tokens, systems set up by the design team.

Designers shift from builders to enablers. From pixel-pushers to systems thinkers. They create the structure. They set the rules. And they trust the team to play inside the sandbox.

Developers become the tech guardians: validating what’s published, ensuring performance, accessibility, and SEO are all in check. PMs and marketers become faster, freer, but also, more responsible.

‍

What it means for our clients

At Outsight Studio, we already work this way.
‍
Mixed teams. Live collaboration. Clients navigating prototypes before the first line of code is written. These new tools just make our work more fluid, more connected.
‍
But they also raise the bar. Fluid roles mean clearer systems. Faster decisions mean better alignment. Tools give power… and demand responsibility.
‍
We help our partners build product teams that are ready for this new world. More versatile. More integrated. Less siloed. And always anchored in what matters most: the experience people live.
‍

And hey! We also had the joy of co-organizing the   Config 2025 Watch Party in Brussels
‍at Google Digital Atelier; connecting 80+ designers, developers, PMs, and curious minds to celebrate these paradigm-shifting updates in real time.

‍

There was critique. There was doubt. There was excitement.
Because whether you love or hate these updates: they matter.
Figma isn’t trying to be an all-in-one monster. It’s trying to help us work better, together.
To empower every role, clarify the mess, and reconnect us to what matters: the user.
Let’s not waste that.