Share Your Thoughts

I’ve inherited a component library where many master components do not contain dummy data (Lorem ipsum and whatnot). Thus, many instances of these master components exist unchanged throughout many of our design files. I want to change these master components to contain dummy data to force future designers to override the text fields. I’ve been trying to find a plugin or a workaround for this issue, but I’ve either hit dead ends on the forums, or others are not understanding what I mean. Hopefully, I’ve rewritten this enough times to be clear, but let me know if I’ve not been.

It’s currently only possible to use HEX value colours in the Overlay background dialog (open overlay). It would be easier to have a theme named colour instead, then you can change the named colour and all the overlay background colours would also change. Now it’s a tedious process to change them manually and there is no easy way to locate them all.

One should be able to reset all the properties of an instance without resetting the text within the component. Or at least text that is set to a text property. More broadly, any property should be able to be set as a “protected” property that is understood to be configurable on an individual basis without being affected by a standard reset.

The search in file list view is just about useless. It appears to find anything with any of the searched words anywhere, including unrelated projects. What you need to find must contain a rarely used word for search to produce useful results. Showing only results that contain all of the searched words in the same order would make more sense. Or there could be an “advanced” search. There should be an option to limit searching to current project.

As an organization admin with 5 teams, it would be great to be able to see which team(s) a member belonged too when viewing the Members tab under Admin Settings

I regularly create components that allow for easy manipulation of prototypes at scale. I can’t, however, use the “Scroll” to prototyping feature on interior elements of a component. I need to break the component which then removes the benefits of having it as a component in the first place. Could we get it so scrolling to an interior element of a component is an option?

I’m working as a freelance designer and have a paid pro account. So I have a space with a bunch of files I work on. My buddy has the same situation. Occasionally, we work on a project together so both need edit access for the same file. It seems like there’s no proper way to do that, even though it absolutely should be easy to do. We can’t be just sharing a team account since we’re working on confidential projects the other should not have access to. Now if one of us hosts the file and the other should have edit rights, the host will have to pay double the editor cost (2x 15$) while the other continues to pay their license. This sucks! I have now more than once been surprised by a 60$ bill for sharing a file with my friend and inviting two PMs from another project to another file only for them to edit a typo or something, but never really do design work. Again, this sucks!

Hi everyone, I’m proposing an idea of adding a new type of components to Figma, which would have manually/auto restricted scope to one or several pages inside one file. It is often a situation when you have design system globally accessible, but for example a component/variant of an “item card” is needed only for specific screen and you don’t want it to be globally accessible, clogging the assets of the file. But it is still replicated several times and has several states, so component/variant behavior is expected. Important note here, is that the proposed local component should also load into the memory only if the current page is opened - that would drastically reduce memory consumption since globally loaded components which are not used consume unnecessary memory.

While working on a project i realised how TV and Game prototypes could benefit from a more realistic interaction. I was thinking how it would be interesting to implement a virtual control, either directly on screen or via the Figma mobile app to simulate the behaviour, maybe with just the direction arrows + ok + back buttons! The hover just isn’t reliable enough to showcase to the dev team how it is supposed to work.

As a developer I am used to working with multiple screens, copying content and/or viewing the same long file on two different screens to better understand the code. I miss the functionality of being able to drag elements being in the same project but in different screens and I think it would be a very practical feature when designing to be able to add elements more quickly, dragging them from one page to another as if they were files on the desktop.

When designing for web apps, breakpoints, and screen sizes are a bit different from viewports on mobile. Users have the capability to decrease or increase the viewport size creating viewports very far apart from standards. If you were able to set a min & max width for regular frames, you could, for example, create breakpoint templates that could be expanded or shrunk in the range of that specific breakpoint. Helping designers validate designs for viewports range and not a static dimension. You could also include a grid for each breakpoint and change it with variables and the child frame could scale according to the range of each breakpoint.

Hi! In my team we use emojis for project names a lot, and we love that, but we miss being able to order the projects alphabetically when they start with an emoji 😔 Perhaps they could be ignored when sorting?

