Suggest a Feature

Hi! My organization uses components and shared libraries pretty heavily, and sometimes one component’s one variant can have tens to hundreds of instances across multiple pages in a file. In this kind of cases, if I go to the master component, make a change to that component variant, publish, go back to the design file, and choose to Update the instances, the unsaved changes icon (i.e. the icon of a little cloud with an up arrow pointing into it) would show up and remain there for a variable amount of time - depending on how many instances need to be updated. Is it possible for us to have a progress bar (a progress bar! NOT A SPINNER) so we can see how many (not as in a specific number, but as in a rough portion, e.g. 25% of all) changes have not yet been saved?

Viewing document color swatches in the color picker is impossible on a notebook or smaller monitor (zoom setting). Allow us to close blocks of functionality on the color picker or allow us to rearrange them more easily. It’s incredibly inefficient and time-consuming to have to scroll down to select a color every time you select an asset since most colors are cutoff.

Show more than 3 users in multiplayer mode (plus the dropdown). There is plenty of space in the toolbar to show more users. Having to open the dropdown and scroll while changing between what user I am following takes too long.

It would be helpful to create instances of “…See More”, “- By John Doe”, or “WARNING” to be able to prepend text styles without having to go into the component manually. Being able to prepend text would be especially helpful in the context of when we need to provide a desktop-level of information in a mobile setting. Right now text syles depend on the visual aspect of the text, but to be able to prepend would add context and ease of workflow without having to change Text Styles every time a component’s text variable is changed within a modular setting.

I sometimes use FigJam to make shareable slides or documents. When doing this, I wish there was an easy way to export each of these files separately in one go (instead of as one file) - and more importantly, that I didn’t have to manually re-name each file from the FigJam board’s name to the section’s name.

I think this has been brought up but reposting just in case. Would love to see this addition for QOL. It would be great if when you hop in to edit a gradient, that you could quickly rotate the direction by 90°. Dragging the handles around is fine when you need a custom angle, but 9 times out of 10 (for myself and others I’ve spoken with), we just want to flip the direction around a couple times. 🍻

When I go to the billing page and see the breakdown of the new seats added to the billing. It’d be nice to see a list of who these new seats belong to.

It would be awesome if we could override and choose a different variable in an instance of a component! Here’s another forum post that asks for the same thing but it’s not tagged as “share an idea”. Possible to override variable value within component instance? Ask the community Is there anyway to override a variable value set in a component the way you can override other component properties? I am trying to make a prototype which illustrates a “like” button with a count update on click. Here is how I have set up my components and variables: [image] The issue of course is that all of them change at once in the prototype like this: What I would like to do is to override the starting counter value on each instance of the like button so that: clicking one…

Please prevent accidental creation of untitled files. I’m constantly having to clean up empty “Untitled” Figma files because it’s so easy to accidentally create new empty files in the Figma native app. It happens when you click cmd-N in the app. The result of cmd-N depends on whether you are in the native app or in a browser. When you use Figma in a browser, cmd-N opens a new browser window. When you use the Figma app, cmd-N creates a new file. In the app it’s easy to create unwanted files by mistake, requiring clean up at some point. I don’t mind closing a newly created file right after accidental creation. What I do mind is that the empty file is saved, leaving me with the chore of managing the debris. Suggestion: If a file is created and closed before it is renamed or modified, delete the file. I’m definitely not the only one with this issue. I’ve seen suggestions, but no solution. Anyone else out there wanna vote this up or help it get attention some how? Thank you!

I would like to be able to use variables to set these image adjustment values:

Currently, I am not able to use a color style from a library as a color variable value. I know that variables are in beta, but I don’t see this capability in the Coming Soon list at https://help.figma.com/hc/en-us/articles/4406787442711-What-Figma-features-are-in-beta#variables.

I have a list of properties in a component that I can change with variables and it works perfectly, the problem arises when I try to change nest instances with the same method, apparently the nest instances are not detected as instances of the component by the variable. I would like that in some future update it would be possible to do this.

In our design system, we’re leveraging modes to abstract things out in components (and even things like typography and color). But we really only want out users to see/use a limited few (themes / spacing in this example). We are using these modes (along with our devs) for component construction / enhancement purposes, but they will never be something end users need to (or should ever) adjust themselves. It would be great if we could control which modes actually show up as options for the consumers of our components.

