Typography variables can now be scoped to limit which properties they can be applied to. For example, if you scope a number variable to font size, you can only apply the variable to font size.

Also, copying and pasting an object bound to local variables will no longer populate a file with local variables unless you choose to in a tooltip.

A nice little update to the Figma mobile app. I like how the app is focused on real-world ​“jobs to be done“ instead of shoehorning the whole Figma experience into the phone.

The move of drafts to teams caused a big enough uproar in the Figma community to warrant an explanation from Dylan Field, the CEO of Figma. Dann Petty made one of the strongest arguments against this change.

The strong feelings made me wonder about the differences in how we use Figma, and it probably comes down to handling multiple accounts and teams. I usually have two Figma accounts — one for personal projects and another tied to my work email address. Each account has its own drafts, so my personal drafts are never mixed with work. If you’re a freelancer and a part of multiple teams with a single email address, all your drafts are mixed, and separating them can feel like an invasion into your personal space. I don’t share the strong feelings on this change, but can see where Dann and others are coming from. (Pro tip: I use a separate Figma Beta app for the personal account, so I never have to switch accounts in the app.)

“For the first installment in our series, we sat down with the Linear team who put forth a series of principles to guide their own work. Here, co-founder Jori Lallo and Chief Operating Officer Cristina Cordova share why opinionated software is core to Linear’s methodology, and how other teams can adopt it.”

My favorite part from Jori: ​“Many people try to adapt things from the industry that might not actually be applicable to them, or they might not know the potential downside. They were developed at places that are bigger and growing faster than most companies, so you need to try to understand what’s behind them and adapt pieces of them.”

Matt D. Smith boiled down his design process into eight steps. I love how a big part of it is conditional on the project’s complexity. So many designers make the mistake of following a complicated process and taking extra steps on more straightforward projects, where that time is better spent on another round of experimentation or iteration. (See also the above quote from Linear.)

What a fun project! A new interview series looking inside Figma files of the top designers. The first season includes six interviews with folks from Perplexity AI, LottieFiles, Bezi, and other companies. There is much value in just sharing the screen and walking through your actual work files instead of creating an idealized version of the design process.

Designer Advocate Ana Boyer with a reminder to plan your tokens and variables implementation before creating them in Figma. ​“In general, building then refactoring your variables is much more work than taking more time to plan before implementing. As they say: measure twice, cut once.” (That said, making refactoring easier in Figma won’t hurt.)

Dan Hollick shared his Creator Micro setup (with a beautiful illustration, of course!), and there are some good ideas in replies as well. I also shared my setup on Twitter.

Using it for a few weeks made me dream of eink key caps that can be updated based on the current mode. I find it hard to remember what keys do across four modes, so I rarely switch them. Elgato Stream Deck might be the answer, but I’m not a big fan of the look.

The other day, I was looking for a tutorial on a specific animation technique and found this course by Tim Gabe. It’s free and has high-quality content — worth checking out!

Christine Vallaure made a responsive and modular type scale using a scaling ratio approach.

A nicely organized UI kit for an open-source platform for commerce.

Jordan Singer shares a few things he learned while designing and building AI at Figma.