Share Your Feedback

If some layers in my component are currently assigned to a boolean property, Figma now blocks my ability to re-assign these layers to a different boolean property without first locating every layer with an existing property and removing the prop assignment. This is incredibly frustrating, because there is no easy way to select these layers. I instead have to dig through (potentially hundreds of) layers to figure out which ones have properties so I can remove them, then use multi-edit to assign them all to the correct new property. This could be a quick thing for Figma to fix, by means of a couple solutions:Allow re-assignment of layer properties without having to first remove existing assignments. Make it possible to select all layers assigned to a property. This is already possible with variants — I can click the button next to the listed variant to “select _ variants.”Here’s an example of my current experience:After merging variants fr

‘Absolute position’ is now called ‘ignore auto layout’, ‘space between’ is called ‘auto’ and there are probably a few other settings that Figma has applied its own naming to.Why?It’s bad enough that layout and styling in Figma does not behave like CSS and HTML in many cases, which means that we have to completely rethink our approach to design. Now we have learn new terminology as well.Even for somebody who doesn’t know CSS, I would assume that it hardly makes any difference which term they learn. It would even be an advantage if they learn the correct CSS terminology, so if they do learn CSS one day (which, in my opinion, would be highly beneficial), they don’t have to learn new terminology for everything.If I could make a wish, it would be to please align terminology and behaviour between Figma and real-world CSS wherever possible.

Hello Figma team,Thanks for this beautiful solution.Just want to say that is in the title.  

The keyboard shortcut to Zoom to 100% is quite uncomfortable. Hitting Command + 0 is just so unnatural, it requires both hands, or moving one hand to around mid-keyboard to use the other Command key and the 0.I know this is pretty standard, I don’t really blame whomever made the call.Now: 1) you cannot edit the shortcut with macOS’s Keyboard Shortcuts feature (I can’t overwrite it to ⌘1), which is quite lame, 2) nor can I set it up within Figma’s Preferences. This could be a very cool addition. Let users choose keyboard shortcuts.To be fair, having ⌘1 go to the Home tab in Figma makes no sense. Why would I want that easy, comfortable shortcut to do that? I barely go to the Home tab.Anyways, I hope this can be moved up the chain.Thanks.

If I have an item or component and send it to a different page, it often takes me several minutes to figure out where it went. 

Figma just added an icon to collapse all layers. A thing that has existed in keyboard commands forever. but once again...they did not provide the reverse. Ability to expand all layers. why does Figma only do anything halfway? maybe instead of focusing on things like silly “FigPals” they could work on the million half-finished shortcomings in the product? instead of a cute temporary bunny, I would like to be able to control which properties of a nested component are adjustable. but Figma is making play toys. this is what my enterprise team license is getting me. 

This is great! Thank you very much!Also measurment  

I would like to learn about User interview questions how to prepare, can some one help me with the suggestions to create the launguage learning app ??

This new pricing model for Dev Mode $35/seat/month just to inspect already finished designs is so out of touch with reality, I have no words. We have an enterprise Figma license and we capped Editor seats to a minimum because it’s hard to sell to C-level. This limits UX maturity and spread of Figma usage in product development across the whole org. We have about 4x as much full-stack developers as we have designers, who OCCASIONALLY need to inspect designs. How the bleep are we supposed to sell those seats to C-level executives? This is completely unrealistic and limits not only spread of Figma usage, but design-led product development in our org even more. If we are to keep Figma, all of our designers are left with one option, to extensively micro-document each design for devs to read as a book. Losing huge chunk of our UX time. What a self-destructing pricing strategy from Figma. What do we do now?

A tiny tiny detail that would make life a lot easier would be auto-tabbing the cursor’s focus to the search bar when I switch from “Custom” to “Libraries”. 99% of the time when working in a large design system I need to search for the colour/variable I want, there’s too many to scroll through. But I always have to make that extra click into the search bar and I often naturally start typing only to realise it isn’t tabbed (accidentally pressing shortcut/hotkeys along the way).Whereas you compare to the File/Asset content switcher it DOES auto-tab once you switch into Assets so its not consistent.Small interaction would save a lot of time! 🙏

