Share Your Thoughts

Right now, Figma Make Design or Generate UI are great at producing static frames or visual mockups, but they stop short of creating true, reusable master components with variants, properties, and auto layout built in.What would be game-changing is if we could describe a component in natural language — like:“Create a Tree Selector component with four nesting levels, checkboxes with all states (checked, unchecked, mixed, disabled, default), a search bar, and expandable/collapsible interactions. Include Auto Layout, variants, and locked states.”…and Figma’s AI would generate a fully structured component set, not just the visuals.

I am trying to export an entire figma make prototype to figma designs. It seems crazy to have to do this screen by screen when there is so much embedded functionality (modals, tabs etc). Is there plan to do this in the future? Or am I missing something 😅 Thank you!

variables可以导入Excel文件，这样可以支持多语言切换，并且具体的String value 里面可以允许你折行

Hi Figma team, I’m using Figma Make, and I managed to create a beautiful delivery app, even though I’m just an ordinary food delivery rider with no coding experience. While building the app, I tested other connected apps, like the rider and admin versions, multiple times. However, I had to switch to another browser to view them through /?app=rider and /?app=admin. It would be very convenient if you could provide a shortcut for accessing these linked apps, like rider and admin. Thank you for creating such a helpful and wonderful platform! 

Hey @figma you know what would be dope? Having the image field as a component property allowing us to just replace the image without having to go into the layers…even better if it would save the fit or fill setting

I would like to share an idea: I thought it would be great if there was a good text editor here where you could effectively make up text, also create an aesthetic design when making up text, and generally create full-fledged documents. In general, it is an analog of MS Word, but with plugins and the ability to decorate the document with a cool design.Question: if it's not a secret, do you have any aspirations in the future to create a platform that would be an analog of MS Word here at Figma? I do not know what it should look like in all the details, however, I have written 3 main ideas: text layout, creating a design for documents, and creating the documents themselves as a whole.

Is there a way to keep a string variable aligned with a color variable HEX code, either through aliasing or by another method? For example: Color Variable |Key | Value| |myColorVar | #FFFFFF| String Variable |Key | Value| |myStringVar | myColorVar variable| myStringVar = “#FFFFFF” Use case: It would be nice for documentation to be able to automatically keep written HEX colour codes aligned with changes to the colour variables they are documenting. Thanks for the help!!

Am I missing something? ive already have a few prototype to be exactly how I wanted and flows. Is there a way to get Figma Make to build the already made in Figma Prototype for me so I can iterirate with Figma Make from here?Otherwise if my design journey starts with Figma Make first, its going to do something I don’t want and will have to spend too much time to debug (I mean its good for ideation or quick concept validation but I want to take approved prototype workflow further and iterate from there)

Toolbar should be able to change its position at the very least. Hotkey users don’t ever need it. Eyes naturally look more to the bottom of the page, and now this useful space is taken by some garbage icons 🙃 The overall redesign is also questionable. I would also support all the complaints about font size, unnecessary gaps between control panels and the edge of a page. May be it looks more “comfortable” for new users, but keep in mind that you have a lot of professionals who use Figma for a long time already, and they want a reliable tool that doesn’t mutate under their hands so they can keep working fast.

It would be very useful to have the ability to offset a stroke. For instance, in the case of the focus state for buttons and other components. Currently, there is a workaround, but it is not very convenient as it requires us to manage shadow and transparent stroke. This is especially inconvenient for a large library of components and complicates developer handoff.

There is a problem about the gaps as i resize elements. I would expect that Gaps respected the space inbetween repeated elements when resizing an element inside the group.how the tool actually works:|→ |→ (i try to represent the vertical bar as the start point and the arrow as the gap. There is an element that be repeated from the vertical bar. The point is when i resize the element past the 2nd vertical bar and the elements get overlapped)What i expected◻→◻→ (i expect the gaps to distance between the elements itself, not the vertical bar)

I have searched and can’t find an answer. I am a bit surprised this isn’t already a feature. I would like to hide the selected object’s BLUE OUTLINE with a key command or in the View menu. Please and thank you.

