Share Your Thoughts

Instead of one giant library file, we break down our components into several files which all inherit from Core library. When publishing this Core library, it’s a manual process to update and publish all the other related library files. Suggestion: Add a secondary step to publishing with a list of all the published libraries that inherit from the one you’re currently in. Select the ones you want to auto-update and publish.

With the latest update, the flyout menu for prototype wires now hovers inside the workspace. This dialogue box gets in the way when trying to select multiple wires. Please revert this menu to appear in the right sidebar so the user doesn’t have to continually move the window around to see the frames underneath.

the big need I have is that I want to keep context of comments placed on downstream child components when I’m viewing and editing a master / parent component. another cool thing could be is if I add a comment to a master component, this special mode of a comment could show up on all downstream child components, which would allow me to question whether the comment still applies in all situations, of if perhaps the comment overlooked some edge case. EDIT: this should also take into account variants. If I comment on a component variant, it should appear on the correct variant.

Hi everybody, I have a suggestion for a ‘developer oriented feature’ to add in FIGMA. As for now it doesn’t exists, there is something we would appreciate I think : Having an option to export the animated interactions settings (with all the ease settings and so on…) we made in the “prototype” section of Figma… I mean through SVG + CSS with @keyframes, JQUERY or anything else ! It’s too bad to have to recreate in HTML, JS etc… all the stuff out of Figma. We would love using this feature to be more efficient and getting a better productivity in our pipeline of production! In one word : “Once we have validated our Figma animated designs, we want to be able to export the code applied for this animate part of the prototype” Thank you very much, Best Regards, Robin

Layers already stack in a way that forces you to expand that pane a lot just to see what you’re looking at. Now, I have to worry about having extra space because the invisible scrollbar might activate if I hit a layer stacked in a half-dozen layers trying to hit the show/hide icon, thinking I have room, but oh no, there’s the scrollbar. Then, of course, because there’s no way to properly search for hidden layers, I have to go search for it manually again. Can we fix this, please?

Please add sticky papers in Figma file as well, like one you have in FigJam, because sometimes you need to brainstorm on wireframes stage already and that would be very easily with these sticky papers.

Please allow instances in Plugins to have access to the update functionality available in the sidebar. This way it would be possible to e.g. update all the instances part of the current selection of the user or part of a specific page.

Command-clicking on an object name in the layers menu brings up the contextual menu - copy, rename, create component, etc… Why not apply this behavior to the object itself, on the artboard?

I feel like this modal could really do with some icons and work on the hierarchy to make it easier to quickly use - its so low contrast and everything looks the same. I’ve used it thousands of times (the pop up from the sidebar before it was this popup on the canvas) and do something wrong pretty much every time More specifically ‘On Click’ looks like the title of the

When importing a library from Figma into FigJam, I would also like to see the name of a component’s variant below each sticker thumbnail. Currently I find it hard to distinguish between each variant as the thumbnail is too small. If the variant’s name was visible too it would make it a lot easier.

Just makes it easier to draw lines and angles, like in Microsoft Whiteboard

Hi people, When we are working in our team in a Figma Design file, it happens that the cursor / user color of the team members are often changed. Sometimes my co-worker is yellow, sometimes gray, sometimes green. It would be cool for everyone to have their own set color so I don’t have to read the name next to the cursor every time! Kind regards Daniel

Hi folks, here’s a suggestion: When I hover over the cluster of file cover thumbnails we now see in the Team view, and you hover over 1 specific file, I would rather see the file thumbnail expand to be legible so I can read what is on the file cover. That would let us create covers with information about what is in the file for a quick view, not just it’s filename as appears now. Thanks, Ben @BenKopf_UPS

Support for native functionality of the following plugin would be helpful.Figma

It would be great if a component has fixed size variable, that you can still select other options within that collection/group. For example I have an input field and have several sizes of height. However, the only way to change it is to detach 😦 What is interesting is that you can adjust the frame of the component without detaching 🤔

Objects placed in tables need: postits, highlights,etc aren’t recognised as part of the table. So if i have a postit in a table, and then add rows above, the posit will STAY where it is rather than sticking to the box it was put in.

The idea The back interaction brings you back to the previous frame, but sometimes you want to step back multiple frames. I suggest adding a number to the back action. Problems with workarounds If you have access to advanced prototyping features, you can stack multiple back actions in the interaction, but it will use the same animation from the navigation interaction that got you there in the first place. If you stack five back actions, it will play five animations, which looks horrendous. You may also ask, why don’t you just navigate back to your desired frame? Because it breaks the navigation history. Say you have frames 1 through 5. You want to use the back button on frame 5 to go back to frame 2, but frame 2 also has a back button, which then will

We have conditional prototype, what is great, could we now have ways to get usage data from Figma? Like add google analytics snippets for see usage on each screen, or some heatmap tool like clarity or hotjar.

would love to be able to toggle on copy/paste as text as the default behavior.

Hello @Figma_Support , I’m currently working on a project which uses many component instances with images inside them. My task is to swap the images to other images which are already imported in my Figma file however the only choice I have is Choose Image which is importing again. It’s a pain. It would be cool if we could choose an image from the viewport, a bit like what we can do with the colour eyedropper tool.

Would love to use other type/fonts in FigJam so we can use our or our clients styles to tailor the branding of our presentations and workshops. Being able to leverage the Figma Design system would be preferable, so governance is possible (color, type etc) Related, allow for the “sticky note” to have a customizable color like the shapes.

Looks like this one was asked before, but i’d like to suggest again that Figma create a User Testing Mode for prototypes. Something that is easy to integrate with user testing platforms that removes unnecessary UI elements, and adds the ability to add feedback within the prototype using the comments feature.

Instead of just assigning numeric vars from one collection to another, we might do simple math operations with them, and in such way create very functional systems. In many design systems we have so called “golden numbers” which function as multiplicators for other values. e. g. : I have some atomic var: var: gridSize: “6”; And then I can have this functional var: var: padding: mode1: [gridSize]*1, mode2: [gridSize]*2, mode3: [gridSize]*3 And this way, if I change the baseGrid value, all others will automaticly update accordingly. And thi sis something with like tons of awesome.

As a user, I need bulk editing of nested properties. As you see in the attached files, I have 2 of the same components with nested properties. But if I select more than one of them - nested properties will disappear and I will see only properties related directly to the current component.