Suggest a Feature

Basic use caseI have a menu component which is composed of:header frame body frame footer frameIn the body frame there is a menu-list-item component.When I use a menu component instance I would like to be able, in the properties panel, to increase the number of menu-list-item to n instances.Feature suggestion: would be a feature that would allow me to flag the menu-list-item as a component instance that can be replicated n times inside my instance, either vertically or horizontally.It would avoid the cumbersome and not so clean workaround of working with slots/placeholders and keep in files plenty of “unique content component”.Other use caseIn my input, when in “inserted” state I can either choose to have chips or text.In the case of chips I would like to flag the chips as elements that can be replicated n times horizontally. In my instance I would be then able to select the “insterted” state of my input with chips instead of text and would be able to put multiple chips as result.

I love sections because they easily help organize content, but they become less powerful as compared to a traditional group without the power of auto-layouts. Adding new content to a section always involves slowly moving everything else around (usually down) and having to always resize it manually. Having the option of toggling on/off something like auto-layouts for sections would really boost productivity!

I had a shadow on one of the components… I could see it within the text but the text didn’t have neither any stroke nor shadow (inside, outside, nothing).Now, I checked the whole component and BOOM it turned out the component had shadow…IMO this is a big NO NO (yet another one).First of all, e.g. developers will not see that a text has shadow.Another thing, I was wondering why my text looks so strange and I really had wander around checking objects, going up, up, until the component…OMG people why are you doing things like that… ALWAYS some idiocy, always something non standard...

It is very hard for UX designers to show flows in figma, mainly because the arrows from figjam don’t allow to connect to different elements which is counter intuitive for UX designers. Also it is hard to work with figjam and figma as separate files for UX and Design specs we need the files together and it’s often easier for collaboration. Figjam is great for flow charts but I would love to have figma and figjam working as one.

I have a feeling neither of the following are possible due to the current flexibility of using template slides -- ie you can choose to use just a few slides from a template instead of using them all. I’ve just published a large slides template for company wide use but realized it does not retain the nested sections or animations between slides. The deck has 91 slides so without the nested sections that appear under each title slide it’s difficult to manage.I also have some slides that use variants of the the same component that I have set to smart animate between then to show the proper animation, but this is not retained in the template either. Is it possible to keep either of these baked into the template? Thanks

TLDR - this doesn’t workhttps://docs.tokens.studio/themes/themes-pro My Next/React web application platform has a pretty sophisticated token pipelineTokens are generated in Figma and recorded in Tokens Studio, where Figma is a participating member of the advisory board (DTGC format) Tokens are transformed by Style Dictionary (thanks Amazon!) into both Tailwind and JSON JSON powers a slot styling API for cachable elements in HeroUI Tailwind layer directives create a clean index of references for the slots Typescript uses branded types to tag data with processed/validated signatures throughout the system. I match the DTGC spec to increase type access between all DTGC-based systems and discriminated unions to handle the uniform interface between the branded DTGC types and systems like HeroUI and Tailwind. Yes, I’m a UX designer. I just also sling a little codeTokens Studio properly inherits in the right orderGlobal types carry core color, size, and other technical declarations Scales ar

This would be handy if I want to mass-select and find hidden layers to show altogether. Unless this is a technical limitation, I am shocked that this is not integrated as an option from the get-go.

I’m constantly clicking on this by accident. Is there a way to disable this shortcut so it doesn’t appear on every single frame?

Hi, I’m really tired that when me and my colleague are working on a file, when I choose a device for preview it applies for her too. Like if I’m working on the mobile BP, e she is working on the desktop BP, when I set the preview device for the prototipe, it applies for her too, its a bit annoying that when can’t have 2 different devices as a preview for our prototypes.

Title Typo: "Ungroup" a component and keep properties of nested frameI have a component with a nested frame (in this case it was a subcomponent - because this dated library used master components) I want to rid it of it’s nesting but the nested frame holds the background color, autolayout, stroke, effects etc. Because I can’t ungroup the VARIANT at the top level, I have to re-add those properties after I ungroup the nested frame.  