Figma currently shares email updates with the subject header stating: " Your week on Figma Community" which is great when it comes to viewing the progress your profile has made in the past week. Also comes a total stats section where the total statistical figures regarding your posts can be seen including the number of views, copies made, saves and comments on various posts you’ve made on your Figma community profile. Although in addition Figma can really add a mini dashboard on top of the community profile page on the Figma Website, right below the top cover or maybe replacing the top cover. This could depict some stats like total views, copies made, saves from all the files from the very start of the profile till date. Along with this the progressive numbers can be shown in percentages such as the up or down percentage for views, copies made, saves and comments this week than the last week or something around this concept. Further to view such details with respect to individual post

I’ve compiled a wishlist of desired updates for Figma in 2024. I’d love to hear your thoughts and additions. What features or improvements are on your wishlist? Layout Features: Enable aspect ratio customization for any object Implement fixed aspect ratio functionality Introduce width and height settings as percentage values Introduce an option to limit width filling of wrapping items in auto-layout mode Incorporate full 360° rotation capability Variable Management: Introduce opacity control for linked variables Enable resizing of variable columns in the variable collections window Implement drag-and-drop functionality for rearranging variable modes Provide the capability to assign variables as page backgrounds Extend variable functionality to all typography properties Allow stacking of variables, such as multiple variables for stroke attributes Component Property Enhancements: Integrate an image picker for components (e.g., cards) to set custom background images Add a color picke

Hi there! I want to share an idea. I think it will be excellent to add a new permission for only edit texts. For example, our content managers want to edit some texts and designers don’t have time to fix all the content manager’s wishes.

PiP; with FigJam as like the “shift-enter” prototype screen in Figma where I can see my FigJam notes in my Figma design file or above it, exit it, and still work in my Figma file so I don’t muddy up the file copying and pasting from FigJam to Figma.

So, the design pannel is absolutely terrible. I need to go into the console to manually change the width of the design pannel. I need to do this everytime I start the app or open a new project/tab. Please just make it scalable with the Figma UI.

In a complex structure with multiple instances overlapping, it is difficult to locate a property object that is modified I repeat multiple clicks and trace back the layer panel to find the properties I want

Please hide phone navigation bar when we preview the prototype on Figma Mirror, mostly i always accidentally pressed phone navigation button when i want to click a menu from navbar in UI 😦 btw, previous version wasn’t like this 😉

Once you open local varables by default some accordion elements are always and you need manually close each of them. It may be tedious if you have a lot of tokens to do so

Figma is the fastest way to share a slide deck with your team, in comparison to porting over content to Google Slides. However, the inability to scan the deck prevents people from being able to quickly navigate to the right slide. Allowing viewers to see thumbnails of the entire deck would enable teams to effectively cut out Google Slides.

it would be great to be able to quickly draw squares and circles like you can in Invision Freehand by dragging the pencil in a diagonal or circular fashion. This allows for quick wireframing while speaking to stakeholders and collaborators.

Current behaviour on Mac app using the keyboard shortcut is to go from: on zoom in: 100% to 200% to 400% to 800% on zoom out: 100% to 50% to 25% to 13% to 6% It’s clearly a hard coded zoom value to multiply by 2 or divide by 2. The factor of 2 works great if you need to quickly zoom in or out, but falls short in providing users with more control in many situations. It becomes a real pain to use when a more gradual zoom in/out is needed, especially in the absense of a trackpad or a mouse wheel (this affects mac and pc) . Some use cases: during remote screen share (google meet, zoom, etc) what looks fine at 100% on a 32in monitor to the designer is too small on the screen share to the rest of the stakeholders and it requires a 130% zoom for proper viewing. There’s a clear difference in overall size when comparing ui in the browser and Figma (widths, text, and all measurements are the same on both: browser and Figma) and zooming out in Figma to 87% is more accurate to what the ui will

When tagging team members, the team member doesn’t seem to get the notification email until about an hour after the initial tag. This needs to be fixed as it is useless to tag someone and wait that long. A lot of teams have to move fast.

I’m happy with the mind map widget (finally) I would like it if I can make it into a Directed Graph (ie) a leaf can have 2 parents