Suggest a Feature

The new variables feature is great! But I’m asking you to add an ability to assign String variables to Text props of component instances. My use case I have a generic component “header” in my company’s design system that can be used with any text. I insert the instance as a part of my specific design frame for iOS. A UX Writer edits the header text. Then, I create a frame for the same screen for Android, Desktop and Mobile Web. In total, I have 4 screens with the same header. Now if the UX writer decides to change the text inside the header instance, they have to copy paste it 4 times. I’d like to solve the sync problem and the need to maintain consistency manually. I wanna make a String variable “screen-1-header” for example, and bind it with the Text property of the “header” instance. BUT as far as I see, Figma doesn’t allow it at the moment, which is sad. I can assign a variable to a text layer that is not a part of a component, but I don’t like the idea of detaching instances from

I’m considering hiring offshore developers for an upcoming project, but I’m unsure about the best approach. There are so many agencies and platforms claiming to provide top talent, yet I keep hearing mixed feedback from people who’ve tried it before. Some say it’s a great way to save money and access specialized skills, while others mention challenges with communication, time zones, and maintaining quality. I’d like to hear from people who have real experience in this area — how did it work out for you, and what would you do differently if you had to hire offshore developers again?

Whenever we copy text from one place and paste it into another text frame, it carries over its own formatting (size, style, etc.). But I want the pasted text to automatically adopt the formatting of the destination text frame. Currently, the copied text’s properties override the destination formatting, which is not ideal.This isn’t a bug, but it feels like behaviour that needs improvement. In most practical scenarios, users copy text because they want to replace the content not the styling. If someone actually wants to preserve the copied text's formatting, they can apply it manually. But by default, it makes more sense for the pasted text to follow the formatting of the target text frame. Can this be fixed or improved?

What is meant by Figma Sites CMS not being available until late 2025 actually mean? I am having to explore other CMS solutions, as a result of the CMS not being available, only after having created a pretty extensive design system for an internal site, components, blocks, and templates. Any update would be extremely helpful.

Hey! I’d like to suggest one update that i believe will help non-designer folks to achieve more with Figma Buzz without additional training/internal guides inside the company.The recently added Figma Buzz support of component variants and swaps is great, but it’s often not super obvious which parts of templates are actually swappable without diving into the template structure & layers. So we often need to rely on internal documentation, or note frames outside of the template to add hints where folks can click to swap/change things.What would be great if in the “Edit content” panel along with text and image fields we’d have a list of changeable components (I.E Components that are not locked in the template master). In that way people who are using templates can discover changeable parts instantly in the same way as they discover and edit regular parts like text and images.

Analytics are critical for understanding adoption and impact in Design Systems. Right now, insights are tucked away in individual library modals, which makes it difficult to monitor patterns at scale.A single Analytics hub — with dashboards, trends, and cross-library metrics — would create a far more useful workflow for teams that need to track quality and usage over time.

After discussing the subject at length with the support, here’s a summary of what Figma allows and doesn’t allow in terms of library sharing (hint: it’s not that simple), and how it could be streamlined: Currently, as a component library creator, here are the options you have in order to share your library (I will not include the options for a Starter plan, they are legitimately limited) As a Pro user: Publish it and share it within your Team (to users you - or your admin - pays for) using the Team library feature. They can access the component anywhere inside the Team’s files, and get realtime updates. Links are preserved throughout even with multiple files. Share it on Community (to users outside your Team): they can duplicate the file to their respective spaces, without live updates. Links won’t be preserved if the library includes multiple files. Share it via link (view-only) to selected users: they can either duplicate it (although not as easy as a Community file), or use it as a

The text in a frame can be independent of other frames, or it can flow between connected frames. To flow text between connected frames, you must first connect the frames. Connected frames can be on the same frame, or on another frame in the document. threading text linking text frames linking text boxes

When we add a delete or close button on a list item or another element on the prototype, the button interaction should delete that item. This way, we don't need to create component structures and states. We can restore the deleted item with reset state. I tried to explain it with an image.explain imageThe red button was added to delete that row. Within the actions area, there will be a “delete item” feature, such as ‘undo’ and “close” operations. In the green marked area and on the prototype, that button will remove that item.

