Share Your Thoughts

 1. Formulas in token values (mathematical operations)   It would be incredibly useful if we could use simple formulas (e.g. paddingXS*2 + paddingXL*2) when determining token values. Many design systems (for example, Ant Design) use this approach to dynamically obtain tokens. Currently, we haven't even found an analog that can be implemented without any plug-ins). The lack of such a feature makes the work a little more difficult.2. Transparency support for color tokens     Currently, if we need a semi-transparent version of a color marker (for example, purple is 100 at 50% opacity), we have to create a separate marker or manually redefine opacity, which breaks consistency. It would be great if we could keep the original color marker and just apply an opacity modifier (for example, "purple-100" at 40%) without resetting the base value.  Thank you for reviewing these improvements — we are glad to see how Figma is developing!!   

 1. Formulas in token values (mathematical operations)   It would be incredibly useful if we could use simple formulas (e.g. paddingXS*2 + paddingXL*2) when determining token values. Many design systems (for example, Ant Design) use this approach to dynamically obtain tokens. Currently, we haven't even found an analog that can be implemented without any plug-ins). The lack of such a feature makes the work a little more difficult.2. Transparency support for color tokens     Currently, if we need a semi-transparent version of a color marker (for example, purple is 100 at 50% opacity), we have to create a separate marker or manually redefine opacity, which breaks consistency. It would be great if we could keep the original color marker and just apply an opacity modifier (for example, "purple-100" at 40%) without resetting the base value.  Thank you for reviewing these improvements — we are glad to see how Figma is developing!   

give the ability to change the icon in the master instance - buttons, without the need to wrap it in a layout, and create a HAG for the layout, because you have a default instance size set in the master component for all instances

The fill is not visible on a vector shape unless its closed. Many applications and the web supports fill on open vector shapes, but not Figma. Please allow something like this. This red area should be fillable by the paint bucket.  

You can only see 8 rows and its too much scrolling. It doesn’t need to be only one column nor so short. If you’re on a 27 inch monitor or bigger it should adapt and grow proportionally to show 30 or more selections at once. It could easily be three times as wide and 3 times as tall. I know about showing just the swatch but I need names visible. Secondly the most commonly used choices could come up first without having to search. 

Hello everyone! I think having a shortcut to open/close the local variables would be very helpful. For example in cases where I’m prototyping and need to access the local variables to ensure the accuracy of the variable names or values that I’m assigning in the interactions. Currently, if I want to do this, I have to switch between the prototype panel to the design panel in order to open the local variables, check them and then go back to prototype. Note: I am aware that it is possible to keep the local variables window open, but this often leads to numerous bugs in the prototype. For example, when it is open, I am unable to drag the prototype interactions to reorder them.

“Rectangle” is not editable This is a small one, maybe. When adding new layers, I can see their name in the inspector but cannot edit the name directly. I only can edit in the Layers pane.Somehow that’s weird for me. Let’s make it more direct, shall we?

Conditional interactions are half broken at the moment. For example, all I want is to create a switch for light / dark mode for my prototype. We already have the “Set variable mode” action, but I cannot use it inside a Conditional if/else. All we need is to be able to do something like: if library/mode == Dark Set variable mode == Light else Set variable mode == Dark There’s also no else if(); while not a deal breaker, it would save time instead of adding another set of if/else (plus the bugs that come with it). Or we could have a switch action to switch between 2 states / values / modes, that would be great to use on switch components and require way less fidgeting with actions.

style 

In Sketch, holding Option + Command allows users to drag a selected object from anywhere on the canvas, without needing to hover directly over the object. This feature significantly enhances workflow efficiency, especially in complex designs where objects may be obscured or challenging to click precisely. In Figma, dragging an object requires the cursor to be directly over the object or its bounding box, which can be limiting in certain scenarios. Introducing a similar functionality in Figma would streamline the design process, reduce unnecessary clicks, and improve overall usability for designers accustomed to this behavior in other tools. Implementing this feature would be a valuable addition for users transitioning from Sketch and would enhance Figma’s user experience by providing more flexible object manipulation.

It is not obvious in the default view of an open document that the user needs to create a frame as a canvas to start a design. Suggestion to either have a visual tooltip pointing to the frame icon in the toolbar alt. a “create frame” button centered on the main area/window. 

Why, in UI3, does an object move 2 pixels each time when using the keyboard arrow keys to move it? I am so surprised by this setting!

