Share Your Thoughts

I often need to record a video of my prototype being someone who works async. I know there are screensharing/recording platforms out there but it would be so amazing to be able to record my prototype and share a link that can just play in figma. 

👉🏽 Did you allready experience the frustration of typing out a comment, then needing to check the name of a frame or another detail outside the comment section, only to lose their entire comment? 😭 Ideas 💡 When a user begins typing a comment, the system should automatically save a draft of the comment at regular intervals (e.g., every 10 seconds). If the user navigates away from the comment section or the page, the draft should be preserved and restored when they return to the comment section. Provide a clear indication to the user that their comment is being saved as a draft (e.g., a small “Saving…” indicator). Include an option for the user to manually save a draft of their comment. Ensure that the draft is retained even if the user logs out and logs back in, or if they access the project from a different device. Thhis functionality will significantly improve user experience by preventing the loss of comments when users need to navigate away from the

I’d like to suggest a feature that would be turn Figma Libraries into version controlled files where the publisher can push updates to the community. The way it currently works is that the community downloads a copy of the library and then must publish it to their team in order for them to consume that library. Under this new model, libraries will always be tied to the original community publisher (say Google, or Apple, or anyone of us) and they can push updates to their libraries as they update them. Users are able to consume those changes or reject them and stay on an older version depending on the project needs.Essentially, Figma Community Libraries should work the same way Github works.

While “Open Overlay” offers granular control over animation styles, including starting position and transition, “Close Overlay” is limited to a dissolve effect. For example, an on-screen keyboard that slides up from the bottom of the screen with precise control over its starting position and animation looks natural. However, when closed, it abruptly disappears. I want the ability to define a smooth slide-down animation for the keyboard’s dismissal, matching the opening animation for a seamless interaction. I hope Figma will consider adding animation options to “Close Overlay” to provide designers with the same level of control for both opening and closing overlays.

I think it would be great having a widget/plugin to include Hubspot’s form within prototypes (as Framer does 😉).

How to change position of annotation. It would be better to show/hide annotations from context menu (right click, Same as hide/show comments)

Our dev team love the Focus View mode, but it is somewhat cumbersome to go back and forth between the normal ‘File’ view to the Focus View. To switch you either have to click the arrow, which either brings you back to the Activity Feed or the File, or use the 3 dots + clicking on ‘Inspect on page’. What about a simple toggle switch between Focus and File view? Why hide ‘Inspect on page’ behing this three dots if there’s only two options in there which have very different purpose:  

If there is an option to duplicate the Text Styles / Color Styles folder then it makes it easy when creating design systems. Attached is a screenshot of the idea.

Add option for sharing a deck with show left panel with slide thumbnails for quick navigation. It’s impossible to quickly navigate and jump back-n-forth 20+ slides decks. There are tons of habitual and rational use cases for jumping between slides manually. 

Problem:While Figma’s Prototype mode is great for building realistic interactions, it quickly becomes visually overwhelming—especially for those who don’t use Figma in their day-to-day. This often leads to a deer-in-the-headlights situation, where communication breaks down both internally and externally.  Collaborating with teams outside our organization becomes especially challenging when trying to get them to understand the user interface from a high-level perspective. Solution:Our company has found the need for a deliverable that sits between static screens and a full prototype. It’s essentially a wireflow but with completed UI. Think of it like Prototype mode, but without the spaghetti mess.I’m calling this concept “Proto-to-Flow.” Figma would analyze your prototype and generate a simplified, flowchart-like view showing only the primary user path. Each screen would be numbered for easy reference, with the option of hiding secondary or edge-case connections.This view would help comm

There are a number of ideas related to this, but none quite capture what I think would be an obvious workflow improvement: when selecting an object with gradients, it would save a lot of time and effort if the gradient colors appear in the ‘Selection Colors’ section on the right hand panel, and are editable. (Bonus points if those colors can use swatches/variables, as others have mentioned—it would give users the ability to do a global edit!)

Hello, I’m writing as a frontend developer. I received a figma UI design, but I only had viewonly privileges. Because of this I couldn’t see some hidden layers which were a different aspect of a UI element. I know this situation can be avoided by the designer, if he makes prototypes to show the different aspects or simply makes the design editable for the developer. However I still don’t see the point of hiding the visibility switch for viewonly users. Please make it available for everyone. If this issue was discussed before I apologize. Anyone faced this problem too?

