Share Your Thoughts

I still consider myself a newbie in Figma (this is a caveat), though I’ve had a chance to play around with it. My hope in using Figma is that it will make it easier and quicker for those collaborating with designers - mainly PMs, Devs, and QA, to find the designs they are looking for. Coming from Invision, it was a pretty bad experience (sorry Invision), and after checking out Figma and other potential solutions out there, I was sold on Figma (for many reasons), and pitched it to my client. Now we are going in. An important contextual aspect of this topic, is the fact that many, if not most doing software development these days, follow some flavor of agile development - so think epics, stories/tasks, and sprints, for example. So the challenge here is, how to best match up the agile development process, to how everything in the Figma design space is organized, so that designs are quick and easy to find, not just for the figma designers. I was hoping

Just now I tried to use the common ctrl/cmd + K shortcut to insert a link to the selected text. To my surprise the keyboard shortcut changed to something else (don’t remember to what, don’t care). The ctrl/cmd+k key combination is common and vastly used in text editors, desktop apps, and web apps. I know only 2 apps that does not comply with this de facto standard: Slack and now Figma. It would be great if you consider using commonly used standards.

It would be nice to have an ability to mark a page inside a project as archived. This is for anyone who accesses the project to understand that the page was archived and should not be considered. However, there’s still a value of keeping these pages in the project to have a reference to a different design directions considered in the past of removed features. An archived page is in a read only mode. It cannot be edited or commented on. It also is somehow marked as archived in the Figma UI. Today I usually create an empty page with the title “Archive” and everything below it is considered archived but it is not a standard way of working with archived-but-still-useful pages.

In my files I have some core mobile designs, and then I usually have a section that points out changes when it gets to tablet size. Or, there could be sections that have background information in them that isn’t needed to view all the time. It would be nice to be able to collapse/expand sections so that upon first view of a page it’s not super cluttered. And then, should you need to expand the sections, you can

Good morning ! Given that we can put keywords in a description for each variant, is it possible to display the variants directly in the asset list, in relation to the words entered and present in the description? Because currently if we enter a description in each variant of a component, when we type a search with words present in a description of a variant, it only displays the main component directly and not the direct variant. Thx you !

Use case: I have a product card with a main image and a row of color swatches underneath it. Right now, clicking a swatch updates the product image to the correct color via setting a string variable (e.g. on click, set variable to “Product_Blue”). It also give the swatch a black stroke indicating it’s the selected color. So far so good. I would like to add functionality where it updates the product image while hovering but then resets it when the mouse moves away. This is currently impossible, as the variable reassignment sticks. This thread suggests using mouse enter/mouse exit, but this doesn’t work in my example because there are as many possible mouse exit variables as there are swatches (how would we know which swatch was selected before hovering over another?) So, I’m proposing that there be a way to set the value of a set variable action to “default”, AKA whatev

I keep stummbling across the same weird UX when you copy/paste a child frame and it pastes outside the parent frame (only occurs when there is one child in parent frame to begin with) - for context I’m using auto-layout.

In my company we work with a lot of sheets, so we created components with what Figma can offer as functionnalities, but they are very limited and absolutely not flexible. So we have to break the connection in order to adapt the content. It would be amazing if Figma released a function “sheet” to create sheets easily: insert/delete column insert/delete row merge cells … etc Just like in an excel for exemple

Hey everyone, I’m writing to suggest a feature that would significantly improve the flexibility of Figma’s text styles. Currently, once a text style is applied, it’s not possible to modify certain settings like letter case, number style, letterforms, and styling sets. This limitation can be quite inconvenient, especially when working with complex typographic layouts or tables. It would be incredibly helpful if we could adjust these settings directly within the applied text style. This would save time and effort, and allow for more precise typographic control. TL;DR: Allow changes to Details tab settings within applied text styles.

Would love for Code Connect to support Angular dev to speed up our process

The blue interaction box is helpful for prompting which elements can be clicked in a prototype. All components with interactive states, even just hovers, now have blue interaction boxes - even when they don’t really do anything useful like navigating or launching a modal. I’d like some level of control over which variant interactions are visually prompted, or some smart defaults (which Figma is awesome at, thanks team!)

