Articles

“Organization admins at companies using Governance+ for Figma Enterprise can now prevent users with view-only access from copying, saving, or exporting files. These controls can be applied to guest viewers or to all viewers, and can be configured at the organization or workspace level to align with your data-sharing policies.”

Bloomberg: ​“Figma may ultimately be able to secure a valuation multiple of more than 20 times its annual revenue, said Matt Kennedy, Renaissance Capital’s senior strategist. With 13 million monthly active users, Figma generated $821 million of revenue in the 12 months ended March 31 and would top $1 billion of annual revenue this year at its current growth rate.”

Figma Sites now supports apex (top-level, like exam​ple​.com) domains and custom subdomains (like yourname.figma.site) so that you have more options for personalizing your URL.

Jenny Wen, previously a Director of Design at Figma and now a design lead at Anthropic: ​“The way I’ve seen great work made isn’t using any sort of design process. It’s skipping steps when we deem them unnecessary. It’s doing them out of order just for the heck of it. It’s backtracking when we’re unsatisfied. It’s changing things after we’ve handed off the design. It’s starting from the solution first. It’s operating on vibes and intuition. It’s making something just for the sake of making people smile. It’s a feeling that we nailed it. It’s knowing how to bend the process in your favor. It’s the sense to know how to keep making your work better. And it’s a clear, unwavering ideal of what good looks like.”

Ridd recorded an entire new video influenced by her article.

Eric Bailey: ​“Like cicadas emerging from the ground, design industry conversations about quality seem to periodically erupt on social media. Also like cicadas, these articles are as predictable as they are irritating.”

A thoughtful essay by Ink & Switch on restoring user agency in a world of locked-down apps: ​“In this essay, we envision malleable software: tools that users can reshape with minimal friction to suit their unique needs. Modification becomes routine, not exceptional. Adaptation happens at the point of use, not through engineering teams at distant corporations.”

“From giant inflatable glyphs to welcoming soundscapes, Figma’s Brand Studio designed an immersive conference that celebrated the spirit of makership at every turn.”

Lots of fascinating details that were not shared publicly before. Figma’s last 12 months (LTM) revenue is $821M, so most likely they will cross $1B in revenue in 2025. Maintaining 46% YoY revenue growth at this scale is nuts. 76% of customers use 2 or more products, and ²⁄₃ of users are non-designers — Figma is no longer just a design tool. The entire form is hundreds of pages long, so it will take a while to read in full.

Figma’s Form S‑1 submitted to the SEC in April is now available to the public. The number of shares to be offered and the price range for the proposed offering have not yet been determined.

Software engineers Darragh Burke and Alex Kern share the story behind the creation of code layers to bring design and code together. ​“Building code layers in Figma required us to reconcile two different models of thinking about software: design and code. Today, Figma’s visual canvas is an open-ended, flexible environment that enables users to rapidly iterate on designs. Code unlocks further capabilities, but it’s more structured — it requires hierarchical organization and precise syntax. To reconcile these two models, we needed to create a hybrid approach that honored the rapid, exploratory nature of design while unlocking the full capabilities of code.”

“We built code layers—interactive elements backed by custom React code—in Figma Sites to help you experiment with interaction and motion without additional technical knowledge or outside help. Whether you’re creating an element from scratch or riffing on an existing design, code layers allow you to add dynamic functionality to your site—from flyouts and dropdowns to shaders and maps—by converting components to code layers, chatting with AI to build and tweak them, or editing directly in Figma’s code composer. And, you can generate multiple code layer variations to compare your ideas side-by-side and experiment freely—all in the Figma canvas.”

Hardik Pandya with a thoughtful critique: ​“When Apple places interface elements behind a glassy refractive layer and claims this brings content closer, it contradicts our lived experience with glass as a material. The iPhone’s most powerful feature has always been direct manipulation — the sense that you are touching your photos, sliding your messages, and tapping your apps directly. There is no separation layer. There is no glass between you and your content, because the screen itself disappears during interaction.”

