UX Collective

We believe designers are thinkers as much as they are makers. https://linktr.ee/uxc

Follow publication

Member-only story

10 Commandments in Figma

Danny Sapio
UX Collective
Published in
8 min readAug 15, 2022

Figma is used by most design teams today, but not all designers utilize it to the full capacity and get the most out of what the tool has to offer.

In this article, I would like to share a few best practices I've learned over the years using Figma to help maximize how we use the tool to become more effective and efficient.

1. If an element is used more than once, make it a component

I recommend as a component best practice to create components as much as possible. If an element appears two or more times in my file, I turn it into a component.

I do this because if I'm using components, in an instant, I'm able to see what a design would look like by making an adjustment in one place. It also keeps my file more organized, easier to manage, and components are quick to search and find when needed.

2. We should (almost) never use groups

Why you should use Frames, Not Groups by Molly Hellmuth

Groups in Figma are basically obsolete.

As Molly Hellmuth puts it in Why you should use Frames, not Groups, in Figma — "As far as I can tell, (groups) only exist because designers are used to having them in other design tools, and Figma is easing their transition by including them."

I can only think of one scenario when groups make more sense than frames or, better, an auto layout frame — and that’s when we have a group of vectors for an illustration. For everyday interface design, though, it’s best to ditch groups.

Groups don't allow us to set different behavior for elements within a group the way frames do. Everything in a group resizes the same way, and it can't be customized the way frames can to adapt content differently on resizing using constraints and independent sizing.

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Write a response

it makes sense to keep our prototyped version separate from our working designs.

How would you then publish changes to your prototype? Would you not have to redo entire frames within the prototype? Ok for simple ones, but if there’s lots of interactions then that gets tricky, no?

--

Great article! And I cannot stress enough the commandment to use frames or auto-layout instead of groups. As I was transitioning from using Illustrator to using Figma for my UX work, I had to get out of using groups by default. Now I'm an auto-layout ambassador and use it for almost everything

--

Use separate Figma pages for different work. For example, I might have a page for a desktop version and another page for a mobile version of a feature.

I don’t really agree with that. It's much easier for developer to find layouts of the page if they are near each other rather than jumping from page to page.
I use separate Figma pages for each website page with its variations.

--