Suggest a Feature

This, but in Figma.Making it possible to paste elements into an already existing component. Im not talking about instance swapping. That would mean creating new components for what i wanted to put into my component. I dig the way webflow is handling it.   

在设计文件内部增加文件夹功能，且可以多层嵌套，这样方便对不同模块的页面进行分组管理。

First and foremost, branching is a great addition to Figma, thank you! Here is some background on how our Style and Component libraries are setup: Project: Design System File 1: Styles (text/color/other token styles) File 2: Components (primitive components, larger organisms, and some templates) What I’d like to do is create a branch in File 1 and change our brand color and add some text styles. I’d then like to “stage” this branch so that I can reference it in File 2 (another file) and test some of the changes downstream in components to see how they might look before merging and publishing File 1 (in case there are things I need to change/add). I would love some suggestions on how I might accomplish a workflow like this, or if it’s something that might be supported in the future. Thanks!

It would help with the prototyping and testing workflow to allow users to select multiple colors in the “Selection colors” section of the property sidebar on the right. When you select colors you will be provided with an option to “create styles form selection” and to “add to variable table...”This will enhance the initial UI testing and research phase of UIX design allowing you to easily and quickly apply your final styles and colors to a design system’s style set and variables.

Why isn't there a 'Sentence case' option in Figma's text transform settings? It would be very useful for improving typography workflows — especially for automatically capitalizing the first letter of each sentence.

Problem:Product Owners (nondesigners) will often times share early work in progress without the designer knowing. This ends up being a headache of dev comments (30+) pinging with comments that designs are not complete or components are not built correctly. Solution:Designer who is the owner of the file can assign specific users/staff so they get all push notifications/emails  Reason:To help each team member own accountability for the consequences of their action. If a product owner wants to share an incomplete file to 100+ people in the organization without communicating the designer. Let’s ensure the push notifications/emails get sent to the product owner that initially share a file too early to help respond to each comment. 

new auto layout is awesome. But not having shortcut for it setting make me sad. really miss shortcut for direction, aligment and padding and resizing option Please make it

It would be great if you could see a colour variables hex code when assigning a variable to an elements fill / stroke.

So I have created a simple form component and used MAKE to create a working version suitable for prototyping (This allows me to have full text entry and validation).The biggest issue is I am unable to tell the ‘Submit’ button to navigate to the next page in the prototype.Even if I tell MAKE to navigate to that page it just doesn’t seem to work.Does anyone have a work-around or solution to this problem?

I suggest having this feature in Figma since we are on a paid plan. Especially when we have so many frames/screens to be exported (eg. 170+) it’s a really huge filesize. And it’s not allowed to use an external PDF compressor platform when our projects are confidential. So far, I can only convert the frames into individual PNGs/JPGs, replace the frames with these image files, and export them into PDF. This is so time-consuming and troublesome.

It is now very unclear to see which files a person has access to. When a user has access to a specific file, you can’t see it anywhere in the admin page. It’s not very user friendly. I remember it being there in an earlier version, so please just bring that back. The files a user has access to should be shown in the sidepanel when selecting a user.   

Bringing this up for visibility. I have a page for “components” and a page for layouts in my design file. These components have many states, so I try to keep things organized by separating project specific variations of key pieces in their own page away from the prototype mockups.  I have a tooltip in these components - on hover it displays another component as an overlay. This works great in the component page - but use that component elsewhere in the file and the overlay doesn’t carry over. I can add the overlay, but have to connect each instance of the tooltip (it’s a quoter, so there’s lots of possible variations) on every variation of my component - which defeats the purpose. It looks like this is something others have asked for: ^Like this one if you’re interested.

When working with SVG assets within a design system we’re often using named color variables that are part of the design system so that our designs support different color modes (light, dark etc) it would be super helpful if there was some way for these variables made their way into the SVG code (with a fallback for situations or usages where the variable may not exist) So in your SVG export instead of this: <rect x="0.331604" y="0.717941" width="20.9977" height="20.9977" fill="#ffffff"/> you’d get something like this <rect x="0.331604" y="0.717941" width="20.9977" height="20.9977" fill="var(--color-background, #ffffff)"/> which would then be able to be able to be dynamically changed based on what is being set for --color-background in the consuming web app.

recurrent use case. For those who also develop, its a life save to quickly be able to copy the svg code. There is also a repeated use case where devs will ask for it. This used to be possible, but now my only recourse is to export, open in an IDE, copy+paste… I looked for this in dev mode but can’t find it there either.

