“After finalizing and polishing their work in Figma, designers often expect developers to magically make sense of it. However, as that’s not usually the case, things can end up looking pretty grim. What’s going wrong?” The authors blame the outdated handoff mindset and suggest the four steps that can turn the handoff process from a potential headache into a smooth collaboration.
Joey Banks recaps the Framework announcements. On choosing between styles and variables: “Wait, but styles don’t allow for modes, right? Wouldn’t the use of styles prevent us from switching themes or brands? Actually, this is what I’m most excited about with this update, and it’s the further positioning of how styles can be useful in combination with variables. Because all styles (yes, typography now, too!) can use variables, adjusting one variable mode within a style will adjust all variables to reflect that new mode change.”
Chad Bergman continues the series on getting started with design systems with a walkthrough of the basics of creating a system tailored to your unique goals and challenges, whether building from scratch or starting with existing pieces.
Jacob Miller, a Product Manager for Design Systems at Figma, gives an overview of everything launched at Framework — Code Connect for developers, typography and gradient variables, and the new Library Analytics API. All of the above is designed to drive design system adoption across the teams because “building a design system is only half the battle — the real challenge is getting it adopted by both designers and developers.” If you missed the event, that’s one summary you need.
“Create a FigJam board during or outside of a Google Meet call to jam remotely or in person.”
“Now, your team can access Figma library data outside of the app, so you can organize the data based on your organization’s needs. This will include component insertion, detachment, and instance data, as well as team and file-level breakdowns. Enterprise plans only.”
“Code Connect is a tool for design systems and engineering teams to bring component code into Dev Mode. When inspecting a component with connected code snippets, developers will see design system code from their libraries instead of auto-generated code.” Currently in beta. Available on Enterprise or Organization plans only.
Sam shares math equations she used in Token Studio to build all sorts of dimension tokens and even a proportional scale that snaps to a 4 or 8 pixel grid. This guide uses typography as an example, but the same ideas apply to sizing and spacing. There is even a free playground in the Community.
“The Washington Post’s inclusive process for creating new design system components bridges the gap between design and development to make features that help navigate the news online.”
Ana Boyer wonders, what if we also marketed design systems like products? “In my time at Figma, I’ve talked to dozens of design systems teams looking to drive adoption and prove the value of their work. Now, more than ever, it’s important to think, strategize, and execute like a marketer. Here are some of the tactics and strategies for helping you position your design system as an integral asset — whether launching anew or revitalizing existing efforts.”
This April Fun Day, Figma had some fun with cursors. “What better way to celebrate this icon of interaction than with a look back at digital eras through the decades? For one week starting this April Fun Day, you’ll be able to choose throwback cursors inspired by four aesthetics from internet history: We’re calling them 8‑bit, Y2K, Skeuomorphic, and Aero. Here, we reminisce about bygone trends and reveal how we brought these vintages back to life.”
Figma is bringing together the design systems community on April 16 to share new features, best practices, and a peek into what’s coming next in the half-day event. “We’ll share more about new capabilities to make design systems more powerful and easier to adopt, as well as features to connect your system closer to code. Our product sessions will dive deep into strategies for structuring and maintaining your system.”
Considering it’s only a couple of months until Config 2024, it’s pretty clear they will put a bow on some of the features announced last year. Typographic variables, anyone?
Tom MacWright writes about his experience building the Placemark plugin for creating vector street-level maps and Placemark Globe for rendering a globe. He covers several interconnected topics, including tracking usage, sandboxing, plugin architecture, and authoring flow.
A guide to creating icons in Figma with a solid introduction to basic tools, grids, and approaches to designing a cohesive set.
I loved this article by Karri Saarinen from Linear on why redesigns are important and its sequel, “How we redesigned the Linear UI,” on tackling that kind of project. “This incremental way of building the product is hugely beneficial, and often necessary — though it unbalances the overall design, and leads to design debt. Each new capability adds stress on the product’s existing surfaces for which it was initially designed. Functionality no longer fits in a coherent way. It needs to be rebalanced and rethought.”
On paying off the design debt: “While the design debt often happens in small increments, it’s best to be paid in larger sweeps. This goes against the common wisdom in engineering where complete code rewrites are avoided. The difference is that on the engineering side, a modular or incremental way of working can work as the technical implementation is not really visible. Whereas the product experience is holistic and visual.”
On exploring the next version without considering practicality: “A secret I’ve learned is that when you tell people a design is a “concept” or “conceptual” it makes it less likely that the idea is attacked from whatever perspective they hold or problems they see with it. The concept is not perceived as real, but something that can be entertained. By bringing leaders or even teams along with the concept iterations, it starts to solidify the new direction in their mind, eventually becoming more and more familiar. That’s the power of visual design.”
On April 1st, Figma makes URLs shorter and easier to read. If you call Figma’s REST APIs, embed files in your websites or apps, or use these URLs in your plugin or widget, you may need to make a few tweaks to your code.
Fast Company calls Figma one of the “most innovative companies in applied AI” for boosting creativity and digital collaboration with the OpenAI-powered Jambot plugin for FigJam. Wild to think that it was born out of an internal two-day AI hackathon just eight months ago. (For additional context, see the above interview with Nilay Patel.)
Nilay Patel, editor-in-chief of the Verge, talked to Dylan Field in a live interview from SXSW about life after the failed Adobe deal, the new multi-edit and Dev Mode, generative AI, the state of the web, design trends, solarpunk, and what comes next. Nilay is a great interviewer, so I highly recommend reading (or listening!) this conversation.
Christine makes a point that we can move beyond the rigid structure of fixed responsive breakpoints with modern CSS layouts, crafting flexible and dynamic designs that seamlessly adjust to different screen sizes. In this article, she covers responsive column-based design vs. modern CSS layout, CSS Flexbox and Grids, and questions if we still need breakpoints.