Its not only me, the designers I know have the same changes when they would like to create team and folder.

i am suggesting to allow us to select multiple components from the stage and publish all or selected, beside the option to create variantscoz after some updates and modifications, publishing from the library window becomes a challenge. some updates i don’t want to publish. sometimes it’s hard to follow the naming as well. and i believe as designers, visually it is easier for us, since we know where and which components we want to publish on the stage. i see this very similar to the new create component update in the new UI. you are allowing us to select multiple frames and select if we want to create a single component or multiple ones at once. to visualize, maybe something like this. and of course there is the publish changes option, which could follow the same approach, or a drop down like the component creation. anyway, the main idea is selecting from the stage to publish. does that make sense?

 Hey Figma Team, Community. I love the new variables system and the ability to change appearances. However, I came across a reoccurring problem in the last weeks: People with only view rights, are not able to change the appearance of a component or frame. This was something we designers weren't aware about. Is it possible, or maybe already in scope to allow people with view rights only, to change the appearance mode? I think this might really help and keep files slim and clean without making lots of copies and changing appearances modes.Let me know your thoughts, thanksJonas

When the title of a page is wider than the column it gets an ellipsis. Right now the only way to see the full title is to edit the title since there is a limit on how wide you can make the sidebar.Please just add a tooltip to titles that are wider than the column, IE when they get ellipsis.

为什么不中文？我真的很想用它

I think it will be very nice to edit files on the iPad.

Hello!Gamedev designers have been adopting Figma more and more into our workflow, and we would love more controller support for better prototyping and navigation options. Some examples:Better joystick radial support. We currently only have up/down/left/right stick movement, but to prototype menus like weapon wheels and radial selections we need more precise input. Hold button + long press button options for D-pad, face buttons and shoulder buttons. Support for swipe gestures on the PS5’s touchpad.To do any of the above we currently need to jump through hoops and map controller inputs to keyboard buttons through 3rd party software, which is not great and doesnt work for many of the above options. If the community has more suggestions, please leave a comment below 🙏 Thank you!

In the design tab, you have a panel of created property options shown at the very top, and in full size, and often when you need to change an instance, you need to scroll first one panel, then another, and they can have a lot of content, which makes navigation through the design tab very long and not intuitive, to simplify the task, create the ability to show part of the parameters for each panel, with the ability to expand it by hovering

Prototyping triggers won’t allow to bind an action to diagonal moves of the stick. Both LStick and Rstick. Tried to prototype a command wheel. Segments should be triggered by eight corresponding directions of stick movement. But only four of them was possible: up, down, left and right. Does anyone else in the game industry experience this? Is anyone using a plugin or workaround to help solve this?

Hello, Someone already posted this, but i was too late to see it, so im posting again. I have a very similar issue. For my part I find it almost impossible to see where a comment should have been if you’ve already moved things around and of course simply Showing Version History doesn’t include comments even if they were present in those versions. I’ve had to rely on context clues and directly asking the commenter for clarity when this happens. Below in quotes was the original poster’s issue “Would the Figma Team please show comments in the SHOW VERSION HISTORY? Right now, I look at comments in the current version, inspect the SHOW VERSION HISTORY, and take a screenshot to see where an orphaned comment should go. And I will look at the comments and the versions because I want to see the state of the wireframes on that date. Thanks for the consideration!”

I’ve been switching back to UI2 just because of the toolbox being on the top left. I cannot get used to having 2 docks on my screen as it just looks weird. If possible, just make the toolbox draggable so I can move it up there or just add a setting for it.

So If text overflows from one, it can show up in another textbox. This would be useful for two-column/grid composition and responsive layouts.

In addition to having AI design the entire wireframe (which results in a lot of output that isn’t really relevant or useful to the user’s specific needs), Figma should implement a version of its AI tool that improves/beautifies user-created basic wireframes (eg. takes the text/button names/general layout that someone has already created and adds colors, changes typography, moves things around so they’re visually more pleasing, etc). This would allow users who have a general vision of what they want their product to look like to save time creating more detailed wireframes so they can more easily transition to the prototyping phase.