Share Your Thoughts

I was looking at library analytics and could not understand why there were no statistics for some components. Then, having searched for an answer on Google, I opened up the library’s publications folder and only then did I realize that there were errors in properties of these components. 👆In the screenshot, the broken components look like normal components It seems to me possible to display these errors directly in the analytics or, at least, highlight them more clearly in the publications window.

The ability to view analytics for color and text styles, the same way you can for components. So being able to see how many usages there are for a given style, and then drill into a style to see all the files that it’s referenced from. This would be super helpful for my team as the number of styles always seems to grow but never shrink. So being able to see which ones are rarely or never used, would help us in identifying which to delete.

Hello, I am working on a Design System and now I am adopting the interactive components. They look promising, but there is one feature that is missing. I was so excited and started adding interactions to all the bread and butter controls - buttons, checkboxes, radio buttons, switches, lists…etc., but then I figured out that usually, the prototypes are representing a few use-cases and not all controls are clickable. So I was wondering whether there is a plan to add a switch on the component level that enables or disables the interactiveness.

I want to know if it’s possible for me (as the owner) to set up something so all the viewers on a FigJam cannot see other viewers. So everybody on the jam thinks that they are alone on the file Thanks ! 🙂

I wish that there was a place to add annotations in the property panel, whenever the parent and child frames have the same size, it will be difficult for me to select the parent frame because the child frame takes up all the space, so that I have to select it in Layer panel and click “Add annotation”

Even before the last update, i found a few inconsistencies within Figma’s interface. The one that bothers my a lot is the properties selection menus. i’ll bring the Font family, Font weight and Font line height as examples.When Figma is set to light mode, the font family selection menu is in “white mode” and the variable selection in nicely located at the top. easy to reach. this is perfect.  The space letter spacing is also in “light mode” with the variables button extruded on the field itself, even better, but for the rest of the menus are constantly set to dark mode and their variable selection are placed at the bottom of the list. for fonts with long list this makes navigation very hard with a lot of scrolling. Please fix this inconsistency as specially the later one is the most inconvenience to work with.Thank you

Most times, I want to know what’s in the figma file or I am just exploring and want to see a file, all of that gets added to recents because in doing that, it opens the file. Now, my recents gets so cluttered because of all these.That’s when I remembered what happens to Community files.This preview gives a sneak peak of what’s inside, just how it would if you opened the file. I think when you are part of org or have a lot of figma files relating to similar things, this helps in reducing the load to think what was in that file or to reduce accidentally opening a wrong figma file. Would be great if a preview option is also available for all the files as well :)

Whenever im using the Actions menu (Cmd+K) to search a term in any of the categories: “Assets” or “Plugins & Widgets” and i select one of the results, after reopening that menu, the search term and category selection is being reseted. this causes frustration since im using this menu to search. im in a search mode. as a user i am not always certain i selected or found the option that answer my need. This pattern causes me to click again on the wanted category and re-enter my search term. this action is very frustrating.I suggest that category selection and search terms will be persistent as long as i did not delete my search term or ended my Figma session. Please consider this fix as the current situation is very frustrating. thank you.  

Hi, is there a way to copy the properties of a shape in FigJam and paste it onto another shape like we do in Figma but I have not found a way to do in FigJam or maybe there is a plugin out there that can do that? 

Subject says it all.

I want to add a youtube video inside my presentation, or add a link inside the presentation which people or myself could click

There are a ton of times where viewers add a comment by click-dragging a box around the item they are wanting to comment on. While this is super cool and I’m sure the comment thinks that doing this is helpful to provide context - and it is - it creates a headache if I am moving screens around and also want to keep that comment intact. This is really frustrating with large projects that have a lot of churn in the UI, and when there are a lot of comments.With a regular comment (no selection box) it is easy to do this - the comment, if attached to an object, will move with the object. I have searched for a way to convert the “box” comment to a regular comment but haven’t found how to do this. Could you add the ability to do this? Or just remove the box comments?Or is there a way to do this that I haven’t found? Thanks.

Hello Figma Team, Please add “Number” Variable function for Ellipse Sweep Property, It will so much of helpful to create Pie diagram for prototypes,

Following are a few things I found myself wishing for as I learned and used Figma Slides recently (it’s totally possible that you CAN do some of these things, and I just wasn’t able to find guidance on them on the interwebs, but I think I was pretty thorough in my search): Speaker notes section would benefit greatly from some not-too-major feature add-ons, like the ability to:Add comments/editing suggestions—When collaborating to build a presentation deck, our team wanted to give feedback/make suggestions as we built out the notes, but we had to find workarounds in order to do this. The ability to comment inside the speaker notes section would be hugely helpful. Better yet, having some baseline suggesting/editing capabilities similar to MS Word would be amazing. Use various text sizes and styling—to help build out headers, subheads, bullet/number lists, and to create emphasis (e.g. bold, italic, etc.) List styling—bullets, numbers, including indent levels to create hierarchy Add color

