Articles

Carly Ayres asks the Figma community to weigh in on Andrej Karpathy’s ​“vibe coding.” ​“Perhaps the question isn’t whether vibe coding will replace traditional development—it won’t—but rather how it might expand who can build software and how we build it.”

Creators can now add structured tags to boost visibility and make it easier for you to find the right templates, UI kits, or design assets in Figma.

“There’s a lot of buzz about AI agents. Robots that do more with less supervision—what could go wrong? We asked our community how this might shake up how we think about UX.”

A first look at who’ll be taking the stage at Config in San Francisco this May: Andrew ​“Boz” Bosworth, CTO at Meta; Ebi Atawodi, Director of Product Management at YouTube Studio; Joel Lewenstein, Head of Product Design at Anthropic; Dr. Madeline Gannon; Karri Saarinen, Linear co-founder and CEO, and more.

“Behind every successful design system lies a surprising secret: numbers. Learn how tracking the right metrics can transform your design system from a helpful resource into a powerful engine for efficiency.”

Org and Enterprise customers can now find styles and variables data in their analytics reporting within Figma. This is in addition to the existing component data for a given library. Library Analytics API is out of beta and includes styles and variables data as well, but it’s only available to Enterprise customers.

When exporting a raster image (JPG, PNG, PDF), now you can choose an image resampling option. Image resampling helps maintain the quality of your exports by determining the color of each pixel. It’s useful when exporting images to different sizes or a vector design to a raster format.

The Detailed option (default) uses an image resampling method called ​“bicubic sampling.” This method looks at each pixel and uses a weighted average of at least four surrounding pixels from the original image for export. Best used when optimizing for detail in exports, such as high-quality images, vector art, and assets with gradients or drop shadows.

The Basic option uses an image resampling method known as ​“nearest neighbor sampling.” This method looks at pixels from the original image and finds the closest matching pixel to use for the export. Best used when optimizing for hard lines in assets or for assets that don’t need finer details, like icons, low-resolution images, and pixel art.

The Tinloof team compiled a wishlist of Figma features that would improve their daily workflows. It’s divided into two categories: must-have features that address fundamental workflow limitations and nice-to-have enhancements that add extra polish to an already excellent tool. (This post was published two months ago, and it’s great to see that a few points have already been addressed.)

Lewis Healey, Lead Designer at Atlassian Design Systems, looks ahead at the industry, the tools, and the people. His predictions: AI will integrate into delivery workflows, tooling will bridge the craft gap, aspirational design libraries will phase out, accessibility will be the default, and systems will become more streamlined.

Anima has been working on design-to-code tools since before the recent AI craze. A few months ago, they added support for shadcn/​ui components, which I tried last week on my current project designed with this library.

Unlike v0, they parse the Figma file and get a lot of details right. I was impressed with how accurately it selected shadcn/​ui components, even if layers weren’t explicitly named or instances were detached in the mockup. It becomes obvious that parsing a file is the right approach when different components look the same on the surface. For example, the trigger for opening a dropdown or date picker uses the same button, but they are different Figma components under the hood, and Anima chose their counterparts in code correctly.

Exporting custom colors and typography variables to a Tailwind config is also a nice touch. I ran into a few issues with excessive Tailwind styling and newer shadcn/​ui components like the Sidebar not being recognized, but overall, this clearly feels like the right direction.

Vercel shares best practices on importing your designs from Figma to v0 and working with shadcn/​ui. I was excited about this integration until I realized it simply exports the Figma frame as an image and passes it to v0’s AI vision. Information about Auto Layout, spacing, color tokens, and typography is not preserved from Figma but inferred from the image. That’s fine for rough prototypes, but there is a better way.

Adobe brings multiplayer to Photoshop desktop and web apps. Now, multiple creators can simultaneously access and edit documents from different computers. It’s about time!

