Share Your Thoughts

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  

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

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

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. 

“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.

style 

It is not obvious in the default view of an open document that the user needs to create a frame as a canvas to start a design. Suggestion to either have a visual tooltip pointing to the frame icon in the toolbar alt. a “create frame” button centered on the main area/window. 

Why, in UI3, does an object move 2 pixels each time when using the keyboard arrow keys to move it? I am so surprised by this setting!

I think it would be much easier to use annotations if they were highlighted when hovering or selecting an asset / frame / object that had one attached. Right now it’s a bit overwhelming trying to find the right line.  

It would be great to have the option of setting a max-width of a grid. Elements would stretch but always with a maximum value.

UI3 feels incomplete. There are so many quality of life features and ease of use benefits that UI2 provides that were taken away in UI3. The UI3 experience, especially for people who have been using UI2, feels like a significant downgrade to the user experience.  UI elements are more difficult to see and understand in UI3, like the layers panel - these new icons are awful, and it's more challenging to collapse panels with the new way the layers panel functions, which is very annoying.There are fewer helpful dialogs (example: UI2 says “Exporting” when it’s processing the export of images. UI3 just hangs there, no dialog, and it appears like it crashed...This is a downgrade to the user experience...Why was this ever changed?).In UI2, you can hover your mouse over any measurement setting, click it, and use your mouse to increase or decrease the value. In UI3, this interaction is buggy about 80% of the time I try to use it, and it infuriates the hell out of me. I feel like I’m relearning h

I’ve created this UI for Narrati through claude ai, I am not sure how to import this UI to figma, If there any figma AI which can convert screenshot into figma design, I want to shift this website to framer, thats why looking for a solution.Framer websites & figma is very same, if there any way to make screenshot to figma design, building framer websites become so easy.

It would be great to be able to use multiple individual variables for effects. For example, I have a blur and a drop shadow saved as two separate variables. I don’t always use them together, but sometimes I do. I would like to be able to use both together, without having to create a separate variable with the blur and drop shadow.