Suggest a Feature

How about adding a Comment type-“Approval”, for an audit trail of all designs signed off by stakeholders/clients. This then tracks the approval process of designs/screens and takes a snapshot of the design when the approval was done. Link this feature to the same before/after feature you have created in Dev mode, and you’ll have a nice tracker of approvals and iterations/enhancements in designs. Design Approved [screenshot] Design enhancement approved [screenshot now vs last approval design] Yes? 😉 Yes!

There isn’t a way to share a presentation with speaker notes. I need to share a presentation with stakeholders who don’t know how to use Figma. My presentation relies on speaker notes rather than text on the slide but there’s no way to share speaker notes.

I use chrome and because of a bug in another application I had to disable hardware acceleration for the browser, however, I can still use Figma on the app everytime I need to, except when I get a link. When I get a link, it goes to the browser and shows me a message that says that the hardware acceleration is off, and stops there. I would love to have a button below to open the same link in the App, since that what I actually want to do.

Introduction of floating panels was a great starting point for the ability to move the panels around. Would love to be able to do this, especially to create customized layout containing plugins and widgets.

Hi there! Just wanted to share that for almost all my use cases, when i change the line height through the shortcut, it increases or decreases into a fixed value (like 42). This means that when i change the font size, then I have to adjust the letter spacing again. It would save me quite a bit of time if the shortcut worked with % percentages. (120%, 150% etc.). Especially for text boxes where the value is originally set to Auto. Thanks so much! It’s such an easy fix, like a 5 min low hanging fruit pastime, something to give the intern! I hope someone can take care of this!

I find annoying to se the dashed preview of sliced elements, in a FigJam file. Like when add a screen or the single component of a library to them.

Some of the suggestions offered in the code of Figma was not ideal to implementation. We worked around the box shadow and found issues with a transition of slideIn and slideOut because the box shadow would be delayed to transition with the body of our third party tool. Via some research, we found that applying a dropshadow solved out transition issue. I suggest that you highlight that the developer mode are recommended styles and provide contextual support of alternative styles one can use to solve their QA issue.

There are many situations where I need a card or a blocked element that can contain multiple components. It has its own auto-layout settings, but I have to reconfigure these settings every time I use the element because I can’t create a reusable component if I need to add more items. It would be helpful if specific components allowed adding or removing elements to create more complex layouts (Open components). A classic example is the settings area, where multiple form fields, buttons, and options can be included based on the context. I believe the main issue is that there’s no way to save an auto-layout configuration without converting it into a component. Thank you

When clicking in the input field for the stroke-width there is two bugs: the number doesn’t get highlighted. In every other input field, the value gets highlighted and when you write the new value, it overwrites what was there initially. This should be consistent. Right now this stops my workflow a ton of times. When the stroke-with input field is active, there is a very large padding making it impossible to see more than two numbers. So if your number is 10+ or has decimals, you can’t see what the full number is anymore. See screenshot under.

At a grid level or somewhere else where we could toggle to turn on a heat map per device frame. An old article but still relevant:Smashing Magazine – 19 Sep 16

At the moment, pressing Ctrl+D on a main component will create an instance if the original component does not have variants. If it has variants, Ctrl+D will instead create a second main component with the same variants (as do Alt+Drag and Copy+Paste). While this reflects the functions that I use most often, I also want to do the other from time to time: duplicating single-variant components or instantiating multi-variant components. All other ways to achieve this currently require lots of clicks and/or typing. It would be really helpful and imo intuitive if both actions were possible via the context menu (right-clicking on the main component).

If component properties could be assigned as variables to components within them in the same way variables can be it would reduce the amount of variants of parent components. Example: I have a table in which each each row is a component with variants ranging from 3 columns to 10 columns as well as a header component constructed in the same way and a total row that is fixed. The rows are then placed within a component, where you can select the number of rows, one to eight. In this set up the parent component has 64 variants. If the parent component could have a property for a number of columns that could be used as a variable by a nested component it would mean that the parent only needs 8 variants. It would also make it easier to change the properties of components in another component where they should match, say you have a status box component that contains a number of child components, one is an icon that can either be a thumbs up or a thumbs down, ad another component that is a col

Im in the process of merge libraries and move colour variables over to a nother varaible schema in another, currently there is no visible indicator (at this level) to show which system each variable is coming from (i have to click on the variable, open the library picker, scroll to the top of the list of variables to see the source). Please surface this information higher up the hierarchy(perhaps a tooltip on hover?)

