Share Your Thoughts

Please allow us to quickly create a local master of a shared component and replace the current instance with that new local version. Requiring a detachment before making a new component loses all of the variants, etc. of the original component.

Love the new Tables option and it really helps organize and track work. However, being unable to use sticky notes, shapes, community widgets etc in tables prevents it from being used with the rest of FigJam potential. Would love to see this feature be available.

Sometimes text do not fit into default shape size. Such shapes feature ellipsis and a drop down to expand the shape. It would be great to see full text on hover in such cases, as you might not always want to expand the shape.

Main problem: I often accidentally press cmd + t when i want to just replace content with cmd + R. This is frustrating since this opens the New file window. I always quickly press Cmd + W to close the window and get back to work, but this is not taking me back to my working file but instead switches to a (random?) file in my tabs. So two problem here: Cmd + T is too close to a often used shortcut (Cmd + R). Cmd + W doesnt take you back to previously active tab

If I have two files and I can’t decide which file an object/frame/pageg should live in, I’d love to be able to embed a live/syncing view of the frame into another Figma file. I imagine it working like a PS Smart Object where you can double click or something similar to jump to the original to edit it if needed. Right now, my best option is adding a button widget or link to the frame. You could almost do something similar with components, but I feel like it’d end up clogging up the component libraries if used for this purpose. Thoughts?

I have an idea for a new Figma feature. DEAR FIGMAAA, Please make the name of a variant visible above the frames of the components. See screenshot what i mean for concept. I think it will help designers and developers a lot. Current situation is you only see the names of “normal” frames and single components …

It would be ideal to have a comments feature WITHIN the merge review dialog. Similar to other code version control tools (like Chromatic for Storybook), it would be ideal to be able to have a discuss/comment area in-context of each updated element in the merge. Currently, the work around seems like that people have to first find exactly what it is they want to comment on (listed in the Merge dialog), and then go to that object in the file/page/canvas, and comment there? The downfall of that is those comments on the canvas get lost with the merge/branch. In addition, having a description accessible for each branch after it’s been merged, would be beneficial too. Similar to this request: See branch description after the merge Thanks for the consideration, and I recognize that this feature is very complex!

I believe the section’s reaction to mouse is inconsistent. If the entire section is visible on screen, it is highlighted on mouse hovering anywhere inside the section, and it is selected on mouse click. If no section edge is visible on screen, it is not highlighted on mouse hover, and it is not selected on mouse click. But if any edge of a section is visible on screen, it is not highlighted on hover, but it is selected on mouse click. I’m so much used to clear the current selection by clicking on the whitespace, this is a second nature to me, and I do it without thinking. The current section behavior makes me constantly check if the section got selected when my intent was to clear the selection. Considering that every other selectable canvas object in Figma is highlighted before being selected, you can always tell if a mouse click is going to select that object. Section makes an exception here for no reason.

I hope that within a file, one or multiple frames can be set to ‘visible to me only’. Regardless of whether the person who created this frame is the original creator or a past editor, any frame they establish and designate as ‘visible to me only’ should solely display to them and not be shared with other collaborators. Please take into consideration challenges related to changes in user permissions, as well as issues of file duplication, cloning, and how this type of module might be compatible. Apart from frames, the same applies to pages within the file. However, the number of pages is constrained by your policy of allowing only three free pages; it might be worth assessing its commercial potential. Lastly, I’m looking forward to the smooth launch of the ‘visible to me only’ feature for frames and hope it will be available for free use. 希望在文件内，某一个或多个frame“仅自己可见”，无论创建此frame的人身份为创建者或曾是编辑者，自己创建并设置的“仅自己可见”frame，将只对其自己展示，不对其他协作者公开，请考虑用户权限变更或文件复制克隆等问题，以及该类型模块如何兼容。 除frame外，文件内页面pages也同理，但是页面

Addition to the current variables Add and manage multiple sharing links for different modes Restrict mode view access per link (e.g. a client is provided with the link that has their brand theme mode) Great for white labelling

Why can’t I connect to the team component library after creating a new project?

AUTOMATIC FIGMA TUTOR 💡 Create a step by step interactive Figma tutorial from a Figma file or component Similar to: ScribeHow (creates tutorials by tracking what button was clicked in the website) but in Figma Pros: create tutorials for a certain component using its version history from contributors (Figma community or others) easily follow step-by-step tutorials of trendy design components in Figma points & highlights which button to click in Figma along with an AI text generated instruction share interactive Figma tutorial with others Impact Increase the number of tutorials, tutors and contributors in Figma Easy access and sharing of tutorials to the public Market Opportunities easy creation of tutorials meant an increase in number of Figma tutors selling interactive Figma courses possibly on the Figma community or on this “imaginary social platform” Possible Issues: Unnecessary changes may be recorded and might hinder tutorial process Some changes may be lost in

