Share Your Thoughts

How often do you are using Figma while browsing the web for ideas and want to get some colour in Figma? Or have reference software open and you want to just use the same colour? Eyedropper could just let you do it but unfortunately, it is limited to the Figma window currently, meaning you need to get a screengrab or copy the image, paste it to Figma and then pick the colour. Photoshop have this and it’s one of the first things I noticed missing from Figma.Photoshop Training Channel – 6 Feb 17

Artificial intelligence companies are transforming how users interact with digital products. From personalized recommendations to intelligent chatbots, AI is becoming a core part of modern UI/UX design.Designers now face a unique challenge—creating interfaces that not only look great but also support complex AI-driven functions. It's no longer just about static screens; it's about designing dynamic systems that adapt, learn, and evolve with user behavior.As artificial intelligence companies continue to push innovation, UX designers must consider how to maintain trust, transparency, and simplicity in AI-powered experiences. Whether you're working on voice interfaces, smart assistants, or predictive dashboards, your role in shaping the future is more important than ever.

First of all, STOP hiding important values like dimensions from me in place of an auto layout value. This is the biggest annoyance I have with the new design. It’s like you tried to simply things, but now the whole UI feels more cluttered and busier than ever.The fact, I have to stop concentrating on what Im working on and move my mouse all the way to the side panel, and then PRECISELY hover a tiny rectangle to get a fundamental dimension, is so unpolished as an interaction. Don’t hide dimension values!!!

I would like to be able to drag and drop the export preview and move the dragged asset directly to my Downloads folder in the dock (macOS) or my knowledge base tool. It’s easier than open the dialog, choosing the destination, reusing the image from that destination.

I would love the ability to expand the “Review Updates” modal into a full-screen view so that I can more effectively check library updates in detail to understand all of the changes that will apply and more easily compare current-vs-updated for each component instance

There’s a need from our engineer partners to maintain versioning of components within Figma. Right now, this process is SUPER manual. The Designer has to maintain a version number within the description box, for reference. And when making changes, we then have to update the description version number, and then secondly add that same version number to the dev ready notes so they can see it in the Ready For dev section (which is also hidden when opening dev ready under “Compare Changes”). It would be amazing if there was just an automatic number 1.0.0 applied to the component when marked ready for dev in a library. And then it could be a button for the designer to determine which type of change they are making and just add the patch number and maintain that so dev can see that and the history of that change. 

Hope I can change the annotation’s position: left, right, top , down

Can we add an ability to more easily filter or scan a list of users in the share/access panel? It would be really nice to bubble up who is an editor vs viewer, who is external vs internal. :) Thanks!

It would be great to set Variable/property to a value like height. This would help us change all the values in our components at the same time. Imagine you have a list component, that includes 5 titles with the same height and width that are valued by variable, if you could add variable/property to their height, you no longer need to create their different sizes, you could control their size by property.

Every time I exit Figma and come back, the previously selected sort order is lost, and it defaults to "Last modified" – "Newest first". Previously, the selected sorting option was always preserved.

It would be great if the Layer and Properties Panels were adjustable because they get in the way of me seeing the artboard/screens that I am working on. Another thing is that when I close these panels, I can no longer see the comments that include feedback or edits that need to be made on my screens. Because of this, in one view I can see the comments and everything, but can barely get to the screens on the artboard to do anything about it and on the other, I can see the full artboard, but not the comments. Both options are frustrating, especially since I’m just trying to make some edits. Therefore, I suggest making the Layer and Properties Panels adjustable so that they don’t get in the way and allowing the comments to be visible even when the panels are collapsed. 

In Figma slides when you click on a group of slides it's not clear which slides are in the group. Attached is my solution. So the darker blue with the blue text and icon is the slide the user is on right now. But the slides in the lighter blue with grey numbers are slides in the group but show the user is not currently selected on those slides. 

Enhancing Scroll Bar Visibility in Figma PrototypesOverview: When designing prototypes in Figma, having a visible scroll bar that appears automatically during vertical or horizontal scrolling can significantly improve user interactions. This basic affordance helps users understand that more content is available beyond the visible area.Steps to Implement: Visible Scroll Bar: Ensure that the scroll bar appears automatically when users scroll vertically or horizontally in your prototype. This visual cue indicates that there is additional content to explore. Formatting Scroll Bar Appearance: In the property section of Figma, you can customize the appearance of the scroll bar. Adjust settings such as color, width, and style to match the overall design of your UI. Benefits:Improved User Experience: Users can easily navigate through content, knowing that there is more to see. Consistency: A formatted scroll bar that aligns with your design ensures a cohesive look and feel across your UI.

