Share Your Thoughts

The current layout for stroke per side is top/bottom/left/right, if you go into custom, it is left/top/bottom/right if going clockwise, then if you tab through it goes left/right/top/bottom. I think it would be more intuitive for designer and developer for these to be setup how it is with border radius. Going top/right/bottom/left, in a circle clockwise order.

while presenting my software design in Figma I was facing problems using my navigation prototype. and that was because of hover effect on Present page of Figma.

Showing the entire description in the tooltip when hovering over a component in the asset panel can create a large amount of text that is not necessary to understand the usage of the component or to choose a component. Keeping the description short will prevent adding more important information in dev mode or under the component description in the right panel (or in the new modal when it returns) My suggestion is to add another field (header, summary) above the description, that will be shown on the tooltip in the asset panel, where the full description will be shown in Dev mode and in the right panel. Alternatively, maybe it is enough to truncate the tooltip after a few lines of text, this way the author can decide what will be shown in the tooltip and what will only be visible in the description

Firstly, I’d like to express how impressed I am with Figma. It’s evident to see why it’s leading the way in UX design and collaboration. However, as a disabled visual designer, there are key features that, if addressed, would significantly enhance the usability of your platform for people like me. A few months ago, I communicated my challenges when I began using Figma. Having spent two decades in this industry, it’s concerning that this is the first design tool I’ve struggled with due to my disability. My fear is the potential risk of becoming irrelevant if I’m unable to efficiently use Figma, which is now a mandatory skill in most modern UX/design jobs. I recognize that many Figma users might not face these issues. However, I believe there’s immense value in enhancing its accessibility. Here are some features I believe would make a considerable difference: Extended Toolbar Options: Allow users to click for commands like grouping, ungrouping, zooming in/out, rather than depending on s

On Layers panel, the divider between the top list (pages) and the bottom list (layers) is really not easy to see and therefore grab. Could we have a more comfortable one? Minimalism is cool but not when it goes against usability. Thanks!

Inspect tab is least effective to me with the way each section is put one after the other. There is not option to move the sections up & down or remove sections that I dont needed. When working in developer mode, layout & code sections are of top priority to me & they need to be shown at the top always so I can copy the code. Please provide option to perform above actions.

Currently Figma allow design system authors to have alternative titles of components using the component description. I’m suggesting adding a new field instead of having many different titles to the description field. My workflow include onboarding many new designers so preparing for their different “Naming” Backgrounds is beneficial without impacting the actual component description.

Been enjoying prototyping with variables and conditionals! What would have been 68 individual frames, I have a complex prototype using 3 components and 5 frames. Thank you Figma!! In the future, it would be great to have efficient ways to apply actions across multiple frames such as: Copy/paste actions Group multiple actions into a set of actions a user can copy and paste Select multiple frames and append new actions into each’s interaction set Variables with functions/series of interactions???

I searched but couldn’t find a request like this. Now that you can queue up a bunch of commands in a single interaction, it would be nice if you could inject a pause in between executions. Example: On click set variable showFrame to true Wait 300ms Set variable x to 5 Right now I’m achieving this through a hack. I have a “hotspot” component with two variants, and I do this: On click (of variant 1 of the two-variant hotspot) set variable showFrame to true Change to variant 2 dissolve 300ms Set variable x to 5 This works, but it would be cool if there were a more straightforward way. Note if you need more than one “wait” in an interaction using this hack, add more states to the hotspot, as for whatever reason, changing back to variant 1 doesn’t work.

When moving and adjusting large designs or flows, the comments remain where they originally were. I want them to come along for the ride and stay with the component or area on the Figma where they were originally placed. I don’t want to have to go and grab them to put them where they were. There was a suggestion made by a PO earlier and it’s not the same use case. I don’t need to move frames to other pages. This is more about work in progress on the same page.

When selecting a number variable, it would be helpful if the actual number value is shown next to the name. Color variables have the color swatch for easy recognition. Number variables could mimic Text styles, where the font size and line height are shown next to the name.

Please allow clicking a component to: change the variant of some other component show or hide an element

Please allow elements to be shared across variants. It’s very brittle to rely on names for connections between variants. It’s also very tedious to have to give everything a unique name.

Formatting like H1, bold, etc. currently aren’t reflected in the hover state of components in the Assets tab. The minimum solution to the problem would be at least not to ignore line breaks.

I would like to be able to bulk edit component descriptions. For example if the descriptions are structured with headlines that are consistent across all components, I’d like to be able to edit those shared text elements in bulk, instead of going through hundreds of components individually.

We have been managing our design system(s) for Desktop, Mobile, and TV applications in Figma for some time now and the experience overall has been great (especially with the updated Auto-Layout model) but one thing that has been extremely difficult to manage are design tokens. When I say manage I actually mean we are not using them because there is no solution to do so between Figma and our actual developer component libraries (Apple TV, iOS, Android Mobile, Android TV, HTML TV, HTML Desktop, etc…). We would love to more widely support themes in our apps and at a minimum use tokens for colors, spacing, font weights, and more. This would not only dramatically help with design speed and consistency but allow developers to more easily translate the components and layouts to real platform components (if you could inspect or export the tokens). Here are a few key items that are quite difficult without first party support for tokens. Color Themes: Without tokens you have to rely on color s

Like in Sketch it would be great if you could get the pixels from a selected object to a hovered object.

Can the transparency be easily set in the color variable when referencing colors here? This is highly desired and we hope it can be supported.

The new component details pane looks awesome, and being able to switch between variable modes is neat. However, switching between say ‘light’ and ‘dark’ mode becomes non functional unless the background behind the component is also able to change. Would be nice to be able to link it to surface-default variable or similar.

When using the prototype features, variables are a great way to allow dynamic designs. Unfortunately, using variables like this gets very unwieldy very fast. Consider this example: I have an radiobutton component, which has a boolean “checked” property. Based on the radio button, I want to change the variant property of a button, which has the variant property “style” with values “inactive”, “active”, and “disabled”. So on each radio button, I need to define something like this: On click: Set Variable “radiobutton-1-checked” to “true” Set Variable “radiobutton-2-checked” to “false” Set Variable “button-state” to “inactive” Even with this minimal example I need to set three different variables so that each component gets its correct state. It would be so much easier if one could apply an expression in place of a variable. Then one would only need to set one variable e.g. “enable-button” to “true” and instead apply the expression “enable-button equal to true” or “enable-button equa

Managing plugins is cumbersome. Your bookmarking doesn’t sync across personal and business accounts Your bookmarks aren’t set to default Some bookmarks appear in the side panel, others don’t There’s general inconsistency in the bookmarking experience Plugins aren’t categorised (which makes discovery hard)

This help page says Any text before the first / will become the component name. Every extra / level will create a new property. Well I waste a lot of time deleting properties and restoring the name after the slash / after I create a variant. I use Slashes for maintaining an Atomic System. This way, it looks like Figma doesn’t want me to have atoms, molecules and cells. 🤷

the text suddenly disappeared.each click will be restored, please help to solve the problem

When exporting frames, can we export the text-only, as opposed to the files being nested into 5 layers? For example, if i am downloading an icon-svg with the frame name to be design system/icons/arrow-up, i don’t want the exported asset to be nested into 3 file layers to reach the asset. Same goes for labeling frames with dates using /. Just want to download the asset with their name intact

It would be really cool if you could merge multiple sticky notes contents with a shortcut. Or to take bulleted lists within sticky notes and convert them into multiple notes.