Articles

“Adobe Inc.’s $20 billion takeover of Figma Inc. is set for an in-depth European Union investigation over concerns the deal could harm global competition for software used by designers.” The EU’s in-depth probe is set to run until December 14th, so the future of the deal will stay unclear until then.

Five industry leaders discuss leading products through design and ​“getting rid of the classic product management function”, as told by Brian Chesky during his fireside chat with Dylan Field at Config. A very impressive lineup of contributors to this piece — Lenny Rachitsky, Julie Zhuo (Facebook), Steve Johnson (Netflix), Sho Kuwamoto and Yuhki Yamashita from Figma.

John Maeda shares takeaways from his Design in Tech Report, thoughts on designing with artificial intelligence, and why we should embrace uphill thinking in a world optimized for shortcuts. See also the livestream ​“Diving deeper: Designing with AI in the future”.

“Saving” and ​“liking” resources are now combined to make Community simpler to use. Your saved resources are available from your Community profile or the Resources dropdown in a Figma file.

The number of installs or downloads used to be the only metric in the Community, but over time it was replaced with how many times a resource was used. Now you can also rate and review Community resources. It’ll be interesting to see which of the most used resources are also the most loved ones.

You can now embed videos in FigJam. MP4 and MOV files are both supported.

That’s pretty cool, especially if your team has multiple products with distinct color palettes! ​“Introducing custom color palettes in FigJam: you can now create custom color palettes for your team, so your files can match your team’s own aesthetic or company branding (Organization and Enterprise plans only).”

“On the Enterprise plan, workspace admins can now brand the workspaces they manage to reflect their group by adding custom icons to workspaces. Organization admins can do this for any workspace in the organization as well.”

So excited about this release! I spent a good chunk of my Config talk discussing workarounds for using wide gamut colors in Figma, and this update addresses them all. See this thread by Qi Linzhi on the engineering challenges of implementing support for Display P3.

The next thing I hope for is a more precise way to select colors. Figma relies on hex values in the UI, but they’re supposed to be limited to sRGB and aren’t representative of what you’ll see in the browser. The Dev Mode uses the correct color(display-p3 R G B) syntax as an output, but that doesn’t help much with input. Besides that, I’d like to see when the color is outside of the sRGB range and what is its closest fallback. OkLCH isn’t the easiest color space to use, but OkLCH picker gets that part right.

I love the format of this new newsletter. Every week, Aleks summarizes the many discussions and hot takes that took place on Design Twitter (or should we call it ​“Design X” now?!) It’s a valuable community service and I enjoy the roundups!

Aaron Shapiro talks about his work as a Staff Product Designer at Patreon to ​“guide product, design, and engineering teams in an effort to clean up a decade of cruft and reimagine their existing design system.” It’s a fascinating behind-the-scenes look at how an expansive design system is being built, but I also love this format and storytelling way more than a regular portfolio presentation.

Emily Brody, Product Marketing Manager at Figma, writes about the go-to-market strategy for the Dev Mode and how the team prepared for the launch and triaged bugs, requests, and feedback during the first two weeks.

Carly Ayres from Figma sat down with the people working across design systems tooling both inside and outside Figma to understand what the rise of tokens and features like variables mean for the future of design systems.

Christine Vallaure wrote about one of the most under-the-radar new features of the Dev Mode — units conversion. Now, you can design with pixels and then translate them to rem or other relative units in code. (Thanks for sharing the friend link with Figmalion, Christine!)

Fantastic post by Developer Advocate Jake Albaugh on how component properties can be translated and aligned between design files and coding frameworks to help designers and developers work better together. ​“Implementing components as a designer in Figma differs from implementing as a developer in a codebase. When you optimize for the developer or designer experience with a component, it is tailor-fit for that specific purpose — even if it shares a name with a component in another environment.”

Missed that piece at Forbes a few weeks ago: ​“If you ask me, the antitrust environment right now is kind of nuts. […] I’m going to apply similar thinking to Adobe’s proposed $20 billion acquisition of Figma. The short version: I believe this deal is a sound one, and that regulators who are dubious about it are looking at the wrong things if they really want to promote innovation and protect customers.”

Interesting note on Adobe XD: ​“At one point, XD had 200 people working on it, but the product lacked the real-time collaborative element that drives Figma’s success, and sales never took off. Adobe ultimately reassigned more than 90% of the people working on XD; fewer than 20 work on the app now, and their job is just to keep it running smoothly to fulfill existing contracts.”

Rauno Freiberg is trying to deconstruct and dig out the ​“why” behind great displays of interaction design: ​“This essay is not a tutorial nor a collection of guidelines. But rather an observation on the invisible details of a few interactions that I use often but rarely think about. Besides recreating interfaces, I found this exercise in reflection to be another great way to build a stronger design intuition and vocabulary.”

Staff Software Engineer Daniel O’Connor peels back the layers of the Thumbtack​’s design system, Thumbprint, to show how they built it for flexibility and efficiency: ​“Our current approach is one of layers, dividing our design system up into three levels: Thumbprint Tokens, Thumbprint Atomic, and Thumbprint Components. This approach has transformed the way we build and maintain our design system, and made it easier to deliver a great experience to our consumers and end users.”

Great help article if you’re still struggling with understanding the difference between variables and styles, or questioning if styles are becoming obsolete.

Joey Banks spent a lot of time after Config adjusting component libraries to use the new Figma features. In this issue of Baseline, he dives deep into variables and wrote an epic guide on what they are, how he is using them, and a few shortcuts to help make workflows and creation more efficient. My favorite tip on using the number variables: ​“With your cursor inside an input, tap the equal = key on your keyboard to launch the variable list quickly, or hold Shift + click. To remove a variable, click into the input and tap Backspace twice.” (Note that the = shortcut may go away in the future.)

This part of his conclusion brought back the topic of usability vs. visibility started by component properties: ​“One thing I still find to be a little challenging within this new way of building and viewing components in Figma is that so much of the previous on-canvas visual representation is now absent using variables. Previously, if there were two density sizes used or if a layer was toggled as hidden within a particular situation, that was easy to see, as we had to build it out as a visual variant. With variables, much of that information, such as sizing, booleans, and color adjustments, is all within the Variables modal and not on the canvas.”