UX Collective

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

Follow publication

Five areas Figma need to improve on to stay a step ahead

Steve Dennis
UX Collective
Published in
15 min readAug 30, 2022

A modern glass office building with a Figma logo faintly visible on the windows. It’s partially covered by yellow construction material, with a maintenance crew working on scaffolding outside the building.
All images by MidJourney, directed by the author.

It’s 2022. Figma has completely taken over the Product Design world over the last four years. It’s rare to see a company gain such rapid adoption across an entire industry so quickly.

With that kind of growth comes a lot of problems. The product accrues debt in different areas (both technical and UX) as a team tries to scale fast. Business and user pressures lead to certain areas of the product being prioritized and others falling below the line of what you have the capacity to focus on. A lot of aspects of a product also become a lot harder to fix at scale. These are all realities of product development that everyone should try to understand. I know this well from experience.

I don’t assume any solutions I suggest here are the right ones, and certainly not as easy or quick as an article like this may imply. This is simply an exercise in reflecting more deeply on my experiences with a product that I love and use daily and trying to identify the biggest pain points. The aim is to have a little bit of shared Figma community catharsis, but also to spark ideas within the Figma team or the community at large (hooray for plugins).

Disclaimer: I am friendly with many people on Figma’s team, have participated in a lot of user research sessions for them, and have guested on a Figma live stream. These suggestions come from a good place with the confidence that Figma‘s product team can and will continue to nail it.

Right. Let’s do this.

1. Design tokens

Design tokens are a simple concept with incredibly powerful capabilities if used effectively. If you’re unfamiliar with Design tokens, they are variables with unique names that are assigned simple values, and can be used in place of static values for colors, pixel values for spacing/sizing, fonts, etc. They are very similar to styles in Figma, but more granular and more powerful.

Physical tokens with a variety of colors and sizes. Not what design tokens actually are at all.

Currently, the only workable solution I’ve found to using design tokens in Figma is to use a 3rd party plugin such as Figma Tokens, Design Tokens or Themer. We use Themer at Onfido, but…

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

Written by Steve Dennis

Senior Design Manager @ Onfido, writing about design systems, product design, leadership, and tech @ clipcontent.substack.com.

Responses (10)

Write a response

I can't be the only Figma user on the planet that wants FORM FIELDS for prototyping. Figma is useless for e-commerce usability testing without them.

--

#6: Prototyping. It’s a joke how basic Figma’s prototyping features are.

--

Say you’ve made a structural change to a component like splitting Button into two components, Button and IconButton. The previous Button component had an icon-only variant toggle, but w...

One thing, vaguely related to this, which I really hope they address in the near future is smarter cascading of properties and components.
For example, let's say I am setting up form components for a number of different input types (text, checkbox…

--