Share Your Thoughts

String variables are all fine and well. You can’t use them as input to components, which makes them somewhat unusable, but they’d be all fine and well if you could. The existence of strings, however, does leave you wanting more interesting data structures to use while designing. On that note (provided that the abovementioned component-input-issue is resolved) I’d like to have the option to use json in my designs - this would make it much easier to prototype using realistic data while also providing an opportunity for generating sample input data to stress-test your design (the latter probably coming from plugins). For example, I would like to use the following “projectData” json as a component input to a “projectView” component: { “projectName”: “MyProject”, “projectCreationDate”: { “year”: “2024”, }, } In this view, any text field named “projectCreationDate.year” would resolve to 2024, any text field named “projectName” would resolve to “MyProject”. I’m sure there are more clever ways

Hello, It would be immensely useful if I could see a list of all components (with variant indication) and variables used per page / file, and be able to compare that to the entire list of components / variants / variables available in my design system. This way it would be easy to spot any unused component / variant / variable in the design system and purge it. Thanks

Maybe the overlay functionality was originally designed to simulate modals. But two (unnecessary?) limitations limit their power for other applications: The fact that I cannot have more than one overlay open The fact that I cannot interact with the area outside the overlay is very limiting Please allow for having multiple overlays and for interactions outside of an active overlay. If you need regular modal behavior, you can still have that by checking a checkbox (off by default) in the Figma UI. Limitations like this mean I have to back & forth between Figma & Protopie. I fully realize that Figma may not be aiming for HiFi prototyping (text fields, conditionals and even sensors). But just a couple of well designed tweaks and features will enable me (and probably others) to do 90% of my prototyping in Figma… Example: Image you have an image grid with smaller images. Clicking an image will make it go full size. A prototyping execution for this is loading an overlay with the b

This is a simple thing that should existed long before they released Figma, right?

We badly need this feature in Figma. The time tracking feature allows designers to keep track of how much time they spend on each design project. For all product designers, it is incredibly helpful. Investors will occasionally demand to know how much time was spent on their project. That’s why we need this feature in Figma.

I would like to be able to search for a colleague and jump into the board they are currently looking at. There are many situations in which I am in a call with colleagues, and they want me to follow them. It always takes some time to find the correct board they are currently in. We tend to tag each other in comments or share links to the board, this however is disruptive to a presentation or meeting. I would prefer to be able to easily find a colleague regardless of what board they are in and to also be able to follow them across boards.

During the user tests it’s important to show scrollable areas in the prototype. Specially for desktop prototypes. This should be a default behavior.

I have 12 pages in one file, but I can only see a maximum of 5 in the menu viewport. Anyone accessing my FigJam document would have trouble understanding the structure, especially since the pages list collapses every time I close the file. I’d prefer an experience similar to Figma, where my pages are always visible. To help mitigate this, I’ve added an intro page that shows the list of all pages.

“When I’m browsing community resources in an infinite scroll format and click on a specific resource to view its details, can I be returned to the same spot I left off at, instead of going back to the top of the page?”

We maintain a single design file for a feature and iterate within it. It would be helpful if once a design is complete, we could lock the frames, or instances of components, within the frames so they no longer receive component updates. Being able to reference previous versions of a design is critical for us, and the way libraries work right now breaks this. (edited to be more clear - locking instances of components)

Our design system file is view-only for basically all users. We have typography styles for desktop and mobile, which are defined in variable modes. But as a view-only user, it’s not possible to see whether text is using the desktop or mobile variable mode. A user should be able to see which variable mode is active even in view-only. Even nicer, a user should be able to view the variables and modes in view-only.

Hi there, while working on a slide deck, I deleted a slide by accident. It was autosaved and I could see it in the deck version history. Unfortunately I’m unable to retrieve it and add it to the current version. I tried: copying the slide (from the navigator on the left) in the autosaved version and hitting “paste” in the current deck version copying the slide content (selecting everything in the slide > Copy) in the autosaved version and pasting it in a empty slide in the current deck version duplicating the “old” autosaved version as a new deck, and copying from there. It seems you cannot copy-paste across different files or versions of the same files. Quite devastating in my opinion, also because this doesn’t happen in the “normal” Figma. Hopefully this can be fixed soon! Cheers Giovanni