This is one of the most baffling decisions in UI3. When you have an existing component, you’ve kept the exact same icon as UI2, but changed the button’s functionality. I’m constantly accidentally creating a new component, when I’m trying to go to that component. Please, when you have a component selected, hide this action in the ··· menu. There’s no reason for it to be one of the primary actions. 99.9% of the time when I have a component selected and I go to press this button, I’m actually trying to go to that component. Now that functionality has moved to the folder name, which is very confusing. But at least removing this button from the primary action menu next to the component name would help.

I’m tired of managing multiple files for just one thing. Nedd a a feature like this, where I can open all the file type in one file instead of manging multiple files for the same project.

It would be great if the Color Contrast Checker could also work for variable. I had to disconnect my variable or style just to check the contrast ratio.

1. Describe the problem your experiencing Our design file has 50+ comments across various projects at any given time. As a designer, it’s noisy for me to see all comments instead of ones just on the page that I’m working through. Suggested idea Filter visible comments by page.

Hey folks,I’ve been using Figma AI lately, and honestly… it sucks. I had high hopes – I mean, AI in design sounds like a dream, right? But the reality is far from it. It’s clunky, barely understands prompts beyond surface-level UI, and ends up creating generic screens that I still have to completely redesign.Instead of speeding things up, I’m spending more time cleaning up AI-generated junk than I would if I just designed it from scratch. It feels like a beta version of something that might be useful one day… but it’s definitely not there yet.Has anyone actually had success using Figma AI in real-world projects? Or are we all just nodding along pretending it’s the future when it’s really just a waste of time?Would love to hear your thoughts – maybe I’m missing something?

Hi all! I would like to share with you this question with the community, as I have been researching a bit and found nothing. I saw someone shared before this question, but there was no answer and the feed is closed now. [Change "Reset all changes" to "Reset specific changes + drop down menu"](https://Link to the post). ----> Please, read this one for more info. It would be great to hear if anyone has any trick that allows them to reset all changes, without reverting the text content to the original component one. Any tricks or solutions that might be already in placed? Thank you!

Hi, Is there any option to automatically sort the items/components in the variants menu? Seems like I can drag them and drop but while having lots of elements it’s quite hard to keep things in the correct order. I know there are plugins to sort items in the layers menu (like SortIt) but would be great if there is an option to make the same (A->Z, Z->A) for the variants. It will make life easier.

The new DevMode annotations tool is Awesome!!! Having lots of annotations tends to clutter up the screen on the design side, however, and it would be nice to be able to toggle their visibility on and off like with comments or multiplayer cursors. I had assumed that hiding comments would hide these as well, but such is not the case.

It’s rare that I use groups, but I do have a doc with a dozen variations on a layout in a frame that I had grouped to hide the frame names on the canvas and I was surprised that when I selected a child frame in one of them, Select Matching Layers returned “No matching layers to select” for what should have been matches for the other child frames of the frames in the group (and do match if those parent frames are ungrouped).I would expect Select Matching Layers to work the same way in a group as it does for a section (where matching children are found, but limited to within just the parents in the section). I guess I’ve always considered the contents of groups (and sections) to be a “loose” collection compared to the “rigid” collection of the contents of frames.

First of all, it is very neat to have this feature in Figma, it made me switch from our company standard (powerpoint sighs) to Figma Slides (or is it Slide Deck?). The possibility to add interactivity, such as polls, is great! And sure, removing the background, changing mode (dark/light), is very neat. But, we are still designers. To put it into user stories: As a designer I want to be able to change the default font and theme colours for a slide deck (after all, we are all bound to use templates we didn’t design) As a designer I want to be able to style the poll components (and to hide components I don’t want to use, such as vote count) As a designer I want to create my own templates As a designer I would like to import powerpoint/keynote template files (which of course I have to tweak in order for it to be correct)

Problem:The annotation customization feature is limiting and does not preserve category settings across files, nor does it allow for standardization of categories within an organization, requiring users to have to re-author custom categories for every file. Solution:Allow users to choose between the standard customization categories or an organization-approved set of custom categories. This could be set by an administrator, or something that can be published from a central approved library. And/Or allow individual users to preserve custom categories between files.Suggestions:Allow for custom colors to be used for categories. Provide an option for numbering of annotations (numbering will help with accessibility annotations, including: page landmarks, reading order, heading order, focus order etc.). Allow for more robust text editing within the annotation, including: addition of rows to organize information, adding clickable links for developers to refer to developer documentation (secti

You can use the scale tool (K) to scale a component which is good. Problem: Once I used the tool, the scale of the component is reset to 1.Solution: Add a property to components that show and let you set the scale of it. See image attached.Mockup of Scale component property