Share Your Thoughts

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.

Hi @Figma_support Issue If you choose unevenly spaced objects, Figma doesn’t allow you to enter a numeric figure to evenly space these. It does if the objects are evenly spaced though. Example Let’s say you have 3 objects on the canvas, each at different distances from each other and you want to set the vertical spacing between each object to 32px. You need to evenly distribute the objects first then then set the 32px spacing. Solution Cut the need to evenly distribute step by adding horiz and vert spacing inputs fields when unevenly space objects are selected. Mock up Thank you!

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.

It would be nice if a specific gamepad interaction (eg. X-Button) could trigger transitions on multiple components in a frame. At the moment, the first component that reacts to it in the frame (from the top down) will “swallow” the button input, the next components will not receive it. Example: Build a component that has a Change-To interaction (changing its appearance) that is trigged via a Gamepad button (eg. X-Button). Eg, a circle changing from black to red on X-button input. Place that component several times on a page. Run the Present mode and press the button. → Only the first component will react to the button input. The others will ignore it/not receive it.

When reviewing branch changes to a number of components, when you compare current with new you get a choice of either side-by-side or overlay view. Side-by-side view is the default but I usually find overlay the most useful so I switch to this. When I click Next and the compare view of the next change is opened, I have to click the button again to switch back to Overlay mode. when I have a hundred components to go through - tis additional step of reselecting ‘Overlay’ takes its toll. It would be good for the view mode to be persisted.

I don’t know when this change happened but it used to be that if you picked “presentation - fill” the prototype would fill by WIDTH of the design. Now, very confusingly, it fills by HEIGHT. So if you are designing a website, and you pick fill, it will fit the entire page in the view finder. There is a “quick fix” in the viewer where you can select “fit width”, as I’m sure there were a lot of complaints about this, but now, when sending a prototype to someone, you have to add screenshots and instructions on changing Figma presents along with it. Please add " fit width" to the prototype section in the designer BEFORE you are in viewing mode so that the prototype looks correct on load!

It would be great if apple users wouldn’t have to type whole Apple ID account every time they want to log in. I would love if you could login into Figma using your Apple ID as you’re able with an Google Account.

I noticed that in the Component description, there is a proper line break, but it is missing in the version history. It would be very helpful to have line breaks in the version history description, as it is used for the change log.

I’ve had the issue, that when sharing my Figma files with people who aren’t well-versed in Figma, such as clients. They often struggle to discover that they need to push down the divider line between the pages and layers to access all the pages. Additionally, the layers aren’t particularly relevant to them. In my view, there could be a more intuitive separation just like there is now between the layers and the assets, similar to how Framer accomplishes this, for better user experience.

Would be super helpful to also have the option to view the Color (SwiftUI) instead of UIKit. Sure it’s as simple as wrapping Color() around the UIColor, but why not 🙂

Because variables are set at a global level (using local variables), moving components or component sets from one file to another breaks everything, and the local styles must be recreated and relinked in the paste-to location. If Sections or Frames were used as the “owner” of the component variables and Local Variables could be used the same way they are today, plus aggregate all the “Section variables,” then managing variables would be easier, and moving components and their variables would be seamless. In addition to solving for broken variable references, this approach would help organize variables and keep them close to where they are being used.

I always find myself wanting to move my plugins out of the way from my tools. It would be awesome if I could just have my plugins open on my second monitor for use when i need them instead of having to close them and restart them whenever I use them.

Right now objects are updated one by one, so if I want to update 100 objects, the layer panel on the left is updated after every update/creation, and it’s suuuuuuper slow. If there was a function that I could give all my objects to, and then it would do work with all of them at once, and then update the layer panel once. That would be amazing. 🙂

Auto layout is great, especially with the new Wrap feature. However, I find it quite limiting still. It would be incredibly handy if you could add a logic or conditional to a frame with auto-layout. For example, if a frame is > 1366px to run horizontally, but for < 1366px for it to Wrap automatically. This would especially handy for components that have the Fill Container width applied to automatically cascade and fill the frame when scaling down.