Share Your Thoughts

When one of my design system assets is invalid, it’s barely visible at the moment of publishing that it’s invalid and it will usually take me a few minutes to notice what’s wrong since it doesn’t look any different from usual publishing at first glance. Having a warning that’s highlighted and look different from usual on the publishing modal would help a lot. Thank you!

Hi! Long time listener, first time caller – I have a small detail quality-of-life suggestion: Currently:Arrowheads currently adopt the angle of the point at which they connect to the line. This often leads to arrows being “ugly”, due to big variations in the optical spacing between arrow head ends, and the line with which they are connected.Proposal:Make the arrowheads “aware of what was before the final point of the line”, and adjust the angle of the arrowhead so that the optical alignment becomes a bit nicer. I don’t know exactly what math magic is needed for this, but I’m sure more smart people than me can work it out, if you agree with the issue.Thanks, take care! 🙌 Example of the current arrowhead implementation in the first row, and my proposal (with nicer optical alignment) in the second row. 

Hi, Is there any option to select specific characters in multiple text fields? For example I have to change every “a” character to be blue. I know I can use Find and Replace to find the characters, but I have to go one by one to change the color. If you have any idea how might i do it, please let me know 🙂 Thanks in advance

Would love post its to stick to the different elements in the page, kinda like Comments are tied to an element which has a comment assigned to it.

As per the last update, when closed captions are activated while starting a conversation, the popover that comes up showing the captions has a very small width value, making the text unreadable and it cannot be resized unfortunately.It would be great to also drag around the window so it can placed anywhere on the screen just as other Figma modals.  

When I’m in the Prototype dialog (see attached screenshot) and want to select a Frame to navigate to, the menu that pops up truncates the names of top-level frames. It would make my life simpler if this menu auto-sized its width so I could see the entire name of all top-level frames on the page as I use a naming system that is quite lengthy, but useful to me.

Other website builder are really bad and the UI designed in Figma cannot be implemented of those builder so . I think a Figma website builder with all the Figma features would be really nice

 Could you make these two icons slightly different?I know I can unpack the ASAR and edit the tray icons manually, but it would be great if they were distinct by default.Thanks!

When you create a new document, you cannot currently add it to a new folder or project directly from that file. You have to return to the home screen then create the new project, THEN add it. It would be much more intuitive to add the folder when organising the file from… The file itself.

When designing components, variants may exist that are optimised for different breakpoints, or parent frame dimensions (e.g. a search icon when space is limited, but a search icon+textfield when more spacious)Within an enterprise, it is difficult to communicate the rules around the variant styles to use, and then ensure they are being adhered to.Could max-min widths be set on components, so that when used in designs, the instance automatically show the correct variant.Ideally this would have some enterprise governance, so that in some cases, the designer can over-ride the variant used, and in other cases, can’t. 

The new responsive prototyping tool allows prototypes to show one single layout, within the min & max constraints set.However, it is usual to design other layouts for other breakpoints.I’d like layouts to be linked - so that the prototype fully adapts, and switched layouts as the screen gets wider/narrower (or shorter/taller if desired).My ideas are there’s two ways this could be made easyBy using a naming convention of screens. Eg. Layout 0px, Layout 720px, Layout 1400px By linking the screens in the prototyping settings E.g. Instead of setting ‘Click’, you could choose ‘Screen width’ and set the width when to switch to the new layout

Hi!I would like to add a tag to the components in the design system library.Normally, all the components we have in Figma are also developed. However, in some cases, we create components specifically to facilitate the design team's work, even though they are not part of the design system as developed components.Instead of separating these complementary components into a separate library, our idea is to maintain a single library so that designers can access all resources from one place.Here as an example of the idea.I hope it can help more teams.  

Hello, I’m generally pretty chill about product updates, and I understand that companies need to evolve and improve their features Figma included. But honestly, I think you're heading in the wrong direction when it comes to prioritisation.Obviously, us the users don’t get insight into your development plans until changes are released. But I urge you to reconsider your product roadmap in terms of real, tangible benefits for designers.We’re the ones paying you after all…The new UI3 update introduces several changes that just don’t align with fundamental design principles. Since the rise of tools like Photoshop in the 1990s, there has been an industry standard in layout alignments, UI iconography, and UX best practices. Disrupting these conventions for the sake of change feels counterproductive.I understand the ambition to create the best possible software, but some of these decisions feel like change for change’s sake. With UI3, it genuinely feels like I’m driving in reverse, dealing wit