Just got UI3 today. Contrast is far too low on icons in the Layers panel, grey text in the Styles panel, and input fields, buttons, etc. RGB values of 245, 245, 245 are not dark enough compared to 255,255,255 white values used for the UI. Please darken that colour further. I was able to get every problematic grey shade in one screenshot. This needs to be dramatically improved for the sake of usability.

Allow to create sections for single object. It’s very common case. Add auto-layout functionality to align objects inside section. Now we use plugin “Screen Organizer” to make all margins consistent.

It would be great to be able to set the REM value per frame/section too. If the default REM is set to 16 px it would be great to be able to side-step that for a section that is mobile frames for example. One option could be to be able to change the REM value at the code settings, and change the value. It would also be a great feature if the variables would be possible to add math functions. For example that a [variableA] = 3*[variableB]. I know there are plug-ins for that but if that would be part of the basic FIGMA feature regarding variables.

A pretty minor thing but with the newer UI3 update it feels less obvious that I am dev mode. I spent some time trying to troubleshoot why I couldn’t rename a Figma page only to realize I was in dev mode. I don’t feel like its obvious enough that I am in a different state. Part of it might be because the dev mode toggle and tools is now at the bottom view and a little out of sight. Or maybe some things outside of the canvas should still be editable like the ability to rename Figma pages?

There should be a way to see your colleagues within FigJam. Hey Figma, does this exist already and if so, am I out of the loop? If not, is it on the roadmap? I just want to see the people I’m jammin’ with, ya know?

As Figma has recently updated its UI3 to use fixed side panels (which used to float), I for one would love for the top bar to be back in its place… which would also mean that the now hidden boolean operators and component switches (or any other submenu for that matter) would no longer be hidden (red squares in this screenshot). Apparently the user base isn’t ready for an interface that floats… nor am I for a floating menu on the bottom. It really is only a few pixels loss in the total height… but improves on usability a lot, because the submenu’s (red again) aren’t hidden under some icon somewhere… but can be used right when you need them. And you can do that with a lot more components. When I select two objects: When I select a text: Which in UI3 was hidden behing a submenu. Wouldn’t it be nicer if all those options were all in the top bar!? Or better yet… a combination of the two? On central menu for contextual tools… and full options still in a dropdown menu. Hidden in three dot

When working on multiple files at a time -the old UI with black header was much easier to differentiate b/w Figma and fig jam files. Now, I have spend 4 sec to look for the exact file I want to click on.

As a design systems designer with a Design team of 75+ designers I want to bulk swap an entire component library with a similar but updated library So that when I’m syncing Figma Libraries between two or more separate Figma Organizations, I can easily replace a whole component library at the library level instead of needing designers to swap libraries per Figma project file. This feature would use some existing workflows and interfaces for choosing, comparing, and merging/swapping components in bulk. This swap should be treated as publishing a new update to the existing library and still require Designers to “accept” the changes. New components or existing components with a different name, should be treated as introducing a new component into the library. Open Questions: How are new components handled within the updated library after the swap? How are design elements that aren’t components handled within a library swap? To give a specific example of how this scenario appears. Organ

I have sure the most Figma’s users separate their assets in a page called by “Assets” and cant link the interaction “navigate to” to a component to another frame in the main page. Please, vote to Figma’s team add a way that we could use navigate to on a component in a different page from another.

Hello! When a stakeholder leaves comments on a design, we make changes that involve adding/removing sections, changing their heights, etc. What this does is that now, after I’ve made the change, all the comments underneath that change haven’t moved, but the design has changed. Just like comments move when you move the whole artboard, could we not have comments move inside an artboard when sections disappear? If a 300px section disappears, all comments underneath that should move 300px up, to ensure that all comments stay placed on top of where they were intended to. Otherwise, you end up with a lot of “I don’t like this, can we change it?” on top of something it was not meant to be on top of.

Double clicking the edge of an element to change its width/height property is neat, but finding and clicking edges can be error prone and finicky, especially with nested objects. It’s also hard to remember which property is for regular double clicking and which is for option/alt. It would be super convenient and fun if I could just hit w or h to cycle through hug, fill, and fixed. Easy to remember, easy to execute.

As a user… 😁 I wish I could set the default styles per Figma elements separately. For example: Text will get a grey fill The square will have a different grey filling The section will have a green stroke with a 10px stroke etc… Who is with me??