Suggest a Feature

Now that I can set visibility with a variable, I would like to have the ability to defined a transition for the visibility of that item. Then I could flip a variable to turn on or off a UI element and have that element transition onto the screen. (slide in, slide out, fade in or fade out). Without this feature, I have do some crazy work arounds and given the limitation of variable interactions on a nested component… it is a pain in the… workflow.

Allow the Autolayout Horizontal and Vertical gap to be defined by a variable. A use case is changing from a list view to a card view. They both use Autolayout, but the gap distance is different for the rows of a table vs cards. This might also be useful for making components responsive to different screen sizes.

I have an idea for your software that could really help us out. In our team, designers and product managers often put their designs and project plans in the same file, and then they give this file to our engineers. This leads to a lot of discussions between the people who work on the front-end and back-end of our projects, especially when they’re writing the specs for our APIs. The problem we keep running into is that when we’re working on these files, it’s really easy to accidentally mess up the design files. We don’t want that to happen. It would be great if engineers could look at the designs and add their own notes or comments without being able to change the original design. So, my suggestion is: can you make it so that when designers hand off their files, the engineers can write on them but not edit the actual designs? This kind of control over who can do what with the files would be a huge help when we’re putting together our project plans. Thanks for considering my idea. I thin

If I have edit access I use the Rect tool to sometimes measure some distances/relationships between objects. When in view-only access this is not possible, so I have to figure out distances in a round the houses awkward way, this is terrible for pixel perfect implementations. Maybe it would be enough if the marquee select would show its coordinates/measurements, but a dedicated Measurement tool would be best.

Hi! I would love the ability to “Detach All” instances within a selection. How it would work: Select an object(s), right click the selection, and click ‘Detach All Instances’. Anything that is a component or instance within the selection would turn back into plain objects. Why: I prefer to use Components throughout my page designs and I also turn each of my pages into a component. So lots of layers of components. My developer uses the Figma to Webflow plugin, which requires NO instances or components on the page. At the moment I have to make him a copy of each page and manually go through the layers to detach everything. Would be nice to make him a copy of the page, right click, and ‘Detach All’ instead. Happy holidays from Pennsylvania!

Would be great to be able to set Z index value. (In line with what is available in CSS)

Recently, there is no option anymore to open the prototype in a new tab. Since I’m always switching between those two views, I have to open the prototype, copy the link, open a new tab, insert the link, move back to the previous tab and go back to the file. It’s also not possible to STRG+click it to open in a new tab or open it with a right-click in a new tab. → opens in same tab Does anybody experience this as well? Is there a setting where I can configure the behaviour of the play button?

When I’m adding comments to a mind map, the comment is not “Attached” to the node I’m commenting and when there is a change to the tree, the comment is misplaced and often we lose context. Because mind maps are so dynamic, it’d be nice to allow not losing the comments. Also, it’d be great to turn comments into actionable items. I already do this with stickers, but i think you could easily productise it from within the comment.

The ability to bulk choose the variable value for all modes when adding new variable. E.g. create variable > color > select color > apply to all modes

it would be nice to have a function to collapse all layers at once!

Spelling mistakes are shown only if you open the text editor, which means, that when I did a spelling mistake in a text but got out of the current component, I will not see the red line anymore, and will not notice this spelling mistake, this cause our team problems during execution, and basically caused spelling mistakes in production.

How to read it using Plugin API?figma.com Thanks

Is there a way to convert custom spring specs to cubic bezier values?

I think making this feature would be like opening Pandora’s box since itd absence is quite limiting and promotes redundancy. I built a menu. I add once instance of menu-item inside. Now I can multiply the number of times that item is shown. So one contextual menu, for example, can have 2 items while another, with the same component, can have 10. While people currently workaround by having dozens of hidden items, this is not optimal and leaves us with a “dirty” feeling.

We are using FigJam for our user research. In Jira and Confluence, I am adding links to stickies or sections in FigJam in case more context is needed (one Jira issue can have multiple links). This way we have backward traceability and can dive deeper with selected users as we flesh out the user story. It would be awesome to have backlinks appended to the linked Sticky automatically so we have traceability the other way, and can make sure all important feedback is captured. “Create a Jira issue from sticky” does not work due to the many-to-one relationship. Ideas welcome! If this is doable as a plugin will be happy to explore.

Hi, Just recently I mispressed a shortcut from Ctrl+A to Ctrl+Q, and I’m surprised that Figma immediately closed the whole app. At first I thought Figma were crashing, but I tried the button again (Ctrl+Q), and I find that it is a legit shortcut. I don’t think this shortcut belongs to Ctrl+Q, we should replace it with other key combination. Thank you for reading.

It’d be great if I could set an option in Prototype mode to scroll to top when a component is clicked in a way that it works on any screen. Currently you need to choose a specific page you want to scroll to. Example of use: scroll to top arrow that works on all screens in my prototype automatically.

We often have the problem that we don’t know how many items we should include in a component, for example a toolbar. We often end up adding some hidden extra buttons. This works, but it has some really annoying downsides: We have to guess a good maximum number of items We have to detach if we want to add more We cannot handle separators in a good way, other than adding them everywhere and hiding them It’s way too difficult to reorder items I suggest that autolayouts can have a property that allows for adding more items of a specified type (with reordering). Then we would be able to make our components much more simple and flexible.

Hey Figma, I really love your tool but constantly rearranging frames manually, especially in large projects, can be quite a hassle. Any chance of an update where duplicated frames maintain their sequential order? It would be a huge time-saver for designers! Here’s the video about this topic.

When accepting updates from a library into a working file, I would like to know which components/screens are impacted by the accepted updates. Maybe highlight in some way what changed, so that I can guarantee that nothing broke in my design work.

Please add a new feature so I can rename the text without having to double-click the text. Because sometimes I have the text behind another layer and I don’t feel like bringing the text to the front just to rename the text. I think if you click on a text layer, the design tab should have an input box I can type in to rename the text.

Hello Charly, I use Figma extensively for UI design. I find it quite unfortunate that the Figma interface is not very aesthetically pleasing. I would really appreciate having a beautiful, modern, and intuitive Figma interface with rounded corners, a nice dark mode, shadow effects, and more. Thanks Charly

The local variables table is the closest thing to a data object in Figma. It would be great to assign/change a mode through interactions, for example: onClick-> changeTo → Mode “Theme2”

Cmd/Ctrl + Shift + Z: Redo last action doesn’t redo input field calculations. It would be much faster to redo than to each time do the calculation. eg. when I use the golden ratio, I multiply repeatedly with 0,9045 - so after doing the first calculation, I would love to be able to then just use the keyboard shortcut for further repeats.