Suggest a Feature

Please show all prototypes when clicking out like the old version. New version so bad make me can not choose all prototype to edit quikly

I really interested in using FigJam, it works so well with me so far in studying, but it would be better that I could use my tablet to handy take note in FigJam

I know this data exists so why can I not view version history on a page by page or component by component history? Sometimes we get weird changes that no one on the team recalls making. Maybe it was a mistake? Maybe it was a merge conflict that was difficult to deduce? Who knows. We noticed something unintentionally changed and we want to track down when it changed, ideally, on a component basis (My team manages a design system) so we can learn what happened and take steps to prevent it from happening again. How I see this potentially working is selecting a component, or even variant of, and viewing its individual history via the property panel. It could just be dates there like we see in the file’s history panel, but then allow me to dig deeper and use something like the merge resolution UI to visually compare the current version to a selected historical version. Basically, similar to what we see in Dev Mode. Current version history capabilities are super generic, tedious to use, and

Hello Figma Community and Figma Team! I loved our last video for LBU and it inspired me to compile this list of things that I find are really beneficial to have in Figma and to teams in general. Please see the 17 new ideas below and feel free to contact me if there are things that need more explaining. 🙏 1. FigJam: Have the option to count all the Stamps without having a Voting Poll active, I do find it hard to track all our stamps and it tends to get messy when doing polls as sometimes we miss some stamps not being counted. 2. Variables: Have the option to move a Group to another Collection, PLEASE ADD THIS ONE 3. Text Tool: Having the ability to type text on paths 4. Component Properties: Having the option to allow a nested/child component to be duplicated within the main component. A good example is forms with multiple text fields 5. Variables: Having support for Padding in numbers 6. Text Styles: If I have a text style applied to a paragraph with regular weight if I highlig

We need German languages

This goes for all web apps actually. But my guess is that it’s a simple change to fix that…

When you lock a layer, the editor should show a lock icon next to the frame so that it is easy to spot if a frame is locked. Additionally, the icon can be a toggle (like “Ready for Dev”) so that people can unlock and lock without digging through the well-named layers that we designers clearly do 🙂

The settings for line height and paragraph spacing. These features are very effective for single-line text editing but can be inadequate when dealing with multi-line texts, especially in the design of documents or user interfaces. This is particularly true for scenarios that require fine-tuning line heights for multiple lines of text. I suggest that the Figma team consider adding a ‘Multi-line Text Line Height Setting’ feature. This would allow users to set line heights individually for multi-line texts, thus providing greater customization and flexibility. As it stands now, the font variable seems clunky

Hi all, I work on a design system team as part of design ops. we run a hybrid design system model so product teams actually manage their own theme libraries with our “template” library. current behavior in Figma: insert a global comp swap global theme lib to brand theme lib insert a new global comp swap theme lib again just so this new comp can have the brand colors problem statement as a des ops person, I want Figma style library swap to match by all styles rather than just visible styles in a file, so that when a new comp is inserted there is no need to swap styles library again. potential solutions as brainstorm: link all styles via ID or some kinda of meta data in addition to the name (name still need to match otherwise we create communication gaps on brands using their own styling names)

I’m having issues while merging a branch some edits that I might have done by mistake (eg deleting a page) it’s not possible to ignore the edit and revert to the original content. The feature, I’m requesting is like having a history of different pages / section.

Ability to copy, move, and swap (re-link) Quality tool Having a tool to evaluate unassigned surfaces for variables would be beneficial. It would aid in determining the closest variable color that can be assigned to them.

auto layout is very cool, but its functionality is limited. It would be really cool to have a table so that in each cell you can insert an object, text or picture, whatever you want. And for each cell to have its own independent alignment.

Using alias variables: Creating a conceptual map of variables would benefit both designers and developers. Conceptual maps serve as an excellent visual aid to illustrate connections. In the development phase, when checking colors in DEV mode, developers at the moment not have a clear view of how variable structures are organized.

i want to have different icons / images for different modes for icons, i have made them as instance is there a way to do it that i missed?

Clicking a tab in Figma opens the tab in a new window, this is very annoying. It started happening after I updated my mac OS.

When I click ‘publish assets’ and then use the search to narrow down what to publish, the search covers up the description sneakily, and I always forget that I have to close the search to add a description. Sometimes, I click ‘Publish’ thinking there is a next step—after all, that’s what I did to get to the step where I can add a description. But no, it actually publishes. I tried to cancel…but it didn’t work. And I can’t add a description retroactively. Please make this experience less susceptible to human error.

I would love for Figma to know about the basic HTML elements. This has been suggested before (HTML elements, CSS layouts). I really enjoy how the UX world is moving away from using graphic design tools (I started with photoshop, personally), and towards more integrated workflows. I also understand that using graphic primitives (lines, rectangles, circles) makes Figma more versatile and usable for other UI technologies… But it also generates quite a bit of pain in my everyday UX live. Handing designs off to devs is made much harder because we will always have to explicitely discuss the mapping from Figma rectangle to HTML button/input/section, or else include some type of documentation. In multiple projects, I’ve seen different cumbersome ways of doing this: comments, naming layers so that they correspond to HTML elements, or adding tables with documentation under each frame in Figma. It also means we need to teach UX designers enough HTML so they don’t think up things that can’t be imp

Currently FigJam keeps color and stroke setting from shapes, but not the filling. Is very annoying have to set which type of filling I want every time. Also would be nice to have more customization on shapes and connectors as suggested on “Advanced Figjam Tooling Please”.

At the moment, right click and left click both activates the top toolbar actions. It would make it quicker for me, if right click would open the dropdown menu with additional tool options (e.g shape tools) so I don’t have to aim for the small arrow next tot he tool every time.

Is it possible to generate Figma URL based on version. I want to publish a version of Figma designs for any changes withing team.

I’m working on a 20-page file and often switch between Dark and Light Mode UI, based on how my eyes feel. I’d like to have the ability to change a file’s page color to my preference and apply it across all pages in the Figma file with a simple button. Perhaps a “Apply to All Pages” button in the Page color panel would work. This way, I wouldn’t have to change the default F5F5F5 page background color on each page individually. I also don’t want to control this UI element with a variable (I see that as an option), as I anticipate my developers getting confused when going through my variables and asking: "What is a Page Background, and where is it applied?”

There is inconsistency between what is shown in Figma UI and what is sent in response for Figma file (GET /v1/files/:key - https://www.figma.com/developers/api#get-files-endpoint) related to letter spacing for Typography token. It’s possible to declare letter spacing using either pixels or percents, but in API response we always receive values in pixels. It would be really nice to know original letter spacing unit. Here are 2 different typography with 12px and 12% letter spacing and their representation in API (GET /v1/files/:key): As you can see, we can’t build our interface for this letter spacing unit that would match values configured in Figma UI. So, it leads to inconsistency for our users that see percent values in Figma but pixel values in our UI. Or vice versa: if we convert all pixel letter spacing to percents, then people created letter spacing in pixels would see another value in percent units.

The resources pop-up should remember if you’ve choses “Local Components” and the view type. At the moment it defaults back to “Recents” and grid view, when I prefer different settings. This button is a cool alternative to having to switch between Layer view and Asset view to get to my components, but if it keeps on resetting each time I click off of it it has no use whatsoever.

We use Figma to create one-pagers and guides. The issue is that when exporting to PDF Figma automatically outlines all of the text. You lose the ability to make an editable PDF with acrobat because all of the type is a shape. It would be great to have the option to retain the type when it’s exported. If there’s an option to fix this lmk.