Suggest a Feature

Hey there! I’m a designer and use Figma on a daily basis, like many of you. Our job as designers is to improve user experience and make interfaces easier to use and understand. However, it turns out that in improving everything around us, we’ve completely forgotten about what we have - our tool, Figma. I found that I was constantly experiencing negative pattern when working with the Plugins menu. So, I decided to do some research to identify the problem and come up with a solution to make the daily experience of using Figma more convenient. → I chose myself as “persona” and conducted an interview with myself to localize the problem → I involved my colleagues and conducted additional interviews to confirm the hypothesis → Then, I made a survey for designers from different chats and groups to gather quantitative data to see if the proposed solution would be useful So, here’s my improvement: Plugins groupping feature 👇 I've improved the Figma plugins menu I’m currently

Would be so great to be able to create Responsive prototype instead of fixed “image like” prototypes. Like framer does actually.

Would be awesome if mindmap nodes and branches were in colored bubbles instead if plane text. For big mindmaps color coding is a must, but picking a color for each branch manually takes away from the process of free-flow of ideas.

I’m currently using the Figma measure plugin during my design to tech handoff for my less front end savvy tech teams. The best part of this plugin is that it highlights the frame box that I’m measuring against. Since in Web development every HTML elements are modeled as CSS box. Therefore highlighting the frame box in my Figma design for tech handoff is super important, just to give my tech team a high level idea on how to construct the HTML elements and write the CSS code to position those HTML elements. However, when I played around the Figma dev mode recently, I was hoping it can achieve similar functions like the Figma measure plugin. But the Measurement feature is just useless since my tech team will have no clue that the X pixel measured is between which two layers, especially for a very complex design layout. Figma measure plugin is free but Figma dev mode is not. I would hope at least Figma dev mode can achieve the same functions like the free plugin, but looks like not. Kind o

I searched and couldn’t find any an option for this… I think it would be nice to have an admin toggle to require a comment when publishing a library. I manage our team’s component library and feel a detailed comment for any changes is imperative, but I don’t like having to be the comment police each time a teammate makes a change and publishes without leaving a comment. Being able to set this globally or maybe even on individual libraries would be nice.

It’s incredibly frustrating that when you hover over a Figma browser tab, it shows you the document title, but when you click and hold the browser Back button, the page history just shows “Figma” for every document you’ve recently visited. So you have to randomly click on them until you find the one you wanted to revisit. Is there any way you could show the real document title in the Back button history? It does already appear in the browser history window, so I’m not sure what the back button does differently, but it’s the same in Firefox and Chrome. (It’s even worse in Safari… it just shows the URL, but not the part that includes the document title.)

When in Prototype view, the destination of an interaction is shown by a blue arrow (aka noodle). The destination may be off-screen. It may be very, very far off-screen. There should be a simple way to “go there” – to bring the destination frame into view, or select it so that I can use Shift-2 to bring it into view. And vice versa – a simple way to go to the origin of a noodle. Currently I have to either follow the noodle by panning, or zoom out until I can see the destination, then zoom in. This is laborious. How about a context menu when you right-click on a noodle, with the options: Go to destination / Go to origin / Interaction details

When any element is inside a transparent section the name of it is barely visible. It would be great if at some transparency level the text color would invert back to classic blue or the section’s color.

Hi! My organization uses components and shared libraries pretty heavily, and sometimes one component’s one variant can have tens to hundreds of instances across multiple pages in a file. In this kind of cases, if I go to the master component, make a change to that component variant, publish, go back to the design file, and choose to Update the instances, the unsaved changes icon (i.e. the icon of a little cloud with an up arrow pointing into it) would show up and remain there for a variable amount of time - depending on how many instances need to be updated. Is it possible for us to have a progress bar (a progress bar! NOT A SPINNER) so we can see how many (not as in a specific number, but as in a rough portion, e.g. 25% of all) changes have not yet been saved?

Viewing document color swatches in the color picker is impossible on a notebook or smaller monitor (zoom setting). Allow us to close blocks of functionality on the color picker or allow us to rearrange them more easily. It’s incredibly inefficient and time-consuming to have to scroll down to select a color every time you select an asset since most colors are cutoff.

Show more than 3 users in multiplayer mode (plus the dropdown). There is plenty of space in the toolbar to show more users. Having to open the dropdown and scroll while changing between what user I am following takes too long.

It would be helpful to create instances of “…See More”, “- By John Doe”, or “WARNING” to be able to prepend text styles without having to go into the component manually. Being able to prepend text would be especially helpful in the context of when we need to provide a desktop-level of information in a mobile setting. Right now text syles depend on the visual aspect of the text, but to be able to prepend would add context and ease of workflow without having to change Text Styles every time a component’s text variable is changed within a modular setting.

