Suggest a Feature

I would love to be able to set variables for font sizes. That way i could define the reduction amount for the mobile versions of our designs. Set a vaiable of 40px and a mode “mobile” with the value 32. This would make this kind of conversions a breeze: If a text looks to big, opt for its mobile version. done.

Need to resize color palette (and other palettes). Tired to scroll it every day. Add this feature please.

I leave comments in my projects to discuss certain topics and also sometimes use the comment function for documenting specs. It would be good if comments could be visually distinguishable (discussion vs. specs comments), so that devs can see at first sight which ones are important for them.

Hey folks! Am I the only one who would love to receive a notification or a ping (outside the Figma App but as a Mac notification) when a specific person of the team enters the file?

I use a custom emoji font made as a COLRv0 font. This technology has been supported for years in all browsers and in Sketch app but is not supported in Figma.

I think y’all should color code them like illustrator or aftereffects because it gets confusing and overwhelming.

I find the latest update to the gradient functionality not very good. It’s displaying a list of “Stops”, but it’s really not as important as the “color picker” of each stop, it takes more work for the user to change the color. Please go back to the old version.

Actually an Admin that doesn’t edit drafts looks like it’s never entering Figma, even when doing administrative tasks. Please consider Admin activity in the Last active status. Actually we do some editing in the draft to overcome this.

As an avid user of Figma, I’ve found the platform to be incredibly powerful for designing and prototyping user interfaces. However, I’ve noticed that there’s room for improvement when it comes to managing scrolling interactions within prototypes. Specifically, I believe that the addition of scrolling controls and scroll smoothing options would greatly enhance the presentation of prototypes, providing designers with more control over the user experience they are trying to simulate. Scrolling Controls: The ability to add scrolling controls to frames or elements within prototypes would allow designers to create more interactive and dynamic experiences. This feature would enable users to simulate scrolling behavior more accurately, particularly in cases where precise control over the scroll position is necessary. Scroll Smoothing Options: Introducing scroll smoothing options would further improve the realism of prototypes by adding a more polished and natural feel to scrolling interactions

Currently text styles allow you to do some modifiaction without breaking the text style. Change text alignment for example. It would be helpful, especially with the introduction of typograhic variables, to be able to have more options available without breaking the text style. Specifically casing; uppercase, lowercase, etc. Also text decorations like underline would be helpul as well. My use case is that I have a multibrand design system with each brand using a different font family. For buttons, some brands use title case in the button text and other brands use uppercase. The only way I can mange this change efficiently is through swap library. I would like to use variables as thats what we are using to change color, size and spacing between brands. But without being able to change or target the capitalization option, we are stuck with using a typography only library and using swap library. Another, and maybe better option, would be to allow a string variable to target a user specifie

Hi You can easily access variables via the Figma Plugin API. Meaning you can create ‘pickers’ to and populate them with team library variables for things like radius, spacing and colours. With the advent of typography variables, you use a composite ‘style’ to group a number of variables together (i.e. to make a H1 or paragraph style). In order to create a picker for typography styles, based on my styles contained in my team library, currently I have to ask the user to select each variable individually (for font size, line height, font-family, font-weight, etc). Whereas what I’d like to be able to do is for them to simply select a single typography style. Unless there is going to be a move towards composite variables (yes please), can the team library methods be updated to include a getStylesInLibraryAsync method? Thanks

The lack of a Shape Builder Tool (like in Adobe Illustrator) is surprising. This is an essential tool that I use on every project in Illustrator. I have used the Boolean Groups, but they don’t fill the use of a Shape Builder Tool. A SBT allows me to trim the edges of overhanging shapes, which I commonly do when designing.

For example imagine that I have these 2 token variables: page.margin = 16 icon.padding = 10 and that I have a component that contains an icon with the padding. To ensure the icon aligns vertically I need my component to have a margin of 6, but only because the icon already contains 10 padding. Therefore, to make my design using tokens I need to specify the padding as: page.margin - icon.padding = 6. I do not want to use the value 6 directly as then when tokens are updated the design will not be. This is related to Using expression as a variable's value but not the same. To support tokens for measurements this is essential.

Introduce such a possibility, so it will be possible to do thanks to variables, for example, transparent black or transparent primaries. Currently, you need to make a detach alliance.

Hi folks. Is there a way to view a prototype on mobile that displays the sidebar and its flows? When viewing my Figma prototype link on mobile (iPhone, all browsers), the sidebar that shows all user flows does not display at all. I have four user flows that I want to display. I tried testing my prototype with all viewing options (fit to screen, fit width, full screen, full size). To confirm, this works fine on desktop. Mobile is just not complying. 2022-2023 threads on this seem to not give a clear answer. Your help is appreciated!

