Articles

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.”

“There is a cohort of world-renowned graphic designers whose work people know whether they’re into design or not, and Paula Scher’s name sits squarely on that list. With this in mind, we invited the Pentagram partner to share her ​“10 rules for play” noted down over a formidable and long-lasting career.”

In-person attendees of Config 2023 found a copy of a playful zine in their swag bags. Figma collaborated with It’s Nice That on The Playbook to showcase the benefits of spontaneous thinking and curiosity through design. Inside, there is a piece on ​“how to embrace (and enjoy) endless iteration” by Chief Product Officer Yuhki Yamashita, as well as an investigation into what it truly means to be a collaborative engineer by Chief Technology Officer Kris Rasmussen. If you prefer getting hands-on rather than sitting down with an essay, there are also a host of activities to tackle.

Intuit is the parent company for products such as Quickbooks, TurboTax, Mint, Mailchimp, and Credit Karma. Intuit Design System (IDS) is used as a foundational system that other multidimensional design systems are built on top of. Nate Baldwin wrote about creating a design token taxonomy for it: ​“Token names are how design tokens are referenced and identified by consumers. But at the core, a ​“name” is more of an ordered representation of a catalog system and API. This catalog system and API is also known as a token taxonomy. Building a clear taxonomy assisted us in appropriately and consistently classifying tokens, as well as providing a scalable and predictable naming convention for consumers.”

“For added security, organization admins on the Enterprise plan can set an idle session timeout to log out users as soon as 12 hours after they become inactive. By default, Figma automatically logs users out when they are inactive for 21 days.”

Starting July 6th, Figma Enterprise customers have the option to host key parts of their Figma and FigJam files in the EU. This feature is designed to give Figma customers in the EU greater flexibility to meet local compliance and data privacy requirements.

A deep dive into variables by Thalion.

Lilibeth Bustos Linares is a teacher at Memorisely and co-organizer of a wonderful morning hike with Zander Whitehurst a day before the Config. Thanks to jet lag I was able to get up at 5:30 am and join the group at 6:30 am. It was wonderful to walk the Historic Trail of San Francisco and chat with so many designers from around the world! 

Dan Mall is an expert in design systems and a fellow designer from Philadelphia. Dan organized a post-Config basketball game, hosted a special dinner, and even captained the winning team at the Figmatch design competition. His recap focuses on what makes in-person conferences really special.

Joey Banks’ recap of everything announced at Config. (I was lucky to meet Joey and share the scene with him at Config, and his deep knowledge of Figma and expertise in design systems are second to none. Highly recommend subscribing to his Baseline newsletter.)