Currently when the gradient window is open the shortcut doesn’t affect the object, so it could be used to flip the gradient instead. In some scenarios it could also be useful to flip vertically. Both shortcuts could work on bitmap fills too.

I frequently utilize prototype mockup features when sharing prototype links with clients and colleagues. Currently, I design web and responsive/mobile versions side by side to maintain a consistent visual aesthetic across both platforms. However, when it comes to sharing them as links, I must relocate one of the versions to a new page and adjust the prototype settings to display it as a mockup. This approach also complicates the review process for Figma files as it becomes challenging for reviewers to switch between pages. I believe it would be more efficient if we could apply prototype settings at the page level, with the option to inherit settings from a parent page if nested. This would allow us to have both mobile and web designs on a single page while using distinct prototyping settings for each.

Font missing error while login in from a different computer. If possible to embed fonts within Figma file/project will be very useful. this feature is present in Sketch.

Considering the fact that scss is much more powerful than vanilla css, and Figma showcased double linked variables of the type that are being used in scss code, it would make so much sense to suppport scss out of the box alongside with vanilla css This is really powerful and would make implementation of DS that much easier. Otherwise, supporting just CSS introduces the problem of having color names like body-color that just translate to #000 instead of color-neutral-100 for example. This would make so that devs would have to manually look up hex adresses in the main color definition file to understand what colour variable name “body-color” refers to if they would be using SCSS

Restricting the level of zooming out was a terrible idea, or at least terrible execution. It used to be much easier to navigate, just by zooming out to bird’s eye view and then back where I wanted to go. And I don’t who thought that the current implementation of this restricted view is okay to be rolled out but they probably haven’t been using Figma on a daily basis. It is now possible to lose frames – they can get behind the right edge of the screen so far that they can’t be dragged back. Ridiculous bug like this have never appeared in Figma before. It feels like there’s a new management and they don’t know what they are doing.

In the “Used in recent pages” section, I suggest a user-friendly way to keep track of where a component instance is used within the current project file. Simply by clicking on an item in the list, a sidebar will appear, showing you a comprehensive list of all the places where that specific component instance has been used in your project. Moreover, clicking on any item in this list will seamlessly navigate you to the exact location where that component instance is used. This feature is designed to make it effortless for you to locate and edit components, enhancing project organization and ensuring you never miss any important details.

I often need to know if the root of a component instance is local to my project or not, and so I find myself using “Go to main component” just to find out. I think something like this to indicate that the root is outside of the current project would really help. Option 1 Option 2

Sometimes, I want to identify all shapes matching a color that isn’t yet assigned to a variable. To identify them, I click on the button labeled ‘See all n colors’ to initiate the identification process, having the following options: Click the ‘See all n colors’ option, then use the color identification feature. If I select the wrong color, I must select the entire frame again and repeat the process until I choose the correct one. Change a color to a random visible color to check if it matches the layers I want to identify. If it doesn’t, I need to ‘Cmd + Z,’ click ‘See all n colors’ again, remember my progress, and try the next color until I find the one I want. Adjust the opacity to 0%, then return it to its previous level. This method “works” when the color has sufficient contrast. Proposed Solution: Implement a feature that allows color matching selection direct from the canvas.

Issue: Sometimes I need a guide at a specific location, IMO it should snap to the nearest vertex, but occasionally it doesn’t, requiring manual adjustment. Proposal: Snap guide to nearest vertex or, alternatively, have it snap to the selected vertex. Here is an image illustrating the current behavior:

Hopefully something that is already in your backlog but we need a way to set variables etc. on entering/exiting a screen via a ‘navigate to’ interaction. An example use of this is to store the last user entered value for a variable so a back/undo/etc. function can restore it. I’ve tried to hack this using ‘after delay’ set to 1ms at the screen level but this fails to trigger reliably. onPrototypeStart/End would be very useful too.

Please add scrolling of hidden content directly in the canvas. Otherwise, I have to constantly check and uncheck a scrolling area’s clip content checkbox when flipping between the prototype and making changes in the canvas. I should note that this wouldn’t be needed if Prototypes that fill viewport was implemented.

Please allow an object to be pinned to the side of a container without having to manually position it. Dragging an absolutely positioned object is imprecise and error-prone. It would be better to make it like CSS where you can enter numerical distances from the top, right, bottom, and left sides and have the object automatically honor the values. Here’s a graphical example:

Please allow frames to fill the user’s viewport while viewing a prototype. This will let both the designer and the viewer to get a better sense of how a page will feel in the real world and eliminate the need to set frames to be some arbitrary lowest common denominator size when a prototype features scrolling sections. It will also set the stage for responsive prototypes whenever Figma adds those.