The window for NFL groups in the direction of host potential customers upon pre-draft outings shut closing 7 days, nevertheless there are continue to status trickling out. The hottest of individuals is Texas offensive deal with Kelvin Banking companies Jr. , a projected 1st-spherical choose who frequented the Fresh England Patriots at 1 place inside of the Wilson of KPRC 2 Houston was very first towards write-up the check institutions Jr. , 21, is coming off a 3-period occupation with the Longhorns that noticed him start out all 50 video games he looked within and get paid many affected individual honors. Inside of 2024 by yourself, he acquired the Outland Trophy as the state's easiest lineman, the Jacobs Stopping Trophy, and was called initial-staff All-American and initially-personnel at exactly higher than 6-foot-5 and 315 bodyweight, Financial institutions Jr Mitchell Wilcox Jersey. brings together superior establish with an explosive initial phase and natural and organic actions t

test

I’d like to know WHO created every annotation, just as with comments.Or at least make it optional. I often want to add “comments” for stakeholders that I want to persist, be visible always, and not be resolvable. So I go with annotations. But I want my name attached to them. At least sometimes.And I find myself asking people “who are these annotations from” quite annoyingly often.

The Problem In figma, it is currently not possible to persist certain compository styles without having to think of all the possible use cases before and putting them in there, or to provide a component just so that it can be used as a reference, a starting point. The reason for this is that once a layer is in a component, it cannot be replaced, removed, multiplied or reordered. This makes sense, but limits what a component can do. Examples Buttons that are capable of showing any icon. The Icon can only be replaced by a different icon of the same size or the same parent component (icon/*). Meaning, that all icons that are available need to be thought of before. This breaks the components capabilities, because it all of a sudden needs to be aware of the icons it can display. Text-Content Content that consists of a variable structure of headlines, paragraphs, lists, quotes, etc. Designing a Template for a view that will receive content from, for example, a CMS is impossible as a

I have multiple Figma accounts with multiple clients and multiple projects. I also have a handful of designers on my team. Because all of us manage changes requested by the client, we often miss some tagged comments because the structure of notifications in Figma is just a long list. I would love to be able to tag comments as “To do list” and then reference and jump to all those action items and mark as complete. The more I convince companies to adopt Figma, the more comments there are (by non designers). I’d also love to tag comments as “ideas” or by topic so i dont have to guess click on everything to see which comments i need to look at. Essentially I want to “View groups” of comments that are most relevant and just hide the ones that are needed on the page for others but are in my way when I’m doing my work.

Working with comments in Figma is still very inconvenient. There are several features that are greatly missed for easier management: Group management of comments. For example, to select a group of comments and move them on the page, to another page, delete them, or resolve them. For now, I have to go through and delete comments one by one! Lack of access policies. Case: I shared the prototype with a client, but I don’t want the client to see the internal comments from team members (comments from the editing mode are accessible in prototypes for some reason). «Done» all comments on a page/file. Basic filters: by user, specific day. Tags! Different team members comment on different topics: UX, art, dev, business, etc. There needs to be a way to filter comments not only by team members but also by themes. The simplest thing: hashtags! For example, we could specify something like #front-end in comments, and then click on the hashtag to see all comments related to that topic.

It would be really nice if I could pop out the variables into their own window. Currently I can only have it as a dialogue in Figma, which means it always overlaps over my design and especially on smaller screens this becomes quite the issue. I often need to see variables and my design at the same time, so moving it to a second monitor (or even on a laptop quickly switching with alt + tab between the two) would be very helpful.

Hi Figma team 👋 I’m a product/app designer and I work with large, complex files that contain many components and extensive documentation. The new behavior of Figma Annotations — where they briefly “float” or animate during scroll before becoming sticky — is extremely distracting in daily use. Because my design system files are dense and rely heavily on annotations, this micro-scroll animation triggers constantly. It feels like a bug or glitch every time I move through a frame, and it makes focused work much harder. Feature request:Please add a simple toggle to disable this animation and allow annotations to be instantly sticky (or fully static). Even a basic on/off setting would significantly improve usability for designers working with large files. Thanks for considering this improvement!

I was thinking of what if @figma adds CYMK Color, which can be used for printing purpose. Recently was designing a poster & wanted to print it but, after printing colors were changed. So i thought what if @figma can add CYMK Color in the software. Let me know what you guys think

As BNPL apps deal with sensitive financial information, security is the number one priority. Java Spring boot or ASP.NET core can be considered in terms of highly secure and scalable environment in terms of the backend. Such frameworks provide the security features like authentication, authorization procedures that are essential in the financial applications. Swift (iOS) and Kotlin (Android) are perfect to create secure high-performance native apps in the case of mobile development. Secondly, it is essential to consider embedding powerful encryption libraries and achieve compliance with PCI DSS when processing payments in the BNPL app development, as these should provide protection to the users and make your customers trust you.

FigJam的工作背景版本增加了切换为深色背景的功能，可以根据需求设置。白色太耀眼了，我一直习惯Figma的深色背景，用起来非常简单。

It would be helpful to have the ability to download a CSV file of members with all of the data available online. It would also be helpful to be able to view historical data for specific time periods in the event permissions have changed or members have been deleted.

Feature Request: Multi-Select in Point and Edit Current: Single element selection onlyProposed: Ctrl+Click for multi-select with task list Benefits:✅ Select multiple elements at once✅ Clear task list above chat: "Task 1", "Task 2", etc.✅ Reference specific tasks: "#Task1 change color to red"✅ Faster, more precise, less confusion Use Case: Complex forms/dashboards with many similar elements

I’m working on our team’s design system and we’re planning to use CSS Grid as the basis of our page structure in code. I’d like to replicate this behaviour in Figma to close the gap, and while the Grids frame setup in Autolayout is CSS Grid, it’s incredibly limited. You have a max of 12 columns (which is fine, that does everything you need) but the rows having to be predefined by the number, and worse, by having to be 1fr makes this setup useless. This means rows have a predetermined height based on the number you add that evenly divide the space within the frame. But content is king, and they don’t respond to the heights of what lives within them or collapse if something needs to be hidden. It’s frustrating that Grids was released without even this basic aspect, I don’t know what you can do with the current set up except for a super simple splash page, and the inspect makes it even more useless as it won’t be accurate. I’ve been told by (supposely) an employee at Figma via the subredd

I’d love to see some enhancements to the Projects screen and file browser. There’s a variety of old topics for this out there, but they appear dead – many of them years old. Better UI for ProjectsDisplay descriptions – Currently you can add project descriptions in the project settings, but they don’t display anywhere Display metadata – See belowAdditional metadata for projectsTags – Ability to add tags to projects, particularly around what products they are for Statuses – Similar to the ready for dev status in designs, allow labelling project statusFiles not in a projectWith miscellaneous concepts and FigJams, sometimes they don’t have a dedicated “project”. We don’t want them in drafts though, because we want to have shared access. This usually ends up with us creating a “miscellaneous” project to store these files. It would be great if files did not have to be in a project, similar to how on your computer files don’t have to be in a folder.Project/File archiveWhen projects are comple

Figjam’s Pages and their restricted horizontal scrolling has become an issue for my team. Typically, we work left-to-right. For instance: When we have a meeting with stakeholders, we create a board with the agenda and content. During the meeting we annotate that board, then to the right, we create another board to ideate the next topic. As more work items and meetings come up, we add boards to the right, so that we have a visual trail of the work we’ve done. Figjam’s limited Page canvas have made it very hard to work like this because we can’t keep adding content to the right because the canvas ends. Because of this, we wrap our work lane up (because we have more vertical space available), but that makes the Page more difficult to navigate because a user then has to zigzag through the trail of work. Questions: Do people ever use the vertical height of a Figjam Page to it’s fullest extent? Is there a way to limit the Figjam board based on a storage level instead of a arbitrary amount of