Share Your Thoughts

It doesn't make any sense for me to own the organization, pay for a seat for a professional on my team and not be able to modify the project, nor even manage the access permissions of that project (such as removing people who are no longer part of the project). tip: add permissions to the project owner to manage access.tip 2: add permissions for the project owner to be able to edit the files (even with an added cost) without having to have a new paid seat.

Why is the after-delay trigger limited to 2000ms?Wouldn’t it be better to have more options like a max of 4000ms/5000ms to allow more complexe interactions to happen or even allow more time in one screen if needed?

Am I the only one who’s left wanting by the new position sticky feature? In my opinion, there are three main problems with the new sticky feature: It’s not compatible with auto layout SolutionMake the sticky elements always appear on top of other elements (and later add a z-index feature so we can fine tune the behavior) The sticky element has to be an immediate child of the scrolling container SolutionMake the sticky behavior relative to the closest scroll container instead, so the sticky element can be a grand child, great grand child etc. Only works for vertical scrolling and can only stick to the top of the container SolutionAdd an offset property (top/right/bottom/left) - like the CSS implementation - super simple, but pretty flexible (only problem with the CSS implementation is the overflow: hidden limitation) What I want to be able to make None of which is possible with the new sticky feature unfortunately HTML prototype Note the sticky footer inside th

It takes a long time for styles from a design system to update when used, literally around 5mins before the changes is reflected, for better content if I’m using a current text style and I change to a different text style, it takes close to 5mins before it is eventually changed.

I am enjoying the improvements to annotations, but would like to be able to make a couple of bullet points in an annotation. Ideally we’d have the same support here as we do in comments, where dash + space starts a bullet list. The workaround of opt+8 to insert a bullet character doesn’t bring the indentation and I’d like to keep these points in the same annotation as they are related, and adding more annotations clutters up the file quickly. 

Image parameter adjustmentI can't see the exact parameters that I'm using to increase the exposure or saturation of my images, and if I want to get the exact same exposure increase for another of my images, it's difficult. This makes consistency in long term design pose a difficulty.New UIChanging button icons or changing the position of buttons without improving the experience or adding functionality is not friendly to long-term users. PrototypesI have seen to your growth, and I have seen your efforts, and your intentions. But the limitations of prototype still persist, such as the complaints about all the “on scroll” interacts, also including the inability to trigger a change when the global value changes.

Figma Slides is a great tool, but in order to fully compete with PowerPoint and Google Presentation, this tool must support the presenters’ devices (clickers). The head of the sales department is satisfied with the quality of our presentations, but it is inconvenient to show them to the audience without a clicker. Guys, this is important.

Let's address the elephant in the digital room: Figma's compulsive need to force-feed updates to its users like some overzealous IT administrator. This isn't software evolution - it's digital waterboarding. The complete disregard for user autonomy in their update policy would make even Windows Update blush.Without warning or consent, we're suddenly greeted with relocated features playing hide-and-seek, shortcut keys that now trigger random functions like digital slot machines, and UI elements rearranged with the logic of a toddler playing Tetris. That carefully cultivated muscle memory? Gone. That optimized workflow? Obliterated. All sacrificed at the altar of "progress" that feels suspiciously like change for change's sake.The most infuriating part? The complete lack of new bottom bar. While we're scrambling to meet deadlines, Figma smugly insists we pause our actual work to play archaeological dig through their new interface. Their update notes read like fortune cookie wisdom - "Impr

I’d love see my Figma frame syncs the auto-layout properties when copy-pasting to Figjam.

Some suggested improvements for the Variables DialogIt should be possible to open the Variable Dialog at any time, even if an object is selected. Once open, it already stays open as you interact with objects, so there is no reason that it can only be launched it by deselecting everything first. Make all the Variable Collections available all the time It would be very useful to be able to see the list of all collections all the time  Display Variable Collections and their groups in a tree structure Make each collection a “top level” tree node, showing it’s name followed by a list of modes if it has more than one. Benefits: All available collections would no longer be hidden in a dropown More efficient to switch not just to a different collection but right to a specific group within that collection Could support drag and drop to move variables and groups from one Collection to another when the other has the same number of modes  Variable Collection group branches should support empty

Hi all, I am wondering if it is possible to enable a “push/pull elements below”-function. In my current case I have an accordeon component that changes size based on what instance is selectet / interacted with. Below this component sloser to the bottom of my screen are texts and other elements that are currently “overwritten” by certain expanded instances of my accordeon. In my previous job I worked with Axure and there one can simply select “push/pull widgets below” when adding interactions to a component and all elements on the screen below will be pushed/pulled by the exact difference in height of changed component. Is it possible to add this option in Figma? (I know I could just add all other elements to my component but this would blow up said component way to much and seems unnecessarily complex)