We used to have annual seats for our own staff, and use monthly seats for adhoc collaborators - but with the new billing system Figma has changed everything to annual seats, making our total expense explode! It seems there is no way to degrade an annual plan. Only a way to grow, and feed Figma’s greedy pocket!

The cursor is entirely too small now and feels extremely latent at the new angle. Please, Figma, don’t fix something that’s not broken! The cursor is a tool, not a pointer.Also the addition of light fields on a dark background is fairly disorienting and clutters the surroundings of all info inside the fields. Slows down workflow and makes info less “glance-able”.

it’s really really not convenient for me 

The status on sections for ‘Ready for dev’ are great but it would be really useful if we can have more or the ability to create custom ones for the design phase. Working in a client environment it would be hand to have the ability to mark a section as the ‘Approved designs’ with a date stamp. other useful ones would be ‘On hold’, ‘Shortlisted’ and ‘Archive’ but the ability to make our own would be brilliant. Cheers. 

Oh my godness.I’ve tried a new version of figma slides and loved it so much! The possibility to download presentation both in PDF and PPTX is the state-of-art feature actually. Collaborating killed me because it’s basically stunning. Templates are fire too!!!I’ll never use anything but Figma slides.Thank you Figma Team for creating this! Have a nice day!

There are a lot of great adjustments and logical changes within UI3, however one of the main reasons I’ve still been using UI2 is the floating action bar.Can we get an option to dock this to the top of the screen or put it elsewhere? I use hotkeys for all of these actions and it’s kind of distracting in the center bottom of my screen with a dark background that keeps drawing my ADHD brain to focus on it when it’s not important to actually building designs.

I saw the update, “We updated the file browser to create a more consistent and seamless experience as you use Figma products.”I have too many files in projects -- I need the List View to skim them fast. This change does not make a more consistent and seamless experience, it’s slowing me down and making it much harder to find the files I need. Please bring this back, this is impeding my ability to find things.Is there a plugin I can use to get my list view back?

I just noticed something while transitioning from UI 2 to UI 3, and I’m wondering if others feel the same.Earlier, when using the K (Scale) shortcut, the focus was set in a way that pressing Tab would quickly take you to the width adjustment field. This made it really efficient to scale objects while maintaining precise dimensions.Now in UI 3, pressing Tab inside the scaling option focuses on anchor points first and seems to stay within that section instead of quickly moving to width or height. This small change makes scaling a bit less efficient for me since I now need extra keystrokes to get to the fields I use most.Does anyone else find this workflow slower? Or am I missing something? Would love to hear thoughts from the community!(Figma team, if you're reading this, it would be great if we could have the previous tab focus behavior back!) [Attaching screenshots for reference]

As in the title. Either I will stay longer at work to do my job or I’ll change to HTML/CSS completely. Want to help? IMPLEMENT TABLES/GRIDS, NOT CRAPPY UI.

Some floating window panels in Figma are too small. For example, the color panel. I've created some color variables, but every time I want to select a color, I have to use the scroll bar to find a specific one. It's really exhausting because selecting colors is a frequently performed operation. Why can't we increase the height of these floating windows?

When I serach for a file on the home page, this research among the entire files contents (which is good). But this search algorithm do not prioritize file name it self. For example, if I have a clear match with the file name (meaning search = “ABCD”, filename = “ABCD - Project name”), this should be displayed at the top.

DOnt know why figma must hide propeties and the most of time user have to expand it to continue. Bad ux and create many annoying 

Hey, just wanted to bump this thread, as it’s been 2+ years and this issue still persists. It’s annoyin as hell and requires to create unnecessary wrappers just to eliminate this problem.Solution: I’d expect the swap component property to only affect the component itself, not the particular variant of it. Therefore I could set multiple Slots to be of a single component type (eg Button), then fine-tune their appearances slightly via that component variants (eg Button: Primary | Secondary | Tertiary etc.).

Please tell me if I'm just too used to something else, but this doesn't feel intuitive. It doesn't look like a button, let alone something clickable. I spent days trying to figure out how to bring the properties of a base component into the parent component.Additionally, I have to hover over it to even realize that applying the variable is possible—there's no visual indication of it. You need to hover to discover it.  

"Regarding the page names on the left side of Figma, when we are building a component library, each component may have updates. We hope that there can be a tag next to the page name to indicate the 'updated' status. Is it possible for Figma to implement this in the future?"