Now that we have the ability to make multiple pages in Figjam, I’m finding the need to consolidate some existing Figjams to create centralized files for particular projects or topics. As I move existing boards into the main file I’m creating, I’m unable to also move comments that are in the original files, and it’s 100% important to retain those with their corresponding layouts. For example, I had a board that was for a discovery phase, and there were many team comments added to it as we were learning and sharing info. I wanted to combine it with the board where we were now in the ideation phase so everything for this project would be contained in a single file, but I had to screenshot the comments from the discovery file and add them to the new file as images directly on the board, or drop them as images into new comment bubbles in the new file.Please make them portable between files in the future!

Hey everyone,I work extensively with Figma prototypes, and one functionality I feel is really missing is onScroll.the ability to trigger interactions based on scroll events (similar to scroll animations or parallax effects available in other tools).Does anyone know if Figma plans to add this feature in the near future?If not, are there any smart workarounds to achieve scroll-based animations within Figma itself without relying on external tools?Would love to hear your thoughts!Thanks!

When I use the shift-i keyboard shortcut and search for a component, I can’t differentiate between similarly-named components. The name is cut off after 11 or 12 characters. No additional info is shown on hover.Some of my components have similar names. Two examples are “toolbar experiment 1” vs “toolbar experiment 2” and “comp-input-search” vs “comp-input-string”. These look the same in this popover.How can I see the full names of the components that show up in this popover?

Hello, I think I’ve posted this, but must be in the old Forum.A really helpful feature to add to Figma would be the ability to control the order of items in design and prototype mode as they stack in wrap mode. This makes components more adaptive responsive capable across breakpoints, versus fluid responsive, which is just standard top to bottom order.Thanks,-Scott

This may be a hacky way to achieve what should probably be a standalone text decoration style (highlight)… but with the addition of underline styling, you can basically setup a highlightThe issue is that the underline appears over the text. It would be great to have to option to set the position or z-index of the underline to appear behind the text? 

If I add an instance of a component that in its master form is set to fill, and I am adding it to a frame with auto-layout, I want that instance to be automatically set to fill. That instances are always added as fixed width when the master is set to fill is an annoying inconvenience, especially when nested components also get set to fixed, thus requiring a whole process of fixing widths.

Designing an app using Figma involves several key steps. Here’s a concise guide to get you started: Set Up Your Figma Account: If you don’t have an account, sign up at Figma's website. You can use the web app or download the desktop version. Create a New File: Start a new design file by clicking on the “New File” button on your dashboard. Define Your Project: Outline the purpose of your app, target audience, and key features. This will guide your design decisions. Create Frames: Use the Frame tool (F) to create artboards for different screens of your app (e.g., home screen, settings, profile). You can set specific device dimensions (like iPhone or Android) for accuracy. Design the User Interface (UI): Use Components: Create reusable components (buttons, icons, etc.) to maintain consistency. Typography: Choose fonts and set text styles for headings, body text, and buttons. Color Palette: Define a color scheme that aligns with your brand or app theme. Add Elements: Use shapes

New UI or Old UI?Well, many others must have already asked this question, but what is the point of this bottom toolbar?In the previous UI, all the app's tools were located on the sides and at the top, which is actually very practical and comfortable to use.   With this toolbar at the bottom, this ends up requiring an unnecessary downward movement that is quite annoying unless the user uses shortcuts to access the tools on the toolbar, the main element in the UI, (on large monitors this is really annoying). A solution to this discomfort would be to put the toolbar at the top again or allow this adjustment manually.  Auto LayoutThe auto-layout button, even though it only had a + icon in the previous UI, had a label that indicated exactly what it did. In the new UI, the auto-layout is just an icon and the user needs to keep the mouse over it to know what it does, something that can confuse new users or those who don't know the "Shift+A" shortcut. ShortcutsSpeaking of shortcuts, holding "S

It would be nice and quick and efficient to apply to an elements or components variables or style via command menu.

When I swap overlays, I expect “On Click > Back” to swap back to the previous overlay. But it doesn’t work like that. I suggest adding a “Swap overlay back” action. It will help in cases when several overlays lead to another overlay and the specific previous overlay is known only while interacting in a prototype.

If you have many instances of a component, and you set props a certain way on the 1st instance, there is no way to quickly apply the same prop config to all other instances. “Paste to replace” does not work. “Paste properties” only pastes the visual properties (color, border…) In some cases (e.g. slotting), duplicating the 1st instance many times is not possible. → A “Copy/Paste component properties” item in the context menu would be very useful, and show an error tooltip (like for Paste to replace) if the target component is not the same as the destination one.