Suggest a Feature

I’m super excited to be using native variables in Figma; however, there are couple of glaring holes. Identifying an EM scale for text (maybe this will come with Font Variables support) Need to be able to reference an existing Variable (an Alias) and be able to do math on it; for instance, if Spacer = 20px, i would like to be able to reference {spacer}/2 to get 10px without changing the parent value

The new Figma seems to not process percentages on sizing, compared to the older version. Video shows me adding auto layout to two items, overlaying one item and setting the width as a 50% width, which it cannot process. Switching back to the old Figma I can simply change the percentage there and it works fine.

Here’s the translation of your text into English: "The page and layer separators need improvement. Even though I create a lot of pages, every time the client wants to review the designs, they don’t realize that more pages have been created below. For example, maybe a slight fade effect could be added to the bottom of the pages to indicate that there are more pages below. Additionally, the separator between pages and the separator between pages and layers look very similar, making them hard to distinguish from one another."

The sensitivity of scaling in the new version of Figma art board is too high and not user-friendly. It is recommended to adjust it

The Problem: Collaborating with stakeholders often requires many content updates & iterations (text, image, etc). I think most content writers/stakeholders could easily make these updates but would require editor access, giving them unneeded (& often unwanted) edit permissions. Suggested Solution: Provide a Content Editor role in Figma that allows a user to: Update text layers Update image fills Anything else? Additional features could include: Editor can lock/unlock editability of content per layer Ability to suggest/accept changes (similar to google docs?) Assign content to users for editing? Any other ideas on how this role could work?

When I share a Slide link, I’d like it to open with the left side nav shown by default. Then if someone wants they can go into full-screen mode. Opening links in full-screen presentation mode by default makes it hard to hop around a deck quickly.

The increased size of text, toggles, and lack of color (white text now gray) makes the component property panel rather hard to read and use. Suggest at the minimum - make the property group titles “white” for better legibility/contrast.

Under reset component dropdown there’s “reset others” option that has an identical icon to “More actions”. That wouldn’t much of a big deal if “reset others” only showed up under that dropdown. But in certain cases when a layer inside the component doesn’t have much actions to it then it can show up as the third item on display, exactly in the same spot as “more actions” with identical icons too. It did send me in loops not understanding what was going on every time I tried to open the “more actions” dropdown.

Can we please get an option to use a border/outline grid instead of the filled in grid? When designing its pretty annoying to have a full column on top of your design. A border would be a great addition.

It would be nice to have a feature to remove component.

We have an updated Starred section on the Dashboard. My alphabetically ordered list of about 100 items which I had to do manually has now been shuffled and it’s a real inconvenience. Figma is the industry-leading platform for user experience design, yet so many decisions it makes with the software inhibit the experience of those using it. Starred section needs sorting modes. Custom A-Z Chronological These are the minimum requirement. Look at how Spotify does it for reference.

The team and I have been compiling a list of features we’d love to see get implemented at some point. These are primarily related to design systems and have come about as we’ve been working on improvements to our own system. Would love to know if others have found a need for other design systems related features. Improved token/variable manager: The current token manager is pretty basic and a couple simple additions would really improve our workflows. The ability to search for tokens in a given collection More verbose token arrangement tools, we’ve accidentally moved the wrong set of tokens many times Token mode/column arrangement, the order of the options that are displayed when changing themes is determined by this but if you set it up wrong at first or add any new mode then you can’t rearrange them. Ability to natively export tokens/variables without needing a third-party plugin. Options for raw data, JSON, CSS, etc. Theming and modes: Modes are relatively one-time use right now.

My team has a lot of Colour styles, and sometimes it’s hard to find a particular swatch. Also, Figma sometimes ‘unlink’ the style and the colour. Having the ability to use the search field inside Colour styles to filter HEX codes would be amazing and a time saver.

I use properties and variants a lot in my components. I know I can add them via naming conventions, but when dealing with a lot of existing variants, it can be tedious and confusing. I understand that Figma is trying simplify the UI by hiding the “Add New Property” plus icon. But it’s a key function for me and because it’s only revealed on hover, it took me a super long time to figure it out. (Sidenote, this UI change is not covered in the existing Figma docs). My proposal is that you reveal the plus sign again in the right panel, or minimally, at least in the component’s 3 dot menu. UI3 default state: UI3 hover state: UI3 component menu options

I hope there is a way to recognize the others’ suitable properties. My teammates seem unable to recognize the right one to choose.

At the moment if I open a project with one account, and want to edit/comment on another account, I have to go to Home/recently viewed and switch accounts. It would be great if I could ‘switch accounts’ within the project itself.

Sometimes when too many tabs are open, their names are getting truncated and it would be quite difficult to jump from one tab to another. E.g. tracing a component back to design system to check master component and documentations before jumping back to working file, it would take some time to locate where the working file tab is. Suggesting a feature to incorporate a search bar (collapse if it’s not activated) or even just a keyboard shortcut to let user quickly scroll through and search among opened tabs. Something like command+tab in macOS or control+tab in Figma but with better visual and thumbnails.

Hi Currently, the font used for these two languages is Arial I think which is very bad and unreadable and ugly. My suggestion is to replace it with Vazirmatn, a popular free font with more than 19.0 million users and used by many companies, including Telegram.Google Fonts

We’re looking for a banner with a custom message to appear across all files. Our privacy and security team is asking us to include a reminder (that can be dismissed) as a banner across the top of every file to remind everyone not to include any identifying information or private personal information in our Figma files. It’s my understanding that users don’t have the option to set this up yet, but is it coming in the future??

Would be good to see the selected annotation clearer by either have a stronger focus state or lower opacity on the other unselected ones. I almost didn’t notice that the selected layer had an annotation because the green glow is so subtle.

Why shape size in autolayout parameters but x y is in position block? there is no sense in this. why is the thing responsible for the position, namely autolayout, placed next to the form?, and the position, which is more related to autolayout, is moved to another block?, when I want to change the size of the form, I now constantly look at the position, when the position is associated with autolayout, since autolayout is a setting that automates POSITION. Why don’t you place the position next to the autolayout, and move the layer size up? you also have what is called constraints, and even the buttons for quickly distributing constraints are moved to the position, which is also related to autolayout, instead you create confusion by entering the layer size parameter in autolayout, which sets the position, and the position setting in another block. Why are you doing this? This is complete confusion …

Used to able to pin a comment and see it while working but that went away in UI3, can you bring it back?

I have a dozen animations for instruction functionalities, but every action is a separate GIF. Creating a component with variants don’t work well, as finding the exact time in ms of an animation is hardly doable. Imagine having 3 or more animations that should play one after another, and then play from the start again. Please make this easier, like, creating a list of animations and make looping optional. Thanks!

I am playing with colors for a project. It would be nice to have variables per artboard so I could make color variables that are scoped to an artboard. This would allow users to play with colors and have the colors on the page live update rather than having to set them at the file level which could be harder to manage.

Variants have become one of the most important features I use within Figma. They are incredibly powerful! As they are so useful, I find myself looking for the ability to have properties show ONLY when another property is a certain value. A quick example of what I mean is like this: Let’s assume you have a button, and the top level of the properties are set up to be Primary and Secondary: Let’s now assume I have an icon added to my buttons, but they are ONLY available to my Secondary button: It would be so helpful here if this was possible: Select “Secondary” as my Property on the button variant. When “Secondary” is the active Property, I can then see ANOTHER Property where I can choose the icon for this example. That icon Property is only visible because I have said that it belongs to the “Secondary” Property. Apologies if I have not explained this very well, but I think this could really be helpful when working with Variants.