ContextMy company heavily uses Figma variables and are looking to build out multiple collections each having a unique set of modes. One example would be around Buttons—two collections would be made, one for states and another for size. There would be many other collections that would need to be created to create a comprehensive design system. Caveat: This use case may be an edge case or unique to me.ProblemThe current variable window is very inflexible:Can’t view your list of collections outside of a dropdown feels clunky Can’t resize the left panel with the list of variables Can’t reorder modes (I may be missing something here on why that is built that way)SuggestionsWould be nice to treat the variables’ left panel like the main pages and layer panels Collections could be treated like pages and would be housed in a resizable section above the variables which would be treated like the layers The same way we interact with the pages and layers panels would be the same way we interact wit

Not sure if this has been been covered so apologises if it has! I did search but couldn’t find anything.We are manufacturing our own product/device and I use Figma for prototyping the screens that go onto it. To give a better visual presentation to stakeholders within the company I work for, it would be useful to be able to upload our device image (as a png with the screen removed) so when I show UX/UI flows with prototyping they get a better sense of what it looks like in situ on our product/device.  

Suggestion for the Ask the Community Forum:I've come across multiple threads where users faced similar issues, but by the time I found them, the discussions were already closed. This wastes valuable time when troubleshooting quick issues.I get that storing excessive information isn't ideal, and many problems do repeat. However, Figma is used by a diverse global audience with varying English proficiency, professional backgrounds, and software literacy. What seems like an "obvious" question might not be so obvious to everyone.Would it be possible to keep threads open for a set amount of time before closing or removing them? This could help more users find solutions efficiently.

I want to connect variables with my sizes (e.g. 2.9, 3.9,0.2) to the scaling feature. Is there any workaround right know or a plan to integrate this feature?  

Hi, I’m building tables in the form cells » rows » columns » tables. 1.) This really feels like it needs to be a built in feature within native figma? 2.) My issue right now is how properties nest and aggregate as I build the parent component. Ultimately, it would be great if somehow figma noticed when multiple child components with the same properties are aggregated in a frame so that you can keep properties simple and functional as you nest. For example, when I nest cells into rows, I’d have to select 9+ components to nest if I want to include the cells component set’s properties. Of course I do not do this because it would create a loooooooong scroll in the UI. This results in have to click through several layers to get to the cell level when I’m trying to make relative simple changes at the column and table level. So, when I have the same cell in rows, I really need the properties to be aggregated so that way I can nest at the top parent level and make simple changes easily por fav

It would be convenient to only associate the plugin to some issue types so that the button “Add design” and the “Design” section itself would not show up on all issues. 

It’s been a while now but often when collaborating on the same schema, the width of my arrows are not the same as that of someone else even though I started it from a copy/paste of an existing object that had an arrow connected to it. The only way I can fix that is by copy pasting the arrow that has the width I want and using it afterwards.

The design panel moving as you are working with different elements can be very frustrating at times. I find myself looking for width and height which jumps around depending on what is selected. Can we please be able to lock certain stats in place?

It would be great if Figma can let users control the shape and placement of prototype connectors and also make them visible to anyone viewing the file, so that anyone viewing the art board can get a sense of the pathway to get from one screen to the other. Use cases Handing work off to a developer, they can see what the interactions points are without having to explore the prototype. A random stakeholder browsing around your art board wanting context on what the journey is. You can connect the prototype without having to go back and draw manual lines to show the journey when viewing as an art board. UX improvement suggestions Pain points:Currently the prototype accent color is a light blue, which is hard to see over top of light backgrounds. Cannot control the shape of the flow line, so they sometimes may overlap other frames or artifacts, making it cluttered and hard to follow. Collaborators can only see this if they are editors and have prototyping mode turned on. Suggestions:Instead

the Windows app is really crap, it is nothing more than a webview around the website, it is not a real, full feature, efficiente native app ☹️

Is there a way for me to set color to a property without creating additional variables? Like, I don’t have enough modes to do this well and also modes is a little clunky for prototyping. Trying anything to cut layers.

Hello Figma, wonder if we could create something like a tiny “link button” to set the flow name as the frame name instead of writing it twice and to be more descriptive in case a user forgot to set a title to the flow. and maybe the frame takes the name from the flow name in case there is no other frame has the same name of the frame