Working on Adobe files, people usually advise you to use Font Management tool such as Suitcase Fusion or Font Explorer. This is because fonts weigh a lot and this can be irritating when working on heavy files. Though for UX point of view, custom fonts are always better for larger viewers but as you go further into more creative clients, specific and well designed fonts can be very useful for design point of view. Just a suggestion, it would be nice to have this tool for Font Management rather than installing fonts into the system i.e Font Book. If anyone has a solution, it would be great to hear how you guys are working. Thanks

I’d like to share some insights about the new variable feature. For highly interactive prototypes, storing states in a string is a very practical approach. This method allows the state of an interactive component to switch based on the string content. However, a feature that seems to be missing is the ability to conditionally display or hide a layer based on whether a string variable matches a particular value. More broadly, there is a need for the capability to bind expressions to each property. For example, one could bind the visibility of a layer to whether variableA equals “state1”, or to the inverse value of a boolean variable, booleanA. In addition, the introduction of the “mode” concept is incredibly beneficial. I view it as an object where each mode corresponds to a key. The values of different modes can be used in the “set value” interaction. However, it seems that you cannot specify which mode you want to set when using the “set variable” interaction. I believe that with thes

It’s convenient to often close the left pane given both left and right panes take up so much screen real estate, especially on a laptop. If the asset name was viewable and editable at the top of the right pane as well as the left, you could work with one pane only saving needed space.

So I’ve been making some geometric shapes, and it was a bit painful to do because there are no middle points for shapes. I tried to connect the lines to the middle of the circle. The 2 solutions I found were to: Create the middle points manually; To use shapes with strokes and then add the circles. I think making these middle points will improve the workflow in geometric design.

I would like to request an Android Wear device for prototyping. I currently only see Apple Watch.

I want to be able to draw lines that don’t snap to corners/center points on a shape.

I tried to make some geometric shapes, and I spent a bunch of time aligning all of the lines before I found out about flattening lines. When using the line tool, it’s edit points are not in the center And to do this, you have to flatten it by Ctrl + E: I think making the edit points centred by default would be better for the workflow!

I’ve noticed in development mode, we’re limited to adding annotations from a set of predefined options. However, there are times when I need to include custom notes or additional information, which isn’t currently possible. It would be greatly beneficial if the annotation functionality could be expanded to allow for the inclusion of custom text or the modification of existing options directly in dev mode. Do you think such a feature could be implemented in the future?

Hi! I have a file with some instances that had some variable modes applied (e.g. dark mode instead of light). Nothing else was overridden in the instance. However, Dev Mode shows the banner the message saying: “This instance overrides the color and layout defined by the component.”. I don’t think that’s correct, though, because we didn’t override anything. We just chose a different color scheme in variables. If i inspect the changes, it shows that apparently I overrode the colours (which is not true, I just applied a different mode). To avoid any mistake, I wouldn’t flag it as “override”, rather I would highlight that it has a different mode than the “standard” one (which would be rather better). Thanks!

I’m also having this issue where I can only see the iphone outline when it comes to present mode, but not when I make the frame in design. I want the outline of the phone while I design, not just afterwards. Why is this so hard to make happen? I’ve tried the prototype settings, but it just shows it in a tiny thumbnail and not where I actually need it to be (on design frame area). Please help, I want to be able to design inside the frame with the proper exterior DURING the working process, not just a preview afterwards. Why even have all the different iphone/ipad/etc frames if you’re just giving white boxes? Why not make every single one come with the appropriate outline and then people can toggle on/off visibility as they choose?

I have a sidebar menu list item component with three variants: Default, Hover, and Selected. Each of those has icon and text nested components, and each of those has their own properties. icon has instance swap and Boolean properties: text has instance swap, Boolean, and text properties: I have exposed the properties of icon and text to my sidebar menu list item component. However, the instance swap properties are not exposed to the top-level component/instance: This is annoying because, rather than being able to set all of my properties for my top-level instance in one place, I have to drill down into it to be able to set the instance swap property for the sub-instance.

Taking into account #config2021 announcements, I wonder Figma has any plans to improve the situation by introducing updates to duplicated community files. The problem now with community files is that that once you duplicated it, it is super difficult to incorporate update from original files. And it is often the case that updates and fixes are introduced gradually especially in the file is a design system or something non-trivial. I wonder if brave Figma people have something up their sleeve for this scenario? Much love, @ykovzel