I sometimes use FigJam to make shareable slides or documents. When doing this, I wish there was an easy way to export each of these files separately in one go (instead of as one file) - and more importantly, that I didn’t have to manually re-name each file from the FigJam board’s name to the section’s name.

I think this has been brought up but reposting just in case. Would love to see this addition for QOL. It would be great if when you hop in to edit a gradient, that you could quickly rotate the direction by 90°. Dragging the handles around is fine when you need a custom angle, but 9 times out of 10 (for myself and others I’ve spoken with), we just want to flip the direction around a couple times. 🍻

When I go to the billing page and see the breakdown of the new seats added to the billing. It’d be nice to see a list of who these new seats belong to.

It would be awesome if we could override and choose a different variable in an instance of a component! Here’s another forum post that asks for the same thing but it’s not tagged as “share an idea”. Possible to override variable value within component instance? Ask the community Is there anyway to override a variable value set in a component the way you can override other component properties? I am trying to make a prototype which illustrates a “like” button with a count update on click. Here is how I have set up my components and variables: [image] The issue of course is that all of them change at once in the prototype like this: What I would like to do is to override the starting counter value on each instance of the like button so that: clicking one…

Please prevent accidental creation of untitled files. I’m constantly having to clean up empty “Untitled” Figma files because it’s so easy to accidentally create new empty files in the Figma native app. It happens when you click cmd-N in the app. The result of cmd-N depends on whether you are in the native app or in a browser. When you use Figma in a browser, cmd-N opens a new browser window. When you use the Figma app, cmd-N creates a new file. In the app it’s easy to create unwanted files by mistake, requiring clean up at some point. I don’t mind closing a newly created file right after accidental creation. What I do mind is that the empty file is saved, leaving me with the chore of managing the debris. Suggestion: If a file is created and closed before it is renamed or modified, delete the file. I’m definitely not the only one with this issue. I’ve seen suggestions, but no solution. Anyone else out there wanna vote this up or help it get attention some how? Thank you!

I would like to be able to use variables to set these image adjustment values:

Currently, I am not able to use a color style from a library as a color variable value. I know that variables are in beta, but I don’t see this capability in the Coming Soon list at https://help.figma.com/hc/en-us/articles/4406787442711-What-Figma-features-are-in-beta#variables.

I have a list of properties in a component that I can change with variables and it works perfectly, the problem arises when I try to change nest instances with the same method, apparently the nest instances are not detected as instances of the component by the variable. I would like that in some future update it would be possible to do this.

In our design system, we’re leveraging modes to abstract things out in components (and even things like typography and color). But we really only want out users to see/use a limited few (themes / spacing in this example). We are using these modes (along with our devs) for component construction / enhancement purposes, but they will never be something end users need to (or should ever) adjust themselves. It would be great if we could control which modes actually show up as options for the consumers of our components.

Working on Adobe files, people usually advise you to use Font Management tool such as Suitcase Fusion or Font Explorer. This is because fonts weigh a lot and this can be irritating when working on heavy files. Though for UX point of view, custom fonts are always better for larger viewers but as you go further into more creative clients, specific and well designed fonts can be very useful for design point of view. Just a suggestion, it would be nice to have this tool for Font Management rather than installing fonts into the system i.e Font Book. If anyone has a solution, it would be great to hear how you guys are working. Thanks

I’d like to share some insights about the new variable feature. For highly interactive prototypes, storing states in a string is a very practical approach. This method allows the state of an interactive component to switch based on the string content. However, a feature that seems to be missing is the ability to conditionally display or hide a layer based on whether a string variable matches a particular value. More broadly, there is a need for the capability to bind expressions to each property. For example, one could bind the visibility of a layer to whether variableA equals “state1”, or to the inverse value of a boolean variable, booleanA. In addition, the introduction of the “mode” concept is incredibly beneficial. I view it as an object where each mode corresponds to a key. The values of different modes can be used in the “set value” interaction. However, it seems that you cannot specify which mode you want to set when using the “set variable” interaction. I believe that with thes

It’s convenient to often close the left pane given both left and right panes take up so much screen real estate, especially on a laptop. If the asset name was viewable and editable at the top of the right pane as well as the left, you could work with one pane only saving needed space.

So I’ve been making some geometric shapes, and it was a bit painful to do because there are no middle points for shapes. I tried to connect the lines to the middle of the circle. The 2 solutions I found were to: Create the middle points manually; To use shapes with strokes and then add the circles. I think making these middle points will improve the workflow in geometric design.