I think this might be a bug. Currently, there is no way to see the description defined for a variable inside of a collection when viewing variables in the Color panel. This makes it difficult to determine which variable to use when a team has a large collection. Please show a tooltip on hover, similar to how Styles behave on hover. Only way to see the description is by going into the Variables settings where the collection

It would be useful to have a way to see all files within a team (across all projects), including owner info multi-select and transfer ownership in bulk This would allow to quickly see and fix ownership issues, which currently has to be done on a per-file basis (and requires to check all files to find issues to begin with)

I understand the idea behind reorganizing the action bar and making the component settings appear first in the list of actions. Still, it really annoys me that position control changes place every time. I need to make an effort to find it whenever I change the element selection. So I think that allowing users to customize the location of different actions in the right action bar will be useful. This allows you to organize the list as you prefer, making it easier to utilize in future tasks.

Hi everyone! If I am in “presentation mode” and I notice that there are problems on a particular page, I have to go and look it up on the template to fix it. It would be interesting if the cursor we have in the presentation could represent where we are even when we go back to the worksheet. So that we don’t have to look for the page, but know where we are! It would make the work much easier!

Hello! Is there a way to cache a prototype thats embedded in Slides, when presenting? Let’s say I present in slides, click each slide that has a prototype, and load it, and return to the start of my slides. When going back to each slide with a prototype, it has to reload. Instead, can we cache the prototype, once you click it, and if we need to update the iFrame to pull in changes, we can by like some button in slide that says “Update to latest” or something? 🙏

Would be great to give the Updating Assets alert a greater visual contrast as in dark theme, it’s hard to see it appearing.

Hate to say it but wow for a design company the Figma UX is tragic. Just realized that after 2 years of using it one of the docs we have been using is in my “personal” account apparently, and our company account billing stopped? That account is now “locked” So I wanted to find what card it was billing against and… there is NO WAY I can find to figure out how it used to be billing. The ONLY thing I can find after far too much time trying to figure it out is to just add a new payment method?? Seriously. Too painful to even bother at this point. I’ll just stick with the free account until I feel more like dealing with this awful UX.

For the files search, it would be helpful to focus the search within the context of a specific project (or projects). Background: We have projects for each platform (e.g. web, iOS, Android, etc) which are in progress and other projects for features that shipped or were archived. So it would be super helpful to limit the search results within one of those projects that represent different contexts (shipped/archived, active, etc). Anyone else have a similar model and found a workaround? If not, upvote this baby 👍

Standard user behavior (even in such a simple platform) is ability to resize text boxes by both width and height. Feels very limiting right now and as you add more text boxes, you end up with a lot of overlapping boxes because the height can’t be resized after creation.

Suppose there are multiple frames in one frame. there should be an option to convert the frames into objects or rectangles with the same properties.

Could be great to be able to resize element by frame rate, percentage, viewport ratio, etc. aligned with CSS possibilities.

When we select two layers from the top and bottom and press Ctrl + [ or Ctrl + ] to adjust the positions. These two layers should come closer like in photoshop and move upward or down. Unfortunately, these layers maintain their position (with extra layers in between) in the frame and move around.

Problem Description The Issue: When naming frames or layers in Figma with special characters such as /, Figma interprets / as a path separator. This leads to the following problems: During PNG or other format exports, Figma automatically creates nested folders instead of exporting all files into a flat directory. Designers who use / as part of their naming conventions must manually adjust or reorganize the exported files, adding extra workload. There is currently no option to disable or customize this path-separating behavior, forcing users to manually rename layers or rely on plugins. Impact: • Workflow efficiency is reduced, especially for designers who frequently export and manage large volumes of assets. • Using plugins or manually renaming layers can disrupt the semantic meaning and consistency of naming conventions.

While it is possible to stack different stroke colors, they all have the same width, which limits their usability. Adobe Illustrator has the ability to stack several strokes on one object, all with their own properties. This allows for example for lines to have «halos», which can be useful when used in front of busy backgrounds.