Suggest a Feature

It’d be great to be able to mix booleans within a property, so that toggling on the Foo property causes A to show, while B hides. Sometimes the state of a component has the appearance of two elements linked, but not always that they both show or both hide, rather that one shows while the other doesn’t.

Hi! Variables work well for prototyping inside a Figma file, but I’l like to be able to use variables that apply within the scope of a component. For example, if I have a component that uses a rectangle with a border radius but the rectangle needs to resize, the border radius remains the same and now the rectangle loses the look and feel that it was originally designed with. Ideally, when I create a component, I could create a component variable that’s value is calculated by some function of the height / width of the component. I’d then set the value of my border radius to that variable. Now, when I create an instance of the component, if it resizes in any way, the border radius changes accordingly. So if I’ve created multiple instances of this component in my file, each instance’s height / width could be different and it’s border radius would adjust respectively.

Calling Figma PMs 👋! How about adding a feature that allows us to easily move and duplicate files between team spaces? 🚀 Figmars, If you agree, let’s show our valuable Vote!💪 Together, we can save designers loads of precious time! 😀

it would be nice if the inspector would list overrideable / swappable nested components without one having to drill down into the component’s layers. This would allow to quickly select multiple components and change an override for all of them. Currently I have to click through the relevant layers of all marked components to adjust the overrides in bulk: E.g. changing an icon override for multiple components.

The marker is very pixelated which doesn’t give a good experience when drawing during presentations and meetings.

When copying a deep link to a frame, section, page, etc. into Jira, Jira reformats the long URL based on the file’s meta data (i.e. the name of the file). It would be nice if the deep link had a unique meta title that referenced the frame/section/page etc. being shared Right now, if I share two deep links to sections (titled Section1 and Section 2, respectively) in a file (titled Filename1), Jira will display: Filename1 Filename1 It is hard to tell if I shared the correct link because it is not specific and appears duplicative. The desired feature would allow Jira to automatically display the following instead: Section1 Section2

Basically, what I would like to see is: a “Retry” option instead of the current “Reload” option. Retrying to show the current mirrored frame would take less time than reloading the frame entirely, especially in big projects.

Basically, what I would like to see is: fr / % length units. I really would use those features a lot.

So i was playing around with figjam yesterday (LOVE THE CAT STICKERS) bc I thought it might be a good place to do collaborative wireframes w/ my team (full-fledged figma still feels daunting to some folks) and i tried some wireframing libraries like Figma - Lo-fi Wireframe Kit | lofiwireframekit.com A robust library of over 100 wireframing components that helps you explore ... I noticed you can import these libraries as stickers, but the components don’t scale nicely w/ layout rules. it just scales uniformly… (which I guess makes sense since they are not vectors) I have been using Miro as “Figma lite” for wireframing with my team b/c its so easy to learn. But it is slow and laggy once you get too many wires on the board. It would be amazing to build wireframes directly in Figjam because it feels so blazingly fast - like the rest of Figma!

I am using the Figma API to deploy documentation links to the dev resources in dev mode. This is a great feature that allows useful, contextual information to be put in front of developers where they need it. The API currently offers Create, Read and Update options… but no DELETE. This makes it hard to tidy up large numbers of dev resources once they have been deployed into a file. Options to solve for this are; do it manually (not realistic for many dev resources) pair the REST integration with a plugin which does have an API to delete dev resources. This seems like an omission (particularly given how its supported on the plugin API) and hard to see how this can really offer the kind of flexible integration opportunities without also offering a delete method. Stale or unreliable links are almost worse than having no contextual information. We are in danger of training developers not to trust them

Can we have a feature that allows you to hit spacebar to preview a project in “All projects” view before I open it? I’m thinking like quicklook that mac has where you can preview a file from the desktop icon without having to open it completely. I find myself having to open up a number of different projects to find a specific one I’m looking for if I haven’t visited it in months and this would save time.