Editing compound vector paths would be so much easier if I could click and drag inside of the containing path to select the interior path(s). It could be set to work this way in outline view or in both outline and preview. Currently, when I want to click and drag with the selection tool to grab the inner path, the outer vector displays a angled line pattern. To grab the inner path, I have to click and drag from outside the outer path, then deselect the outer path, or I have to individually click on each of the inner path’s node, which presents another problem. About 50% of the time when I do this and copy/paste it to separate it from the outer path, it pastes it with missing line segments.

While prototyping, I would like to use a value from the element i interacted with in the screen I am going to (ideally without having to pass through variables). I imagine this as a link option, in which you would be able to tell “Use this text in this text box”.

The way masks or pathfinder logic is done in Figma is completely confusing (reverted). The workaround today is to use a community plugin… Would it be possible to have it closer to sketchapp, Illustrator.

is there a shortcut for Clip content? It would be handy to have one for quickly entering and exiting layers that are hidden by Clip content.

Vote for Figma on the iPad—imagine these scenarios: Designers often rely on iPads while on the go, sketching ideas or capturing inspiration. When we need to quickly create or edit a wireframe, the iPad is usually the only tool available. During presentations, being able to modify wireframes directly on the iPad would be much more convenient than using bulky laptops. Unfortunately, the browser version of Figma on iPads doesn’t support this. Now, don’t you think a fully functional Figma on iPads would be a game-changer?

Description When slides are exported to PDF, prototype widgets should be embedded in-place, either as an image or as a document containing the prototype frame. Steps to reproduce Create an empty slide. Add an interactive prototype widget. Click “File” > “Export all slides to PDF…”. Open the downloaded PDF document. Expected behaviour The slide on the PDF document should contain any visual element that represents the prototype. Current behaviour The slide on the PDF document is empty.

Sometimes you have a lot of effects on a simple object that can be a mess. An example is when you are working with neumorphism/skeuomorphism that often needs a lot of different shadow properties. When you have for example 6-8 different drop shadows it can be hard to locate each of them quickly, and a good internal naming system would save a lot of headache. We have a good way to save an effect collection as a style today, but I think an internal naming feature for each effect would improve the way to fine tune and work with an effect style. An example when it would be nice to have: A light themed effect style that needs be converted to a dark theme. Benjamin

Sections are amazing and I use them a lot after they were released. However, when working on layers inside a large section, I will be zoomed in so that a large section is going to fill my entire view-screen in Figma app. Clicking on an empty space is a common thing to do in Figma as it is a typical way to deselect a layer. But clicking on an empty space inside a section is not the same as clicking empty space in the void. It means selecting the section I’m inside. This makes it very easy to accidentally move a section when that is not wanted. I think it should be harder to select and thereby accidentally move a section. My suggestion is that a section can only be selected by clicking it’s frame-title or optionally it’s frame-border. In my opinion Sections do not need to be selected and moved all the time and are edited quite rarely compared to other types of layers. This will make Sections easier to work with and accidental movement of sections should be reduced. P.S. There is also Ph

Right now layers that are locked can still be selected. It would be useful if there was a feature to decide wether you need the locked items to be selectable or not. Sometimes this is just a background and shouldn’t be touched at all, or if you create a workshop for other users and you don’t want them to accidentally select something they cannot edit or shouldn’t touch

Please don’t hide editing tools and features: Edit Object, Use as Mask, and more Figma’s mission is to make design accessible to everyone. And then decided to make some features less accessible. (I know they’re not the same accessible meaning) At first, i was only a little annoyed but now that I’m editing objects, it becomes annoying. Why would you hide it and only show it primarily when you’re editing outside of a frame? (no shortcut key. The most you can do is double click it and if it’s really tiny i say, goodluck) When editing vectors or objects, edit object should be a primary action. In fact, if you’re using grid 1 fraction in this section you can squeeze all of them but instead you opt to hide some and show only 2. (What a tease) Look. The buttons you’ve designed were small enough so why still save space? I like how you made it cleaner, but not how you made it less accessible.

Discovered on a 3rd party plugin, but this is a Figma limitation. My team uses the Writer plugin to test content for compliance with our style guide. The plugin scans hidden layers and cannot exclude them due to limitations on the Figma side. Idea: Enable 3rd party plugins to include/exclude hidden layers.

Edit in Photoshop feature for images. I think it’s better to have a feature to edit photos in photoshop. This is already have in adobe XD. It’s very useful.

Hi! We need a fast function to create an instance with a shortcuts when a component is selected (e.g. Ctrl + Alt + I) , especially to create the first instance when a component is just created. It is very slow to do this via assets or component search. We really need this feature! What do you think?