How can we specify the design component code that the AI should be using? In the Attributions.md file, it says:This Figma Make file includes components from [shadcn/ui](https://ui.shadcn.com/) used under [MIT license](https://github.com/shadcn-ui/ui/blob/main/LICENSE.md). We don’t want an AI’s transformation of shadcn components into what looks like our design components. We want to use our actual design components to limit the number of ways the AI can miss interpret the designs it is prototyping to reduce variation errors between prompts.For example, I can give the AI the same prompt, and it will give me different designs when it’s re-interpreting the shadcn→design components every time.Generating code that is already aligned with our design components is also more useful for engineering workflows to convert the prototype into PR’s.It should also import the guidelines file properly from the design library. I don’t think this worked for me. Between the attributions and guidelines bein

First off. Yes, we all love variables. Secondly, this may have been discussed before, but it might be worth repeating. Also, I’m a bit frustrated so I’m sorry if I gripe a bit. Components need to have their own instanced variables. It is so time consuming having to set up a brand new variable collection for every component that uses variables, in every file. The way my team and I thought we could use variables is to set up the basic variable structure for a component in our library, then be able to adjust the value of the component for each instance. This would have so many use cases, and would honestly make my life so much easier. The current reality is that, when we set up a variable collection in a library, we are stuck with those values for all eternity. No way to change them unless I wanted to make a new variable collection in the file I’m working in and map them to the library variables (which I don’t even know if you can do because Figma seems to arbitrarily not allow you to sel

The background color of the Review updates window does not allow the current and updated components to be compared depending on the color of the components. In example below I am using Figma in dark mode and trying to compare two components that have black text. I am unable to do so because the dark text of the component is not readable on the dark background of the Figma UI. This can be resolved if Figma would allow the user to change the background color of the Review window between light and dark.

I regularly prototype using two desktop screens - I like to design with a prototype open at all times to see it in context to it’s actual size. I love the mobile app mirroring feature because it’s easy to select frames and have the prototype view update dynamically. It would be so so awesome to have a similar mirror feature for desktop, where you have a prototype window as the ‘mirror’ that dynamically updates based on the frame that you select in a separate window. Has anyone else wanted something like this?!

Currently, dashed strokes have ‘trimmed caps’. Is there a way to have all dashes with the same length? Example:

When defining variables (specially numeric ones) there is no way to specify the units.For example a value 16 could be pixels but could be also cm or any other unit. When you consume Figma variables using an API you need to guess which unit is applicable based on the variable name, scope etc., instead of just getting the unit from the API. Is it anything on the roadmap to cover this feature?

Sometimes a particular boolean variable can affect several layers. And some of that layers may require inverted visibility state. E.g. Layer 1 is visible when the variable is truthy and Layer 2 is visible when the same varaible is falsy. Let’s say, we have a multiselect field with a dropdown. When we select the first option, it should be added into the input as a label (label layer becomes visible). But also this option should be removed from the dropdown list as it’s no longer availiable for selection (option layer becomes hidden). So, both states depend on the same variable, but their conditions are inverted. It would be nice to have some negation operator when applying a varaible. Kinda logical not (!) in JS: ! isSelected. Or just allow us to apply boolean expressions as we do in prototypes , e.g. isSelected != true.

Hello, In my design system, I would like to map a container variable that would be a fixed value in desktop but a fill container in mobile.  I tried by setting a fixed value of 0 get the attention of the designers in order to make them change the value on their own but is there a way to automate this directly in the variable? I understand that this is not how variables are working but if there’s a workaround or a way to fix this, I’m taking it <3 Thanks ! 

It would be helpful if we could pick from existing variables when naming a new variant property maybe through a dropdown or suggestion list to avoid name mismatches and improve speed. 

Management of Dev Resource links is critical in our design systems. We are developing a multi-brand design system at Thryv that supports both React and Vue.js, and need to add resource links to a composed Storybook which documents a lot of components.Dev resource links are not editable from branches. We have our main file set to view-only so that design contributors have to branch to work for system integrity. They can’t add the dev resource links as part of their definition of done, putting the weight of that responsibility on the owner(s). Dev resource links can’t be automated easily for repititious components like illustrations that may all use a shared resource, but each component needs a link (and yes, I understand variants -- they are not appropriate for this circumstance). Between being an Electron app and lacking standard accessibility controls, hidden buttons that reveal on hover, and the links themselves changing positions after being saved, it’s challenging to work with some

For sales or anybody that want to show data about his product or company, it would be cool to be able to add line charts or pie chart easily. Right now we need to edit it ourself, but non designers would not be confortable to ajust it. It will be fun to have a tool to create chart where we just have to put our data and it create the chart.