Suggest a Feature

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 lead you back to frame 5 again, when it should take you to frame 1 where the prototype originated from. Alternative solutions Add a toggle to the navigate action that clears history. Say you’re using a navigate action to go back to fram

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. Thanks!

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.

In prototyping mode for opening an overlay there is the ability to add a background (ie; 40% tint of #000). It would be nice to also be able to blur the background.

Currently the only function of fixed positioning on an element is to make it persistent in the same spot at all times. While this is useful the majority of the time, there are instances where it would be helpful to have an element become fixed when it scrolls into view or reaches the top of the screen. For example, there could be a web page that has a secondary navigation below the hero that will become fixed when it reaches the top of the screen and be persistent for the rest of the scroll depth. Then when a user scrolls back up, the element releases from the fixed position when it reaches its original position. You can see this in effect on this page: Develop custom experiences with the Zendesk Platform | Zendesk Sunshine. It could also be used in more advanced manners such as multi-level parallax scrolling. This would be very helpful for both engineering and stakeholders to understand functionality, especially when the designer isn’t there to describe it to them. It would also prov

Hey there, I was playing around with the new variables Beta. I find it cumbersome to use, especially when on a small screen. I believe it could be great if it could detached from the UI into a standalone component in the actual artboard. This way it could grow and there could be a structured overview of all variables at a glance. Here’s a mockup as a screenshot: It could be only as an overview as well, to prevent multiple points of inputs.

It would be a nice feature maybe to have a general search no matter in which file/tab you are (desktop app). Similar to macOS spotlight search .

I’d put in a vote for a “paid priority care” queue where users can pay $10 (i’d probably have paid $30 as that’s 2 per-month seats on our 4 seat team) to have immediate live person responding to my CS query about deleted file today (the CS person who resolved was super great btw) I know putting a price on “priority care” would need careful market testing, and potentially some “number of follow ups” included in the price, but feels like a reasonable place to give users a “pay for overnight shipping” of CS that would be valuable to the customer and to the company alike.

I would really appreciate the ability to create variable blur effects in Figma. Ideally the effect would also work in Prototypes (content traveling behind it would blur). The specific reason for this is to have wysiwyg visuals for Apple’s visionOS header and footer bars.

This is one of my most used features of Arc, and I would love to see this pattern applied to the Figma app. When no frames are selected, it would be great if hitting CMD + Shift + C would copy the share link to my clipboard.

I love the branch/merge feature however I am constantly updating in main when I am intending to update in the branch I opened. The update from main feature is nice, however it’s stressful to have to choose which-update from-which-branch I want when I didn’t want to make updates in main in the first place. I’ve even selected the wrong update and lost work a few times now. I would love if Figma could add something in the working area of the main file that was more obvious upon opening a branch. Something like a bar across the top of the screen that said “Main file: Branch xxxx currently open”.

You should make more clear that the name of the Team is the Name appearing on the Billing to avoid nick names

We’re trying to use the Jira widget to share the single source of truth about the readiness of component within Figma designs. Unfortunately, in the expanded form (which shows the status of the JIRA ticket - the most important information), the widget can’t be used as a link to JIRA issue in read-only mode. This seems quite a major use case, is there a way how to achieve it or are there any planned improvements. As a workaround we are attaching two widgets - in the expended form and in the form of the link but it’s not the ideal way how to work with that. 😉

It is massive work of link color alias in variables. There will cool if user can alt-drag copy of alias from one to anther. or copy / paste shortcut

This is about the new interactions pop-up menu that appears when you create an interaction noodle, or when you click an existing noodle. The pop-up menu appears near where you clicked, but it often obscures the components or noodle you’re connecting, so you can’t visually check that what you’ve done is right, or it means you have to move the menu out of the way to work on things it’s blocking. Or sometimes if you are clicking on a noodle or setting an interaction near the bottom of your display, the menu gets cut off below the viewport, and you have to move it. Then moving the pop-up menu is finicky too. I instinctively try to grab it by the top left or top middle, but there is a drop down menu’s touch target that I often accidentally click instead. I’m a fan of the pop-up menu because it means I don’t have to keep going to the right panel, but I’m hoping how it appears and how to move it could be improved.

When a layer in an auto layout is set to absolute position, it has a different icon. I’d like to have some similar visual communication in the layers panel when a layer is set to sticky scroll, fixed scroll, or has its contents scrolling. Right now I manually type in these states in parenthesis but having it built into the layering display settings would be beneficial: Edit: The layer order is adjusted when contents are Fixed vs Scrolling.

Hello, would like to share my common use case with strokes on Figma. In every design system I made I create doubled contrast borders for my elements like this example. Goal creating this on Figma is a lot frustrating because we can’t handle the stroke position for each stroke. This would be done easily by allowing to set the drawing position for each stroke, instead to set all strokes inside, center o outside. The Problems …with solution 1 The current stroke management in Figma is forcing us to create multiple layers just to add borders or change border positions. Is weird to replicate “outer-border” and “inner-border” layers in every component. Plus, for a design system consumer is hard to keep consistency since they have to copy/paste those layers in their design. …with solution 2 Another solution could be to add a single stroke to the layer, and a shadow effect to replicate the visual effect. This brings the problem that a layer can have ONLY ONE effect applied. So, if the current

There are already a bunch of useful widgets that can boost design-devs communication. For example I want to embed a video on the canvas that my devs can play. Or I exported variables and I want to list them in a nice code block for my devs to copy it. Even Jira widget is useless until devs can’t open a link through it. Allow widgets to be interactable for devs.

Hey, For masked nodes, it would be great if the node properties will already reflect the mask too. Just like ‘absoluteRenderBounds’ already represents drop shadows and strokes, it would be great if it also represents the masks. Today, this data is more of a ‘raw’ data, therefore, plugin developers need their our own algorithm that takes the mask into account when figuring the layer size properties.