It’s the year 2023, and Figma still doesn’t have native table support. I just spent 30 minutes re-jigging all the “cells” in a four-row, six-column fake table because I had to delete one column, add another, add icons, and then manually re-fit/resize all the cells to get things to align properly. I can either fake a table row with a horizontal autolayout, or fake a table column with a vertical autolayout, but it’s still not a table. I want the ability to create a special frame called a Table, that: has an arbitrary number of columns and rows auto-resizes columns evenly based on content width has one or more Header / footer rows can scroll with overflow content (optional) has optional properties for hover / click states (cell, column or row) has optional properties for alternate-line shading can toggle columns or rows to hide as needed can merge or split cells as needed

Hello, currently using the Export widget is very cumbersome. You have to click on a project layer, expand the Export widget, select a file size (1x, 2x, …), select a file format, expand the preview and save. This has to be repeated with EVERY attempt to save! When will you change this so that the widget expansion, selected format, file size and preview display is remembered!

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Sites. Our team will be actively reading and sharing relevant takeaways with the product team. What we’d love to hear from you:What aspects are you most excited about — and why?

Hey Figma team 👋We’re exploring ways to use Dev Mode annotations more heavily in our workflow so that we can move away from sticky notes and keep all developer-related notes/context directly in Figma.However, we’ve hit a challenge — users with “View only” permissions can’t see annotations. This becomes a blocker for our team because our PMs (who only need viewing access) are unable to read these annotations. It’s important that they can, since they often need to reference these details when writing specs and collaborating with engineers.We’re on an Enterprise plan, and while we understand that edit access is required for creating or modifying annotations, it would be really valuable if view-only users could at least read existing annotations.  Is there any existing workaround to allow this visibility? Or is this something that could be cons

I want to be able to set a Layout Guide Style: Color property to a variable so that I can switch the color using Variable Modes.

Hello there, I am currently having issues viewing the guides on my design when the brand colour is pretty much the same as the guides. Take a look at the screenshot. A suggestion for the guides colour:

I know this has been requested a handful of times but want to riase again. I would love to see the ability to add sub folders within project files. I work for a large organisation in which we have multiple teams and products. I work within the website team which has a whole bunch of delivery squads within in. We use the current project folders for each of our squads. The enables us to keep all the squads under one website team within the organisation structure. Having sub folders would be super beneficial.

I’ve been looking into how I can leverage the new MCP server functionality in my design-to-dev handover process, but have been struggling with a few issues.As a means of speeding up my web design process, I have created singular components (no variants) that use variables for spacing, typography etc. These variables relate to modes like Wide Desktop, Desktop, Tablet, Mobile. My idea is that I’d like the MCP to read the singular component and be able to extract all the variables information across all modes and map those values to Tailwind classes (such as pt-4 md:pt-6 lg:pt-8 etc..) With a fair bit of back-and-forth, I’ve been able to recreate a passable version of my designs, but only for a single instance - this using variables from the default/first variable mode. So it’s not ideal to select one frame/screensize at a time and prompt the agent to recreate it - the code output can get messy pretty quickly.Do we know if th

I hope Figma notice this but i been wanting to suggest Figma to create another product that will call Figma Print. Mostly gonna focus or will add features for Print like Crop Marks, Bleed, CMYK. etc

Currently, adding interactive navigation (such as clickable contents pages) in Figma prototypes disables the default keyboard controls (arrow keys for slide navigation).This forces users to manually add keyboard triggers frame-by-frame to restore key navigation, which is time-consuming and cumbersome, especially for large presentations.It would greatly improve the user experience if Figma allowed both interactive navigation and default keyboard controls to function simultaneously by default. This would let creators build richer, more flexible presentations without sacrificing the convenience of keyboard navigation.Thank you for considering this enhancement!

Currently, annotation categories are defined per file.This makes it hard to keep consistency across team projects.It would be very useful to have option for team-level or organization-level annotation categories, managed centrally, so all files share the same list.This would help maintain alignment between designers, developers, and QA.Please upvote 😊

I have just realised that the links in my slides document (anchor to certain slides/pages) are still present in the exported PDF but: Unfortunately they no longer link to the specific pages but to my Figma Slides file in editor mode. This means that viewers can read my notes even without an Figma-Accout. It would be very helpful if this bug (if it is one) is fixed or at least to get more options when exporting as a PDF file such as the option ‘interactive’ or ‘non-interactive’.

Managing local variables is pretty cumbersome and buried in menus. Bringing over the variable window found in Figma, would be big help in managing local variables.