First and foremost, I’m really enjoying using and experimenting with what I can do with Variables. I have barely scratched the surface but feel like these are obvious improvements that should be included in the backlog somewhere: Ability to duplicate Variables Ability to duplicate a Collection Ability to move Variables to another Collection Ability to move a Group to another Collection Ability to move multiple Variables (between Groups and Collections) Add a description for Collections and Groups (I don’t want to repeat the same thing with slight variations for each Variable) Ability to search for a Variable or Group within the Variables window Ability to move the Mode columns within the Variables window [EDIT] When creating Color Variables, I wished that it remembered the last panel I used to create the previous Variable. This would be useful when I’m creating multiple semantic variables via aliasing [EDIT] Ability to scope multiple Variables that are of the same type Thank you so m

Just like we can navigate to the ‘main component’, I would like a functionality that takes me to all the children of a main component. Or does something similar already exist and I’m missing it?

I dunno if this is a bug or an oversight, as it seems very odd that this wasn’t implemented at launch, but can we add variable support to Gap row/column in grid? :) 

Can somebody explain to me what is the point in having multiple stroke layers when they:SHare the same size Share the same offsetAnd another question is is there any way of doing offset to a stroke or drop shadow? I really need this for our focused state in our design system and what I found was only wanky workarounds...

As a user of variables and variants - I'm really tired of writing the same words a hundred times in every new project when I create and name typical elements. It would be great to have some sort of auto-suggestion (like on phone keypads or programming apps) or text replacement for typical elements like buttons, devices, component states (hover, disabled, etc) and so on. Right now I'm using the macbook's internal function, but I don't like this solution because it bothers and irritate me outside of figma :) For now, I'm using abbreviated versions of words to speed up the naming process. 

It would be very useful to have the ability to offset a stroke. For instance, in the case of the focus state for buttons and other components. Currently, there is a workaround, but it is not very convenient as it requires us to manage shadow and transparent stroke. This is especially inconvenient for a large library of components and complicates developer handoff.

Figma should add an outline and outline offset property similar to the properties in CSS. This is useful for focus styles among other things. Currently, there are a number of approaches that you can take to achieve a similar effect, but neither is ideal: Drop shadow: one problem with using drop shadows to create a focus outline is that you have to have a fill. Absolutely positioned frame: you can add an extra frame within an element that’s absolutely positioned and apply a stroke. This isn’t ideal because you’re required to add an extra, unnecessary frame to every element that you want to add an outline to.

Figma desperately needs to expand the overrides that can be reset. For overrides that are not in the list, “Reset All” is a massively inconvenient alternative as it resets things you had no intent of resetting. Every property would be great, but notable top priority: Reset Height Individually Reset Width Individually Reset Autolayout Resizing (Fill, Hug, Etc). Reset Autolayout Spacing Reset Autolayout Padding Reset Clip Content Reset Border Radius Being able to reset on a more granular level is the takeaway here. I feel this doesn’t get enough love, but is a daily annoyance for those trying to retain a source of truth with their Components. If anything, open up the capability for a contributor to build a plugin. If one exists, please point me in the right direction. 🙏

Would be nice to have a feature that allows to reset specific parts of an instance: Shadow Background color of a container Border of a container  ...

By default, the HEX colors show as all uppercase like #FFFFFF but it would be nice if in the settings we could choose to show them as lowercase like #ffffff. An ability to choose this would be great!

Would love the option to set the color of the page to a variable. In an effort to create more uniformity and consistency across files, I created a variable collection for documentation colors, however I’m unable to define the page color using variables. This would be especially useful for documents with 10+ pages, as it’d be an easy way to keep the page background colors all aligned.

PLease stop moving most commonly used buttons to new places all the time!It isvery bad us practise, each time I need to spend time to learn where I can find an options that was moved or has a new look, like whith this auto layout flow buttons, which where presented as a dropdown before. Very subtle and unexpected change.

I think we need to move the aligning panel back to the right, I found myself use gap input more that aligning and by long shot.   

Hi!I wish that when I copy a stroke, the stroke retains its individual stroke-position when pasted. Right now, if I copy a stroke it will paste as an “all stroke” even if the original only applied to one side.Further, I wish it was possible to select multiple individual strokes for one object, such that I could have different weights and colors for each side.I am unaware if these suggestions have been made previously, but I wanted to mention them anyways!Thanks!