Everything we announced at Config Europe, and how we’re bringing design and code closer together in Figma.
There’s a natural tension between design and code. In the world of design, the focus is deciding what to build—in the world of code, the focus is building it.
Traditionally, designers and developers have occupied different worlds, requiring separate tools. In practice, they’re partners working to bring a product to life. While their approaches may differ, each offer unique advantages. Designers optimize for freeform, creative exploration, while developers take a more structured approach. The result is an inevitable tension between the two: what feels like “breaking” a component to a developer is just creative exploration to a designer; what reads as “structure” to a developer might be inhibiting to a designer.
We believe in embracing concepts from engineering and design, adopting the rigor and reusability of code while preserving the rapid iteration and uninhibited exploration that makes visual design so powerful.
At Config Europe this morning, we announced several new features that will carry the best of both worlds to design systems in Figma—bringing them closer to code and making them intuitive to use, while more efficiently translating designs into production.
Teams typically maintain a set of components for design, and one for development. While this is a normal and good approach, straddling both worlds isn’t always easy. When code and design components mirror each other, teams can move much more efficiently. Today, we announced Variants, Interactive Components, and improvements to Auto Layout that will allow teams to do just that.
A single component in front-end code typically renders in a number of visual styles, for different contexts and states of user interaction. For example, a button might have primary and secondary styles, small and large sizes, and different versions for iOS and Android. Currently, a button component like this would be represented by different components, each for a different visual style. This mismatch between design and code can result in miscommunication, ultimately slowing down the development process.
To solve this problem, we’re launching Variants, a way to logically group together variations of the same component into a single, more powerful component. In addition to simplifying the asset panel, this update will allow components to map more closely to code.
Now that you’re able to group a component’s interactive states together with Variants, you may be wondering whether or not these interactive states work with your prototypes.
While Variants let us group a component’s states together, prototyping the transitions between these states in Figma today still requires a lot of work. Just to create the illusion of an interactive object, designers would have to connect multiple frames with overlays.
Interactive Components make prototyping much more efficient by letting designers add prototyping interactions between Variants, so instances are immediately “alive” in prototyping mode.
The introduction of Auto Layout in 2019 brought layout rules to Figma. By allowing designers to make updates to button text without manually adjusting frame size, Auto Layout empowers them to more easily create responsive interfaces. But we knew we had more work ahead of us to bring Auto Layout even closer to how the CSS box model and Flexbox work on the Web.
In our next evolution, we’re bringing a simplified UI to Auto Layout so it’s even easier to use, plus new features based on some of our most frequent requests: the ability to stretch elements along both axes, configure independent padding values, and optimize spacing for common UI patterns like navigation icons.
In addition to making design systems more powerful, we’ve added features that help both designers and developers navigate large, complex libraries.
When you’re navigating thousands of components, finding the right one was previously a clunky experience in Figma. You’d have to remember the exact component name or scan a giant list. In addition to Variants, which will reduce the number of components designers need to look through, we’ve overhauled the Instance Swap Menu so that it scales with your design system. You can now use thumbnails, keyboard shortcuts, and search to find the component you’re looking for.
When it comes time to implement designs, developers need to find the right information. The new Inspect Tab replaces the Code panel and provides more relevant properties developers can grab. The name of the selected layer is shown right at the top to help designers and developers get on the same page about what’s being implemented. And there are new sections showing relevant values for Variants, Colors, Shadows, Content, Typography, Borders, and more. It also lets developers click to copy any value to their clipboard—including whole snippets of key:value pairs—so they can easily paste things into code.
These updates are just the start of how we envision bringing design and code closer together in Figma. There are times when a designer needs a free and unrestrained canvas to work in, and there are times when a more structured code-inspired approach is the fastest way for a designer to work. We imagine a world where designers can move smoothly between those two ways of working as they see fit.
Dylan Field is the co-founder and CEO of Figma. Dylan studied computer science and mathematics at Brown University where he and his co-founder, Evan Wallace, first started experimenting with design tools built on (and for) the web. With funding from a Thiel fellowship, they began Figma. Prior to Figma, Dylan interned at O'Reilly Media, LinkedIn, and Flipboard.
Reflections on Config, our first user conference
When we first set out to organize a user conference, our goal was to create a physical manifestation of the community, a space to have meaningful conversations. Here is a look at some key themes that emerged from those conversations.