Can we get a true aspect ratio lock when the ‘Constrain Proportions’ is on? A true aspect ratio lock means two things: When dragging on a node with ‘constrain proportions’, its width and height always stay in their original ratio no matter which direction you drag it. When resizing on the parent of a node with ‘constrain proportions’ that happens to be constrained, the node takes on the smallest of its supposed width and height, and calculates its ratio accordingly. This would be so very helpful to polygon shapes that want to stay in that shape. Consider a spider chart. When you resize its parent, you don’t want the ‘spider net’ to squish squash; neither will you want a doughnut to turn into an oval. *Resizing of the node’s parent layer is inevitable if you need responsive designs.

When prototyping vertical scrolling, I find it tedious to constantly toggle the container's clipping mask on and off to edit content. Are there any workarounds to avoid this? I don’t want to create a component because the content changes with the progress of prototype.  Figma should automatically turn on clipping mask in Present mode and turn it off in edit mode. 

hey, sometimes i just want to check how people with a viewer role would see the file and dont want to bother logging in with a “viewer” account. then it would be just nice to be able to switch the UI to what they would see. e.g. sometimes i wonder what they can and cant copy or what they see in the side panel AND NO i dont want to go to the Figma documentation and look for that screenshot 😃 just let me switch view > check > done > happy 😃

Currently, when using a sticky note in a FigJam document, the aspect ratio is locked so that I cannot adjust it as I wish. This is annoying. Please give us the flexibility to adjust.

Seria legal uma atualização ou a criação de um plugin com a possibilidade de adicionar sangria e marca de corte.

please, made flutter autogenerate code option this framework is more modern, the most highly rated on github, and supports the largest number of operating systems and screen sizes, it is completely universal for all needs for which Figma can serve

An easy way to access the pages/layer panel when the UI is minimised, likeHovering on this shows the pages/layer panel floating and hides when I mouse out of the panel.  Right now I have to toggle between minimised UI and expanded UI just to change pages or look at my layers. I really like using the minimised UI for it’s lesser distractions.

My team made the switch from XD and one thing we really miss is being able to see ALL your comments in the comments section and being able to click on a comment to navigate to the screen the comment was made on. Please add this feature

Need I say more?

Add a laser pointer to the board so it would be easier for the presenter to direct the attention of audiences to specific parts without the need to actually underline, write, circle etc on the board.

Would be great to be able to create Grid layout, in line with what is available with CSS.

🙏🙏🙏🙏🙏🙏🙏🙏 PLEASE  🙏🙏🙏🙏🙏🙏🙏Add vecotr animaions within figma prototypes.I would love to run eithe lottie, rive or alternatives in my prototype please!Your current plugins only support gif (come on we are not in the 90s anymore) and you state you have lottie support but this is not accurate.I’m sure this is a highly requested item.Please can this be added

I have a very distinct first and last name. My Figma profile uses my full name, which is important for our organization-- coworkers and partners in Figma need to be able to easily tag me in comments and see who worked on files. However, I would like a way to have a different display name and handle for the Figma Community. I don’t really want my questions about plugins, etc. to be publicly searchable if someone were to Google my name. I prefer to have a privacy option and keep my professional work and personal online presence as separate as possible.

I don’t understand why FigJam won’t let us use components inside files. This wasn’t a problem before the latest updates and it makes absolutely no sense. Part of what makes Slides great is that it’s part of Figma. Let me use my colors, fonts, and components please!

I’ve been using variants a lot and for huge numbers of components, it’s amazingly time-consuming. Plugins help but having a keyboard shortcut for “Combine as variants” and “Create multiple components” would help tremendously. Idally, everything would be possible to bind to a custom shortcut. I am proposing the following shortcuts: Create component ⌥⌘K Create multiple components ⌥⇧⌘K Create component set ⌃⌥⌘K Combine as variants ⌥⌘V