Figma acquired Payload, an open-source Next.js CMS. James Mikrut, founder of Payload: ​“Figma and Payload together can and will solve a problem that’s been bugging me (and probably all of you) for years. The gap between design and code still exists. Designers create in Figma, then devs recreate in code, then content teams struggle to maintain it all. It’s inefficient and frustrating. And historically, the CMS tends to make it worse. With Figma, we can (and will) solve these problems in new ways without compromising.”

Kris Rasmussen, CTO of Figma: ​“When we announced Figma Sites at Config, we shared that we’ll be rolling out a CMS for it in the months ahead. Figma CMS will make life easier for marketers and designers who need to update website content, and Payload brings all the stuff developers love—a powerful, customizable backend for building scalable websites and apps, plus an intuitive admin panel for editors. By teaming up with Payload, we’re creating something special.”

This is huge! A few months ago, I wanted to use Framer for a marketing website but ended up recommending building a custom website only because its CMS was so lacking. When Figma announced that Figma Sites CMS is ​“coming soon”, I expected something just as barebones in the beginning. Getting a proper CMS in addition to code layers and Figma Make components makes Sites insanely customizable and powerful.

Apple updated HIG with all the latest design techniques.

Designer Advocate Alexia Danton shares the team’s favorite prompts, pro tips, and best practices for using Figma Make to help you get the most out of the recently launched prompt-to-code feature.

Elie Majorel shares the playbook of prototyping with AI tools, allowing other designers to spend less time on appearance and more time on impact. ​“One Sunday I opened Miro, sketched a few boxes for a new agent search, and copied the flow into Claude. Claude wrote a clear spec. I pasted that prompt into Lovable, pressed generate, and two hours later a working React repo ran in a sandbox. Engineers forked the code the week after. Leaders clicked the demo and said keep going. Two hours from idea to running product. No Figma layers. No endless handoff.”

Ruxandra Duru works with Google designers focusing on the intersection of color, emotion, and UX design. ​“After years of what we could call a color fixation, I’ve developed a three-step approach to color theory. My secret to making color more pleasurable and intentional — and much less scary — has to do with balancing, relating, and completing your colors.”

Robert Bye keeps sharing lessons he learned at Figma. In part 3, he talks about autonomy, creativity, collaboration, communication, and camaraderie which he saw at Figma’s most inspiring teams daily. ​“Before joining Figma, I experienced far too many teams riddled with people playing politics, jockeying for credit, and optimising for performance reviews. Thankfully, that culture was refreshingly rare at Figma. Instead, most folks genuinely enjoyed collaborating, celebrated each other’s wins, and championed each other’s successes. Whether it was PMs ensuring designers presented their own work to leadership or team leads publicly praising IC engineers for fixing gnarly bugs, ego-free collaboration was consistently modelled.”

Figma announced the beta release of the Dev Mode MCP server, which brings it directly into the developer workflow to help LLMs achieve design-informed code generation. Jake Albaugh shared a sneak peek at the GitHub × Figma Dev community event during Config, and I’m excited to finally give it a try.

“[MCP server] allows developers to bring context from Figma into agentic coding tools like Copilot in VS Code, Cursor, Windsurf, and Claude Code. Whether it’s creating new atomic components with the proper variables and stylings or building out multi-layer application flows, we believe this server will provide a more efficient and accurate design-to-code workflow.”

“If you’ve already invested in a design system and leverage patterns like components, variables, and styles that are aligned between design and code, the Dev Mode MCP server is a multiplier — we want to make sure that the LLM can benefit from these patterns, too. Agentic search techniques can take quite a bit of time to locate the right patterns, especially in large codebases. They may also find valid patterns that stray from those referenced in a design. By providing references to specific variables, components, and styles, the Dev Mode MCP server can make generated code more precise, efficient, and reduce LLM token usage. […] If Figma knows which components you’re using, it can share the exact path to the code file the agent needs with Code Connect.”