Hey guys, I see that the UX for selecting gradient colors has just changed. The cool thing is that now there are numeric STOPS, which I don’t think we had before, but the rest of the UX is a bit of a mess. There are too many steps to perform and the steps became less intuitive so they take a longer time. For example, if I click on the color box, I have to look for that color in the list below, then select the color picker to edit the color. So there’s one extra click and the action of finding the list item, which takes longer now. Imagine you have play around wkith some color and you have to quickly go from one to color to another to adjust, it’s a nightmare, I am literally going to use another app just for getting the gradient right. Also, seeing the color picker all the time with the whole color spectrum really helps the process of matching colors. What happened, how in the world did the best tool for UX release something like this? 🙂 Please revert it back to the way it used

While documenting default margins of html tags or text classes is rather easy, communicating and continuously onboarding other designers is very difficult, especially on scale. So in order to align the spacings between text elements it would be super useful to add another text prop which can define margins to the top and the bottom. Please upvote 😉

Right now, projects will appear empty (even showing “0 files” in the count at the bottom) if they only contain private files that the viewer does not have access to. I have admin access for my organization, and even I can’t see if a project does or does not contain private files. We’ve had issues where projected were deleted because they appeared empty, but in fact contained private files. It would be helpful if Figma could indicate if a project contains private files. Even a warning before deleting the project would be appreciated. Right now there is no indication.

It would be nice to be able to have a fixed background position inside scrolling sections. For myself, the end goal would be te be able to create CSS shaders by overlapping scrolling images (specular maps, alpha masks etc) over fixed gradients (examples). It would also be useful to create layered depth, and can be a first step towards easier parallax prototyping with scroll speed fine-tuning

Currently variant swap acts as a complete component swap. All its properties get overridden and are not controlled by the master component anymore. For example: I have a “tab” component with two states: “active” and “inactive”. Once I do a variant swap (set the first tab as “active”), the “tab text” property receives an override. At this step all still looks good, but… …if I want to change the text on the first tab from “Section 1” to “Section A” — I can’t. It’s not inherited anymore. This was already raised on this forum as a question, but not as a feature proposal. So I’m adding one. There is a workaround I pack all component states into a single auto-layout frame and make that a component. If I need an active tab, I switch off the visibility of the inactive part. Now all works as it should But it gets very clumsy / hard to maintain if I have hovers, or I have not 2 states but 5 (primary, secondary, error, etc.) or I use component property as a breakpoint switch. –

It would be great if you could add a feature that allows users to lock pages. Exactly or similar as it exists for locking layers. Here’s the use case/reasons why this would be super useful: During a design process we usually split tasks over separate pages for example: Page 1 - “Round 1 - Design Explore” Page 2 - “Round 2 - Refinement” Page 3 - “Round 3 - Delivery” At each stage we ask the client to comment on the work. At large organizations/with many approvers and projects that span longer timelines, it often happens that comments are left in what we consider an “OLD design” (=an outdated page). In the above example, we would have already addressed the comments from Page 1 and 2 as we are working on Page 3. So the only place where new comments should be placed are in the most current Page 3. Yet it happens often what people catch-up on progress shares via their Figma email notifications, where they click on an outdated Page link (i.e. Page 1 or 2) and they land in these pages where t

It would be great if the notifications panel had tabs to see what you have commented on other files to keep track. Its also super annoying there is not date filter. On default you can only scroll so much and cant see notifications past a certain date.

Hi So I’m experimenting with Variables and creating a hierarchy for primitives, semantics, and components. Only I get stuck between modes in semantic collections going to component collections. The goal is to include collection modes for two design systems for an easier transition of component variants. I am guessing the collection with the changes is the only one allowed to update with I use layer auto collections on Frames. Is there a plan to choose a mode within a nested collection?

I came across the problem of “Setting the position of next overlay after Swap overlay”. I searched the community that people have requested the feature for the same and there was no solution. I tried successfully. On Overlay 1, I used following interactions consecutively: Close Overlay and then Open Overlay 2. Now I could set the Overlay Position as needed, irrespective of Overlay 1 position. Do let me know if this works for you guys! @Dario1

Hi, Will it be possible to rotate the gradient by manually entering angles? For example, I would like a gradient starting from top to bottom, rotated by e.g. 45 degrees or exactly 27.