Suggest a Feature

Hey community, Would be amazing if in prototypes where there are components with scroll; whenever the component scroll reaches its end, top or bottom, then the scroll applies to the page. Currently is frustrating having to move the mouse from the component to the page (if any portion is available, in my scenario there is no workaround having full width data table sticking to the top of the viewport)

When you search for a topic in the community, you find a bunch of files. All is good. Say you click on one to explore it. Here’s the problem: once you’re there, you’re stuck. There’s no way to go back to your original search and see all the results and maybe explore diferent files. Clicking the arrows at the top left gets you back to a new search. I find it shocking that no one at figma has thought about this specific flow.

Hi everyone, I’m a teacher using Figma in a design class. We’re currently working on retro-engineering design prompts. For example, “design Spotify on Game Boy Classic”. The “pixel preview” option is perfect for that while in design mode, however, it doesn’t seem to be available on prototypes. This is 1980, we don’t want super smooth x4 retina anti-aliasing here!

We don’t need “git like” functionality in figma - git already does that. What we need is the ability to use git itself within figma and to integrate and connect with tools like gitlhub, gitlab, and bitbucket. Figma could use git in such a way - at a fundamental level - that you are able to use actual git from within figma (pushing, pulling, cloning, branching, merging… all of it) just like an IDE integrates with git and allows you to work with it from within the IDE. Figma doesn’t need to replace git. Git does a wonderful job of version control already; and, frankly, having figma do something like it would just add more tools that do the same thing to the workflow. In addition, your project would become split between the two tools and you would be separating parts of the team from one another as a result. By integrating git into figma you could keep all stages \ phases of your SDLC

When typing in the styles search bar, I used to be able to tap the up/down arrow to navigate between the results in the search. Now those arrow keys go to the beginning or end of the text in the search bar. This requires me to use the mouse to click on the object I am trying to select rather than being able to use just the keyboard.

Not sure if it’s in the correct place. Hello, Problem: Since we must leave a section unlocked to edit its items (children), a section can be selected and moved by mistake when editing one of its items. This is an annoying behavior and common in collaborative sessions, when multiple people are working on multiple post its, or items in general, inside the section. Possible Solution: A section can only be selected when clicking on its title in the upper left corner. Another approach would be to lock a section without locking its items (children).

The table functionality is great as a base feature today, but it’s impossible to see 🥲. If possible can the contrast and weight of the lines be increased to something a bit more accessible? The table is a really useful tool when it comes to planning activities. In the future it would be nice to be able to merge cells or import tables more seamlessly from Sheets, CSVs, etc. But starting with being able to see it would be great.

I work at a design agency and we use Figma for a lot of things. One of our biggest pain points is when we are getting content from a client. I know there is a comment feature but this isn’t in-depth enough. It would be best if the client could only edit the Text in the design. Something like dev mode where there don’t have to click threw all the auto layout and can just change the type. And maybe something where we can view a history of their changes. Thank you!

As an admin, I would like to be able to customize the Upgrade Request form. Currently, the form to enter a reason for the upgrade request is an optional textbox. How can I make giving a reason required? What if I could add language and/or a link so users can view upgrade requirements? (i.e., who’s eligble) What if I could add and/or make the textbox into a checklist? (for job titles, need to access certain features such as file sharing, etc.) What if we’d want the system to auto-decline requests for certain requests based on the answers given?

Hello! Here is some quick feedback from a new user! I notice you have a too low contrasts for gray text. That makes it quite hard for me to read. It would be very nice if you could improve the contrasts a notch. Here is an example: Thanks!

Is everyone else using Figma to create and showcase branding PDFs / Brand Identity PDFs for simplicity reasons ? Ok maybe I’m alone but I have been doing this for a while and I’ve always had trouble with the exports. My problems : Way too heavy files Some clients can’t see some of the slides The is no export window to play with settings. What I suggest → bring us the good old PDF export window that we can find in InDesign or any other software, so we can enjoy the final process of handling a fresh document to a client. Thanks for adding to the discussion !

When can we use the Figma Plugin API to drop Figma Widgets on canvas, this can be tremendously useful in creating a scaffold for designers to use, and grouping all useful plugins (atleast ones available within an org) to improve readability of the file, and discoverability of the plugins.

The Explore Community button is not easy to track due to the white color, same as the main color on the platform. Please differentiate it from the rest and make it easier to find it. 😃 Thank you!

It be great to see some sort of integration from Loop in to Figma. Bring in a loop component would be a great way to cut down on context switching between Loop where we do a lot of planning and writing briefs for Design sprints etc…

Wouldn’t it be cool to bring all features Adobe has to Figma? I know it’s a lot, just wanted to see if you guys are working on it. The Figma UI would end Adobe Illustrator easily. ☺️

This isn’t just an Idea. Consider it a feature request, as it is painful not to have this in Figma. 🤕 When discussing design options with a team, we often try to sketch ideas or highlight parts of the design as we discuss or review designs. However, using the current pencil feature brings a mess to the designs (it’s hard to remove all those lines from the designs, and sometimes small “lines” or “dots” can be missed). Adding a specific Brainstorm/Annotate mode (similar to how it works in Zoom) would be great so users can switch it on and annotate and sketch their ideas and thoughts. If there is a need to save sketches at the end of the discussion. It could be saved as a separate FigJam file.

I’ve found that basic search in Figma doesn’t give the all the files that contains the searching characters. Take a look at this example : I have a file named [SMT] eHandbook I typed the word “handbook” to the search bar but suggested results are nothing related to the word. Only when i type “ehandbook”, the result that i was looking for appeared

In our case, and in many other cases, developers are english-speaking, but work with a product in a different language. This means, that we as designers, create handovers that have both languages available. It would be great, if there were a better way to implement translations into a dev-handover, rather than adding text boxes beneath each frame (which is the current practice).

ability to organize/group prototypes in prototypes panel

A delete option would be very helpful or a recycle bin. Currently if we delete a file it is removed from the system forever. Or a lock option would work as well, where it is impossible to delete a file unless unlocked.

Can we include a feature in dev mode that allows us to view the original style that an alias name is referring to? In our design system, we want to use token names to enhance automation and streamline our process in Figma for designers. However, we have made the decision to avoid using tokens in our code base to prevent conflicts with Tailwind utility classes. Developers are not concerned about the alias name itself, but rather require the color class utility that it points to in the ordinal scale. To address this issue, I am currently implementing a workaround by appending the ordinal number to the alias name, separated by a pipe divider. This helps developers understand the position of the color on the ordinal scale. One potential solution is to enable a hover-over functionality on the alias name in dev mode, allowing users to view the reference style. Alternatively, we could consider adding an option in the hex dropdown to switch to the reference style, which would

Autolayout and variables work very good togheder, but it’s a pity we are stuck in using pixels. It would be a game changer if we could tokenize values in %, fr, rem and so on. Keeping the design really true to handoff means we must have the ability to use relative measures

Figma team, let’s have a chat. The Vision Pro is incredible. Can we please have a native visionOS app? If anyone can show designers how we should be designing for this new platform, it’s you. Show us how it’s done. Spatial Figma app.

Can we get Layout Grids for Sections? I use Layout Grids to organize my component variants, documentation boards, etc to quickly position annotations and specs alongside design elements within Component Variant Sets and Frames. However, with the introduction of Sections, I could get away from another level of nesting in frames if I just had the ability to use Layout Grids as well.

In addition to dev mode, I wish I could just look at the property tab that viewers can see. This would allow me to stay in the same overall space and see what I am selecting. Jumping into dev mode is possible, however, something about it is less convenient.