Share Your Thoughts

Are there any plans to enable communication with other tools / API’s etc. in Presentation mode? It would be super interesting to see such possibility e.g. using a new Action type, or just an extra “Open Link” parameter like “API”, “Open in background” or something like this. If that would be ever possible - it should be doable to communicate two different Figma prototypes with each other using kind of a Bridge app.

I miss it so much. That is all. 

Hey everyone!After years of designing and building complex products (especially in cybersecurity and B2B SaaS), our team at Good Code decided to distill everything we've learned into a clean, flexible, and extensible Figma Design System. We’re calling it Unify — and it’s live today:👉 https://unifydesignsystem.comWhy we built it:We’ve worked on nearly 50 different platforms and noticed the same design challenges come up over and over — inconsistent components, limited theming support, bloated libraries, etc. Unify is our answer: a system that stays out of your way but gives you everything you need to ship fast and beautifully.What’s included: Light & dark mode out of the box 14+ ready-to-use templates (dashboards, forms, modals, settings, etc.) Tokenized system for effortless theming Smart layout and auto layout support Designed to scale with real teams We’d love for the Figma community to take a look and give us feedback. What’s working? What’s missing? What would help you

Hi Figma Team,I’d love to suggest a small but powerful feature that could significantly improve workflow for designers working with large files or design systems.It would be extremely helpful if Figma could display: The number of times a component is used (instance count) A list or link to the pages/frames where it's being used This feature would help us quickly assess how widely a component is being used before editing or removing it. Especially in files with many pages and scattered usage, this would save a lot of time and avoid unintended issues.  

I’ve recently discovered that our Developers are unable to use the measure and annotation feature when entering Dev Mode. I find this very odd, as a Designer with a full seat I rarely enter dev mode, surely all Dev mode features should be available at Developer seats?

When using named colors I can’t see the name of the color when I select a specific component. Only the raw color code. When I select a layout group however I can see a list of the color names used in that layout but not what actual component they are used on. Please make this possible :-) Adding two screenshots to show what I mean  

I use the arc tool for a few things. One specifically to create circular progress indicators. It would be nice if we could throw on the to-do list, adding variables to set the Start, Sweep, and Ratio here. (Make sure sweep and ratio populate as percentage) Imagine being able to create the component with conditions where on resize, those variable change. That could be helpful. Thanks.

Hello, good dayI used to be able to use AI, but now it's gone and I can't use it!

Why can’t you underline text styles? I get you could just have text underlined in your design system, but it would be nice to simply add an underline to text while you’re designing as well.

I want to measure the demission within the frame and accurately spacing it, but if I measure it with a ruler, I have to calculate it. Of course, there is also a way to make a square to measure the spacing. But I think it would be much more convenient if there was a demission function, so I'm sending my opinion. Hope you have a good day. Thank you.

As a UX researcher, my goal is to bring the stories and content I gather to life visually. With the ability to transcribe interviews easily and pick out specific parts, it would be amazing to take it a step further and automatically generate a flowchart based on the user stories. The same workflow could apply to someone who is mapping out more technical flows. inspirational tool: Whimsical AI: Text-to-flowchart

As IoT devices become part of our everyday environments — from smart homes to wearable health tech — the demand for seamless, secure, and intuitive mobile apps is growing rapidly. But building these apps isn’t just about code — it’s about crafting interfaces that feel effortless and function in real-time across connected devices.We just published a deep dive into how iOS is powering the next generation of IoT experiences. This article explores the tools, frameworks, and UX challenges of building smart, scalable apps that users actually enjoy.Check it out here: https://magicfactory.tech/hire-ios-app-developers/Perfect read for designers and developers creating the future of mobile!

Currently the only two ways to resolve merge conflicts is having to go through each page one by one and choosing whether or not to keep main vs keep branch. batch resolving all conflicts by choosing main or branch. The first way is so tedious, especially when there is only one small change that needs to be merged on one page in the branch, but all the other pages have changed a lot in the main. So we have to go through every single conflict and mark it as main except for the single page that needs to be branch. This is exacerbated by the slow rendering of each conflict, so we have to wait about 15-30 seconds for each to render before being able to select main or branch. The second way does not allow us to have much control over what is main or what is branch, and prevents us from being able to easily selecting the page(s) that need to keep branch. It’d be nice if there was a multi-select option where we can scan through the list of conflicts and choose which ones should keep main or

