Thanks for Unsplash for this image. Customized by Roman Kamushken 🏀

One year in Figma. Subjective tour through pros and cons

The performance evolution you won’t notice just by starting with this tool nowadays

They apparently didn't expect such a number of components

When I developed my first design system in Figma earlier this year, I ran into a performance threshold. “Oops, they didn’t seem to have expected so many components,” I thought, after another long wait, until the primary color redraws for all the templates in my product. It is used in more than a hundred components. It's because the system is huge itself: 1682 components, of which 1171 material icon and 511 design module. And it’s all broken down into 25 pages: Buttons, Inputs, Application barts, Bottom navigation, and so on.

Preview components http://setproduct.com/material/components

I literally felt performance improvements

Gradually, in the process of developing my system, I began to notice that many processes in Figma started to occur quicker. Since I constantly had to change a million little things for a variety of objects, I immediately recorded the moments when it began to happen faster. Then even faster. And faster!

Lack of global colors

So far, we have to invest color as a component in each module to get a design system that is flexible for customization. They already working on it, but nevertheless. I believe that the introduction of global colors can greatly improve the performance of a bulk atomic system. Hundreds of components will get rid of an extra nested element that needs to be redrawn whenever you change the color scheme.

No search by local components

The search becomes available only after you publish it into team library. For example, it is acceptable for teams. But it is unacceptable for an average freelancer who wants to use his design system for his own clients. He clones it for a new client and quickly customizes for his needs. And he, incidentally, also needs the search. And absolutely do not need the features of the team.

Difficult work in Instance if there are many items

This becomes important when there are many components and they have many similar duplicates, but with small changes. For example, a dozen of cards, hundreds of icons. You will not be able to quickly find the desired card module in the drop-down list if they are called like Card 1, 2, 3, 4…. N. And it's not a very good idea to turn the name of the component in it’s description.

The components principle

The very principle of the components is amazing. For example, you offset any element within a component and it is offset in tens or hundreds of subordinates. Bulk editing in just 3–5 steps.

Smart objects snapping

Snap is so well thought out and sensitive that you can work with multiple objects at once at a great distance. You will move and move them and without worrying about missing into the grid.

Progressive selection

I select a lot of objects and I’m not afraid to miss, because the selection is saved in the history of actions. And if you combine selections with pressing Ctrl/Alt keys, many routine actions go into semi-automatic mode.

Some components from Material Navigation Drawer section. Open it in Figma
Smart library as mobile design system with 105 app templates and 250+ components

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store