I think it would be much easier to use annotations if they were highlighted when hovering or selecting an asset / frame / object that had one attached. Right now it’s a bit overwhelming trying to find the right line.  

It would be great to have the option of setting a max-width of a grid. Elements would stretch but always with a maximum value.

UI3 feels incomplete. There are so many quality of life features and ease of use benefits that UI2 provides that were taken away in UI3. The UI3 experience, especially for people who have been using UI2, feels like a significant downgrade to the user experience.  UI elements are more difficult to see and understand in UI3, like the layers panel - these new icons are awful, and it's more challenging to collapse panels with the new way the layers panel functions, which is very annoying.There are fewer helpful dialogs (example: UI2 says “Exporting” when it’s processing the export of images. UI3 just hangs there, no dialog, and it appears like it crashed...This is a downgrade to the user experience...Why was this ever changed?).In UI2, you can hover your mouse over any measurement setting, click it, and use your mouse to increase or decrease the value. In UI3, this interaction is buggy about 80% of the time I try to use it, and it infuriates the hell out of me. I feel like I’m relearning h

I’ve created this UI for Narrati through claude ai, I am not sure how to import this UI to figma, If there any figma AI which can convert screenshot into figma design, I want to shift this website to framer, thats why looking for a solution.Framer websites & figma is very same, if there any way to make screenshot to figma design, building framer websites become so easy.

It would be great to be able to use multiple individual variables for effects. For example, I have a blur and a drop shadow saved as two separate variables. I don’t always use them together, but sometimes I do. I would like to be able to use both together, without having to create a separate variable with the blur and drop shadow.  

In trying to meet users where they are working we need to place documentation within Figma files. This means we want documentation for various personas. In our case, we need to provide documentation for consumers of our library and assets, and documentation for those creating the assets. Feature to propose: A way to expand security trimming (similar way in which we can share teams/projects/files) so we can place documentation within our file for creators and hide it from consumers.

See all layers is creating a fair amount of annoyance in my work flow.Please remove this feature its annoying to no end. 

Need:I would like to optimise the publishing of the different libraries and ideally manage it from a central place.Use case:I have one asset libraryI have one style libraryI have one component libraryI have multiple files for different features - Figma being still too slow to allow me to manage a whole application in one file.Let’s say all the feature files need elements from the three above-mentioned library.Now I change a color in the style library and as of today what I would have to do would be the following: Go in each dependent library and update all the elements that use the color from the style library Publish the libraries Go in each file to update the components in some cases publish some files so that other files can have the latest update of componentsThis requires to open many files and this could be “easily” optimised if there was a feature that allowed to create a pipeline that we can run everytime we update a library.Or another solution, have a centralised place in whic

Our design token collection (variables) was accidentally deleted. Would be nice if there could be a restore action or trashcan concept for retrieving deleted collections. Perhaps archiving could be interesting as well.

I’m really liking the new sections in FigJam (which I used to have to make manually with shapes) but I’ve noticed that the normal grid dots don’t seem to show up within the sections which makes it tough to align items within them that are farther apart (in my case vertically stacked sections). Would it be possible to get these added back in? Or at least some way to use/create guides (similar to those in most photo/graphics editing software)?

Decades ago when prototyping interfaces I would just use HTML prototypes, which made tooltips super easy to prototype.  Decades later with Figma - which is an excellent design and prototyping tool don’t get me wrong - adding tooltips to one’s prototype, is incredibly painstaking.  It would be so much easier if Figma just added a field for each layer called “tooltip”, which, when hovered over in prototype mode, would display the tooltip after a number of milliseconds (which could be customized as a bonus feature).  This would make Figma prototypes tooltip-friendly in such an easy way.  And from a designer-developer handoff perspective,  it would be great if Figma prototypes had a toggle to enable text selection in the prototype. That way the developer would just run the prototype, get the tooltip in context, and copy its text. 

Nice work including Typography and Gradients as variables! But I feel like the ability to use a variable for opacity when defining a color palette is missing. Which means the size of my color palette is double what it should be as you have to define each opacity as a separate variable.

Hi,I had a file named "Wellow UI Kit" in my account (ipek.eldek020@gmail.com) but I can no longer find it.I’ve checked my Recents, Drafts, Trash, and other workspaces, but the file is missing.Could you please help me recover it or check if it has been accidentally deleted or moved?Thank you!