We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
🎉 Welcome to the Figma Forum! 🚀
Find solutions, get advice, help others.
Alright, guys FigPals were the best (and weirdest) thing to come out of April Fools’ this year. They follow your cursor, help you design, and love you unconditionally… maybe too much. 👀 But here’s the problem—they’re only available for April Fun Week! 😭 We can’t let this be just a one-time joke. FigPals deserve to be a permanent feature (with a toggle for those who don’t want constant companionship). That’s why I made a Change.org petition to show Figma how much we want to keep them! 👉 Sign here: https://www.change.org/p/make-figpals-a-permanent-figma-feature Let’s make sure our tiny, slightly obsessive design assistants don’t get deleted forever. #KeepFigPals 🩷🐾 mr bonky mr bonky
Please make Dev Mode Annotations visible by all roles, not just Full Dev Mode seats. This can become costly for users needing context but not all the other dev-mode features. Here’s the scenario: We have a dashboard, with cards showing a customer’s account status. This status can be mapped from multiple back-end statuses, to show just one front-end status. For example, any of the following could be mapped to a single status known to the customer as “Completed”: canceled, terminated, sold, complete, etc. This is something that the developer needs to reference, but then also the PM needs to reference in writing tickets (who doesn’t need full dev-mode access), the QE needs to reference for testing automations, and various other individuals on our team. Placing it in a comment makes it less clearly attached to the specific piece of the design, and requires us to keep documentation dispersed among different tools (Jira, Confluence, Figma etc). Simply making Dev mode annotations visible to v
Hi everyone, I’m developing a Figma plugin that extracts design properties from selected nodes, including text styles and color tokens. For text styles, I successfully retrieve the applied style using: const textStyle = figma.getStyleById(node.textStyleId); This works great for identifying and mapping text styles. However, I can’t find a way to get the color variable applied to a node. When inspecting node.fills, I only see the RGB color, but not the token assigned in Figma variables. Example: In Figma, the text color is set using a variable: color: var(--color-foreground-primary, #000); But when I check node.fills in the plugin API, I only get: { type: "SOLID", color: { r: 0, g: 0, b: 0 }} I tried checking node.boundVariables, but it doesn’t seem to return color-related variables. Questions: 1️⃣ Is there any way to get the applied color variable name (e.g., "color-foreground-primary") in a Figma plugin? 2️⃣ Can we extract this information from boundVariables, fills, or another API met
Material theme builder version 20, released in May 2024, is not operational. The plugin generates theme colours but does not update them in any project files other than the original kit project. This means that if you had any work using Material 3 kit, you are not able to update the theme since May 2024. It is not possible to do any theme-related M3 work with a custom theme since May 2024. Themes in any project that people had done in Material3 UI Kit cannot be updated anymore since May 2024. There is no other Material theme builder plugin. We are hostages of the situation. There are tens, if not hundreds, of reports on the M3 DK page and on the Theme Builder itself page where it has been ignored since early 2024. It appears that version 20 of the plugin was released untested, and the development team was immediately reassigned or disbanded. Nobody from the Material team reads bug reports; nobody responds. Figma announced the category of UI kits but did nothing else; nobody tests anyth
In the design tab, you have a panel of created property options shown at the very top, and in full size, and often when you need to change an instance, you need to scroll first one panel, then another, and they can have a lot of content, which makes navigation through the design tab very long and not intuitive, to simplify the task, create the ability to show part of the parameters for each panel, with the ability to expand it by hovering
Hello! Gamedev designers have been adopting Figma more and more into our workflow, and we would love more controller support for better prototyping and navigation options. Some examples: Better joystick radial support. We currently only have up/down/left/right stick movement, but to prototype menus like weapon wheels and radial selections we need more precise input. Hold button + long press button options for D-pad, face buttons and shoulder buttons. Support for swipe gestures on the PS5’s touchpad. To do any of the above we currently need to jump through hoops and map controller inputs to keyboard buttons through 3rd party software, which is not great and doesnt work for many of the above options. If the community has more suggestions, please leave a comment below 🙏 Thank you!
Hello, Someone already posted this, but i was too late to see it, so im posting again. I have a very similar issue. For my part I find it almost impossible to see where a comment should have been if you’ve already moved things around and of course simply Showing Version History doesn’t include comments even if they were present in those versions. I’ve had to rely on context clues and directly asking the commenter for clarity when this happens. Below in quotes was the original poster’s issue “Would the Figma Team please show comments in the SHOW VERSION HISTORY? Right now, I look at comments in the current version, inspect the SHOW VERSION HISTORY, and take a screenshot to see where an orphaned comment should go. And I will look at the comments and the versions because I want to see the state of the wireframes on that date. Thanks for the consideration!”
Hello, I am working on a class project where I am prototyping a map for a small museum space. My goal is to have 4 buttons at the bottom of the display that when tapped, highlight different activities that correspond to each. Attached below is a screenshot of what I have so far (sorry for the lines across I have other interactions). In short I need each button to: when pressed highlight each shape of the corresponding color when pressed again revert those shapes to their default settings allow other buttons to be pressed at the same time, since some activities will correspond to multiple things Any help would be greatly appreciated!
If you see the screenshot that I attach, the annotations appear in Design mode. I believe that they should appear only in Dev mode. Please advise how I can fix this situation.
ngl, the new ui3 is pretty good. the only thing i dont like is the toolbar position. im still not used to it. maybe add an option to move it to the top?
Hello! I desperatly trying to find out, why the IOS Assets (or components) can not be seen in the Prototype but in the figma file. What am I doing wrong? Wether if I copy and paste the assets to the frame or inserting it, i dont see anything. Is there something to activate or something? Im am using a windows laptop, freshly updated, drivers are updated. It’s so frustrating. In Prototype Mode In Figma File
I’m reaching out to see if anyone else has encountered a bug with local variables in Figma. I’ve created local variables (color, text, etc.), but after applying them to components and assets, they sometimes vanish and become detached after a while. This can be frustrating and disrupt the workflow. Has anyone else experienced this? Are there any known workarounds or temporary fixes? Could it be related to a specific Figma version? Thanks in advance for sharing your experiences and any insights!
EmizenTech is a trusted mobile app development service provider with over 11 years of experience. With 1000+ successful projects launched and 450+ delighted clients, they are experts in creating high-quality mobile applications. Their services include Flutter app development, Unity mobile app development, cross-platform app development, Android app development, and iOS app development. Whether you're looking to build an app for Android or iOS or need a cross-platform solution, EmizenTech delivers efficient, scalable, and innovative mobile app solutions tailored to your business needs. Choose EmizenTech for top-notch mobile app development with proven expertise and customer satisfaction.
Hi, I am using an android table to use Figma. Both the actual app and the website run on Chrome won’t give me the option to edit anything. I need to use this app for my class and the time I’ve waisted from trying to figure out what’s wrong is effecting my grade.
Figma has removed the ability to switch frame between Portrait and Landscape mode (without adding rotation to nested elements). Now the only option is to “rotate” the canvas and it adds -90degress to everything that is designed within. Which also flips W and H. And if a component is designed in portrait and then added to landscape (rotated artboard) and you want to “fill” autolayout and contraint proportions totally mess up. I could make my own frame and use that instead, but I cannot save it as a template within Frame templates, super annoying. Bring this back please: https://www.delasign.com/blog/figma-frame-landscape-portrait/
I want to use magician but it is asking for an access key. Where can I get the access key?
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