Drag and drop to shuffle properties of components doesnt work with new UI. It work fine on old one.

Does anyone else have a hard time organizing Figjam pages?Would be great to have dividers/subpages to be able to organize these better!

Please keep state available and not hidden in an accordion. It is super irritating if it needs to be accessed and the user has to open it to reveal the options. Every. single. time. 👍 

I put a bunch of stuff in a section and named it Section 2. If I then select that section and export it, it exports (correctly) as Section 2.png, but in the exported png it actually includes the little “Section 2” pill or whatever it’s called. This has to be a bug… right? How do I turn this off?

 1. Formulas in token values (mathematical operations)   It would be incredibly useful if we could use simple formulas (e.g. paddingXS*2 + paddingXL*2) when determining token values. Many design systems (for example, Ant Design) use this approach to dynamically obtain tokens. Currently, we haven't even found an analog that can be implemented without any plug-ins). The lack of such a feature makes the work a little more difficult.2. Transparency support for color tokens     Currently, if we need a semi-transparent version of a color marker (for example, purple is 100 at 50% opacity), we have to create a separate marker or manually redefine opacity, which breaks consistency. It would be great if we could keep the original color marker and just apply an opacity modifier (for example, "purple-100" at 40%) without resetting the base value.  Thank you for reviewing these improvements — we are glad to see how Figma is developing!!   

 1. Formulas in token values (mathematical operations)   It would be incredibly useful if we could use simple formulas (e.g. paddingXS*2 + paddingXL*2) when determining token values. Many design systems (for example, Ant Design) use this approach to dynamically obtain tokens. Currently, we haven't even found an analog that can be implemented without any plug-ins). The lack of such a feature makes the work a little more difficult.2. Transparency support for color tokens     Currently, if we need a semi-transparent version of a color marker (for example, purple is 100 at 50% opacity), we have to create a separate marker or manually redefine opacity, which breaks consistency. It would be great if we could keep the original color marker and just apply an opacity modifier (for example, "purple-100" at 40%) without resetting the base value.  Thank you for reviewing these improvements — we are glad to see how Figma is developing!   

give the ability to change the icon in the master instance - buttons, without the need to wrap it in a layout, and create a HAG for the layout, because you have a default instance size set in the master component for all instances

The fill is not visible on a vector shape unless its closed. Many applications and the web supports fill on open vector shapes, but not Figma. Please allow something like this. This red area should be fillable by the paint bucket.  

You can only see 8 rows and its too much scrolling. It doesn’t need to be only one column nor so short. If you’re on a 27 inch monitor or bigger it should adapt and grow proportionally to show 30 or more selections at once. It could easily be three times as wide and 3 times as tall. I know about showing just the swatch but I need names visible. Secondly the most commonly used choices could come up first without having to search. 

Hello everyone! I think having a shortcut to open/close the local variables would be very helpful. For example in cases where I’m prototyping and need to access the local variables to ensure the accuracy of the variable names or values that I’m assigning in the interactions. Currently, if I want to do this, I have to switch between the prototype panel to the design panel in order to open the local variables, check them and then go back to prototype. Note: I am aware that it is possible to keep the local variables window open, but this often leads to numerous bugs in the prototype. For example, when it is open, I am unable to drag the prototype interactions to reorder them.

“Rectangle” is not editable This is a small one, maybe. When adding new layers, I can see their name in the inspector but cannot edit the name directly. I only can edit in the Layers pane.Somehow that’s weird for me. Let’s make it more direct, shall we?

Conditional interactions are half broken at the moment. For example, all I want is to create a switch for light / dark mode for my prototype. We already have the “Set variable mode” action, but I cannot use it inside a Conditional if/else. All we need is to be able to do something like: if library/mode == Dark Set variable mode == Light else Set variable mode == Dark There’s also no else if(); while not a deal breaker, it would save time instead of adding another set of if/else (plus the bugs that come with it). Or we could have a switch action to switch between 2 states / values / modes, that would be great to use on switch components and require way less fidgeting with actions.