Share Your Thoughts

The purpose of this linkage is to make it convenient to make alterations or modifications when necessary, all without the need to update the primary or main component separately.

I am working on a huge project with a very large number of layouts. We are required to have many pages within one project. The problem is that when a new team member arrives, he has to explain everything and review dozens of files and pages inside them in order to figure out where and what lies. We create separate documentation for all files and pages with descriptions for them. This makes the process as difficult as possible. I would like to just go to the File and read its description. Go to the page and read a short description to quickly find out what and where. It would be cool to have something similar to the description in Prototype->Flows

This topic has been apparently discussed before, but i want to make a post to emphasize the importance of this issue. Detaching nested components inside components, breaks all overrides on the parent component instances. I claim this is a major problem, as it makes it really hard to migrate a design system to use properties instead of a vast amount of variants. As an example, i work in a large company, that a lot of materials in Figma. The design system has been initially created a vouple of years ago, and at that point, we had to rely a lot on component variants that very often utilize nested component instances. Now with the new Figma properties, and the apparently upcoming improvements on them, i could quite easily reduce the amount of variants by 80% in general, and make the components much more simple and foolproof. However it would require detaching a lot of the nested components, but it is practically impossible to do that, as there are hundreds or even thousands of instances th

A real quality of life update would be to change the way Undos and Redos work. It’s clear that there are about 100 steps I believe, but this is every single mouse click, selections, repositions, change of everything. It would be amazing to: Track only major changes i.e. styles applied, variables applied, repositioning, increment and decrement of size for fonts and images Have a separate instance for the undos and redos for components, would be great if each component had their own instance or even their own minified version control Obvious buttons for Undo and Redo with a drop down with last actions upon keeping the button pressed for 2 seconds. Just a couple of thoughts. Thanks.

Hey there, I scoured the forum for “spline” but came up empty-handed in terms of topics. 😕 Anyone out there aware of whether Figma plans to add native spline support to their roadmap? Tools like Webflow have nailed it with their implementation, so it would be awesome to see some spline love from Figma too! Cheers, Sanny

If I create a variable and apply it to my design, then delete that variable, the design maintains a reference to a non-existant variable. This is reflected by a disabled/missing variable badge in the field or colors list: The problem is, there’s no way to locate all instances of broken variable references. Through the process of learning to use variables, many have been created and re-created. There are broken references all over the place, and many have gone unnoticed. It would be amazing to have a way to locate them all so they can be swapped for new variables.

Hi there, As a team worked in Microsoft environment, we’re looking for Figma–Microsoft Teams integrations. For comments notifications, for libraries updates and more.

could anyone build a plugin of font finder from image

Hi, it’s my first time posting here so please let me know if there’s a better category where I can post this. I’m working on a Figma plugin to automate a manual workflow and one of the steps is to convert a vector’s stroke to outlines. Manually I do this by following these steps: Select vector layer Ungroup Select parent frame Flatten Outline strokes Currently there’s no “outline strokes” plugin API available at all, and as far as I can tell the “ungroup” API applies to groups but not vector nodes, despite being able to ungroup it in the UI.

Please add Gabarito, a very clean font available on Google Fonts.

When you format a component description (bold text, lists, etc), that formatting is only visible if you hit “show more” on a variant’s description. If you just look at the short version of it (2), everything runs together in one line, no breaks. And if your description is very short - not long enough to trigger the “show more” link - you never see the actual, formatted description, because again, hitting ‘show more’ is the only way to see see the full description. As far as I can tell it’s impossible now to have line breaks in that abbreviated description, which makes it look kinda gross. How I’m formatting this description: 2: what you see in the abbreviated description: 3: You have to hit ‘show more’ to actually see all this

I have some issues when I call the icon from the component, with a different variant it will be mirrored. I have no idea what’s happening.

Simple, easy and straight forward: whenever I create a personal token from Home > Account > Geneate new token the lack of a copy button makes me itchy: Just add a simple copy button inside the input, and make me life easier ❤️

Hi everyone. Is there a way to insert a vector ( a shape, line or icon ) in a text paragraph and make it flow with the text? Some of you might be familiar with InDesign, which has this feature.

Version control for designs or “GIT for designers” inside Figma 🙂: Master design; Branching; Merging changes.

Allow to write variables and style names in the fill and stroke input box, without having to go to the styles panel.

A useful context menu item that celverly breaks a textbox up into separated paragraphs inside an auto layout, allowing the user to easilly add content like images etc into a website flow, also making inporting body copy much easier.

Hi Everyone… This is something I came across lately. If you set a master component to reveal the properties of a nested components, it works well until, in the instance, you swap the nested component ( which has indeed a swap instance property ). If you do so, exposed nested component properties disappear. It would be good if the instance retains the ‘expose nested property’ setting even if you swap the nested component. Whatever property the swapped nested component has, it shows if the ‘expose nested property’ setting is ON. I hope it makes sense? Thanx!

Hello there, Figma! Can you do us designers a solid 😉 and let us save our font preferences for those pesky missing fonts? 🥴 … We’d love to see what you have in store for us, Figma! 🎩✨ If you’re in agreement, give your vote to save the designers’ precious time! 😀 👩‍💻👨‍💻👩‍💻👨‍💻👩‍💻👨‍💻🧑‍💻👩‍💻👨‍💻👩‍💻🧑‍💻🧑‍💻

Hello, if we want to use variables and modes to handle UI themes, we should be able to set them everywhere we can set a color. As requested in other topics, we can’t set variables as gradients steps and we can’t also set color variables as shadows. This prevents any try to switch to variables since no one wants to use half colors as variables and half colors as styles.

When entering a srries of variables on the same subject it would be saving time if you could use the tab to switch from name to value, then the enter to switch to the next one of the same variable type. (or as today the tab brings to create variable you could at least allow the keyboard selection of the type)

When you hover over a value, sometimes your cursor turns into a slider. From there you can click and drag and change the values intuitively instead of having to type out the numbers. On the numeric inputs with big labels, there isn’t much of a problem. But when there are no labels to hover over, the area that detects a hover is so small that its really frustrating to nail it on the first try. Here is a video demonstration of the frustration: Does anyone even use the slider function or am I the only one? It’s super useful in my opinion. I don’t have to type the numbers and I can just approximately size it instead. For anyone who have used Blender, a better implementation of the cursor slider is basically what I’m asking for. What do you think?

When presenting ideas, it would be helpful to have a keyboard shortcut to jump to the next section in FigJam. Similar to the keyboard shortcut “N” in Figma to jump to the next frame.

Prior to color variables being introduced all of our design system colors were saved as styles in our shared library. Now with the introduction of color variables, it seems style usage is shifting to be meant for multiple color fills and other more complex fills. For simple, single color fills, Figma recommends we use color variables (this is based on the tooltip in the style picker, but doesn’t seem to be reflected in the official documentation yet). My team has added all of our design system colors as color variables, but now in the style picker there are two sets of colors, first all of our new color variables, then all of our legacy styles. We’d like to delete the legacy styles so there is just one set of colors for our designers to choose from, however deleting a style detaches all of the instances of that style across text, shapes, frames, etc. So that is not a viable option since all of the existing colors across our teams design files will become out of sync with our design sys

right now a stroke is added to the png bounding box rather than the contents while in Sketch and photoshop you can add it to the outline of the contents. Can we bring that (even as an option) to Figma?