The new Lovable and Builder​.io integration lets you turn Figma designs into full applications. Lovable is a full-stack AI software engineer and editing environment. It’s designed to let you quickly create and iterate on your projects so you can move from an idea to a real application, deployed live, without wrangling complex tools or environments. AI-Powered Figma to Code is Builder​.io​’s toolchain that leverages AI models to convert Figma designs into React, Vue, Svelte, Angular, HTML, etc code in real-time. It can even reuse your existing components in the output and use any styling library or system you need.

So, by using the integration, you can convert Figma mockups into code with Builder​.io and then open them in Lovable, where you can add new functionality or connect it to the real data from Supabase. Soon, you’ll be able to update your app in Lovable whenever designs change in Figma. AI will merge the design changes while keeping all your custom code intact. (Unrelated, this combo was most recommended in answers to this question about the best AI tool for turning designs into a website.)

If you’ve been waiting for more details to start planning your trip to Config 2025, now is the time. Azra Daniels, Director of Events at Figma, gives a first look at what the team is building for the community on both sides of the Atlantic. The conference will kick off on May 6 at Config Commons near Moscone Center in San Francisco, where you can grab the badge and meet other attendees. To avoid long registration lines, partner hotels will offer multiple check-in locations. 50+ sessions will take place in multiple tracks on May 7 and 8. The Maker Space will feature a dedicated stage where community leaders showcase their latest work. Config will continue in London the following week for a one-day event with 10 sessions.

After being at Figma from 2019 to early 2024 and seeing the company grow from less than 100 to over 1,500 employees, Software Engineer Andrew Chan wrote down some notes on what brought him to Figma and why he thinks it succeeded. He highlights two factors that created Figma’s ultimate moat — browser-first link sharing brought non-designers into the product, and their multiplayer technology was hard to copy for existing products like Adobe XD and Sketch: ​“I would guess that this was less of a ​“collaborative algorithms are really hard to implement” and more of a ​“existing products are really hard to make collaborative” problem: Framer moved to browser-based collaboration pretty successfully, but it did so by completely ditching its old product, while Figma-like design collaborative design tools created from scratch are pretty common these days.”

Another great point is on forming strong product opinions early on and crunching on them until they’re right: ​“One clear thing to me is that Figma’s astounding success in design was due in large part to the company identifying a gap in the design space and working on it essentially in secret for years. Folks like Rasmus and Sho formed strong opinions on nearly every aspect of the product-to-be, which we would spend the next few years realizing in fairly recognizable form. I will make this claim mostly without evidence, but suffice to say that many features like auto-layout and component variants had their bones laid out years in advance (although most newer features like variables were designed later AFAIK).”

First Round’s deep dive into how Figma Slides founding PM Mihika Kapoor transformed a hackathon project into one of Figma’s most anticipated launches.

Jake Albaugh talks about how modern browsers have evolved beyond what most design tools can do: ​“While many designers and developers have been working within familiar constraints, browsers have undergone a quiet revolution. The web now supports features like container queries, advanced scoping and inheritance, and responsiveness to user preference. It’s gotten much more sophisticated in terms of color, typography, dynamic units, layouts, and animation. Yet so many young designers and developers I talk to as a Developer Advocate at Figma aren’t aware of these possibilities. We’re still operating within old paradigms instead of pushing the boundaries of what the browser can do.”

Did you know that Figma’s cofounder Evan Wallace created a custom programming language Skew for their mobile rendering architecture? This story slipped my attention, but Andrew Chan wrote a fascinating look at some of its interesting features.

Jacob Miller from Figma ran a poll and discovered that ¹⁄₃ of designers misunderstand DPI. In this post, he explains the relationship between pixel count, DPI, and physical size.

Carly Ayres on the value of combining skills: ​“A design engineer can not only take an idea to a working prototype with little lost in translation, but can spot opportunities and constraints that might otherwise be missed. The emergence of roles like ​“design engineer” illustrates how intentional (or unintentional) skill-building can create rare resumes for roles that might not exist yet. Few design engineers likely trod that path because they saw a lucrative career opportunity on the horizon—rather, chasing curiosity and a desire to see their ideas to fruition, they gradually skilled up in the areas missing from their stack. Those gaps in their abilities mirrored the needs in the industry at large.”