I like to treat my frames the way I build character rigs in 3d, with a single master component as the home screen and nested instances for every group and layer with switches for every state of those objects I want to be able to visualize my entire selection component variants and edit respecting their hierarchy, where I can see how many of the same instance I am editing based on my selection and to navigate all this exposed on the interface, bring to attention with border color the way select works to allow users to jump to that selection. This will enable workflow in which the user doesn’t have to navigate their layers as much to select components, solves the layer visualization which can’t deal with that many sub groups

When working with different teams, there can be multiple changes on the mockup. It would be good if there is an option to create the log each time I change something in a frame. For example, like a widget. Add this widget to each frame; The widget shows a note with the time and date stamp. Then add a comment and save it. Now, when I click on logs, it’ll show me the order in which this Figma file is changed.

Hello, when I have many opened files in Figma, it is very hard to find the desired one. My idea is a button to be created that opens a list with all the opened files. This way it would be easier to open the file you currently need.

Updating components is one thing, but then reviewing the changes is a tedious task. It would be super nice if you could show a short summary of the changes applied to the component. Like a checkout. What I mostly care about is if texts were changed because I could lose hours of work. If you could show something like “text changes=12”, then I would go one by one to check how bad it is If I want. Anyway, you guys really are THE rockstars of product design! You changed everything. Cheers!

As a large organization we’ve run into issues where someone accidentally accepts library updates on a “locked” spec file. A small safeguard would be to have a version history checkpoint automatically created just before a library update is applied. That we can easily revert to a save just prior to the update. It’s a feature that would also be beneficial with branch merging as well. Currently I’m doing this myself, but it’s easy to forget to do so and encourage every editor to as well. Autosave isn’t always reliable at the interval it creates saves and manually creating checkpoints is a buried feature for most.

I intuitively thought it’s possible, but looks like it doesn’t. It would make a lot of sense to implement it I assume though, as many designers including me previously had the styles divided by folders or other way but used styles. Thank you.

sometimes I’m waiting for a thousand years for y’all to publish my components. show a list icon on the publish toast to open a VERY DETAILED list of what exactly is being published.

Inorder to create an interaction for a specific UI element, I have to open prototype panel (alt + 9) and then drag the handle to create the interaction line. As a Sketch + Craft user, it’s damn easy for me to select an element and hit “c” to create an interaction line. Likewise, can we have a shortcut to create the interaction directly without going to prototype panel and dragging the handle. Did you think this is a value adding functionality ? So looking forward for your opinions on this.

When you add an object onto a table in FigJam (eg. stamps) - it will tie it to the table as a whole. As such, when moving the cells around - the stamp will not remain with the content it refers to. My suggestion: Mage the stamp move with the cell, NOT the table as a whole.

When working in a file, the click area next to a file name is tiny. More than half of the time, when trying to click on it (to do things like publish a library), I open the name editor field. It is quite annoying as it happens several times daily when working on my design system.

Hi, It would be great if there could be a FIXED section below SCROLL in the layers for a scrolling view. Sometimes you want to have something fixed, e.g. a specific background, fixed below the scrolling content. It would be like this in the left side layers panel: FIXED SCROLLS FIXED

Here is the use case: I am looking for a plugin to draw user flows. I try a couple of them until I find one that I like. Now everytime I want to use it I have to scroll through a list of all the plugins that I tried (and some that I really hated) to find that one plugin that worked. Needless to say, there are plugins that install color palettes or custom styles in your file, so I’m forced to live with all this clutter unless I erase local storage. Please, plugin management was working fine a year ago. Why fix something that was already good and intuitive? P.S: Searching for plugins in the community page also has room for improvement. It is slow and sometimes it says there are no results before actually displaying results.

Swap overlay’s interaction must be consider «Click outside»

I was about start implementing our typography system tokens and noticed that I cannot, not even one. I cannot set variables to some basic core attributes such as text-size and line-height. The worse is that our system is in REM and line-height is a multiplier (ex: 1.35 instead of 135%). This makes it impossible to implement and use variables in Figma for DevMode, as devs don’t have the much needed token names for reference. I’m also running into issues with colors, where I cannot have an aliased color but also add opacity. I need to define the color twice (–grey-500 and --text-muted), which defeats the purpose of aliasing, which creates design debt on the Figma side.