Share Your Thoughts

Since Scaling Icons or Components through width and height does not scale strokes and font sizes, how about adding a number variable to the scale factor of the scale tool and also add that scale property to the general frame position and size controls (maybe next to “clip content”? Whole components scaled via the scale tool with variable modes would be faster than creating endless tables of sizing parameters for each element you need to scale (strokes, text size, effects…) where you do not need precise control of each property.

The new update in the seats name says the Dev Mode is only able in the Full seat, previously known as Editor. In my company, we want to give the developers the ability to use Dev Mode, but not give them permission to Edit the file. Maybe add a cheaper seat than the Full one only for Dev Mode so the devs can actually see all the useful information without moving by accident anything of the design?

It would be really cool if Figma had a native Wireframe library that housed common elements for rapid prototyping built into the design section. Think of it like Figma’s proprietary design system for its users.

Maybe it will be great if Figma Add Shape builder tool and Stroke width tool to its app for helping many illustrator out there that use Figma for making illustration. What you do you think about it guys? Do you think Figma should add these tool ?🤔🤔

Having an extensive design system for which we have created a separate file for token library that we use when designing, The border tokens do not get applied and does not show when its applied Library is published does not have any issue with value used in spacing , only in borders its getting heavy

I know there are many other threads talking about this issue, but I want to highlight a particular case. I’m working on a single project with a free plan. We are just two users: I’m a designer, the other user is developer. He only needs to inspect my design properly without editing, and has been using Dev Mode until now. The ONLY thing we need is keeping the Dev Mode for him. When I click on “upgrade”, we both appear as “clickable” for upgrading to two seats, but when I deselect me, it converts me directly in a “view-only” user. So if we want to remain the same but with Dev Mode for the developer, we have to pay for two seats! How the hell don’t you offer a plan for just allowing developers to inspect the design properly, without converting him in a editor and without downgrading me to only-view? Figma, did you really study this new move you made? Because I think it won’t have the consequences you want.

Could we please add the Go to main component button on the Prototype page as well? I find myself needing to refer back to components even when im in prototype mode. Thanks!

I have a slide deck that’s 1920x1080. Normal. Have a little icon for “next” at the bottom of each slide, hooked up correctly to the prototyping tool. Click, scroll to next slide. When I send the link to anyone, including myself, the slide stays within boundaries when the phone is in Portrait mode, but when it is in landscape mode it’s totally unusable. This means that people I’m pitching have to try to read text that’s compressed from 1920 width to like 386 width. Attached are photos. And Community Manager you are welcome to give me a workaround, but your product team should just implement a “Present” version of a prototype, and there should be a setting that “constrains” bleeds and overflows.

Since we have the Dev Mode users now, it is possible to have a column like “ last Dev Mode usage” or something like that on exported csv file for the membership list? Currently there are two columns like these: last_edit_Figma last_edit_FigJam They are very useful for member management.

After setting up the button components with the “on click” action, it’s hard to add another “on click” to trigger the overflow.

Since the new preview window option was added this seems to be the default behaviour for the flow starting points. I still want to use the original (fullscreen) present option to display prototypes. How can I set the present as default option for these little labels next to artboards to directly open them in that mode from there? Thanks

It is difficult to pick the prototype link, when have a bunch of links. So if you guys give the option to search Prototype links option, It will be helpful.

It’s great that comments are attached to the parent Frame, but there are some use cases where it becomes valuable for comments to attach to a frame that is inside of another frame because of auto-layout. This Loom recording demonstrates the use case Loom | Free Screen & Video Recording Software

日本語にて失礼。 現状、コメントの仕様として最も外側のframeにXY軸絶対配置で吸着し、frame移動時にも追従するような挙動となっています。 この仕様で困る点は、frameが入れ子構造になっている場合、本来吸着させたい要素（例：ボタン要素など）にコメントをつけようとしても、それを包含している最外のページレベルframeに吸着してしまうせいで、ボタンの位置を移動した際などにコメントが追従してこず、コメントの位置調整を手動で行わなければならないという問題です。 ほとんどのケースにおいてframeは入れ子構造になるため、実質コメントの追従は不可能というのが現状でして、これを回避するためには「一旦要素を最外frameの外側まで引っ張り出してからコメントを吸着させ、Undoを使って元の位置に戻すことで吸着・追従を維持する。」と言ったグリッチに近い操作手順を踏まなければいけません。 また、このグリッチは最近挙動が不安定になってきており、再現性が低くなってきてしまっています。 要素の修正やpublishされた要素をupdateする度にコメントの位置を手動で全部調整するのは時間の無駄でしかないうえに、コメントの位置がずれていることによってコミュニケーションエラーが発生する原因にもなってしまうため、公式で特定要素に対してコメントを吸着・追従させられる機能の実装を強く求めます。 ご検討のほどよろしくお願いいたします。

I met recently an issue with the calculation of a footer height in prototype mode. In order to replicate this: Build a standard footer Place as an overlay, above it, in absolute position, an object that is higher than the footer itself Ensure that a mask hides all object parts that are going beyond the dimensions of your footer. Insert this footer in a very long page and reduce the viewable limits to the device window size. Play the prototype. When playing your prototypes, the object in absolute position will disturb Figma: it won’t be able to restore the positions of your objects and it will create huge margins on top and bottom when scrolling. It can be very annoying if you want to use SVG decoration symbols/patterns on backgrounds per example, as you will be forced to use plain image backgrounds instead.

When a developer requests the DEV mode, we receive a feedback that does not match with the original action as it states that the developer wants to EDIT a content. We simply need a box that says that the developer wants the DEV mode, nothing else. EDIT is for EDITORS, not developers.

Current way to manage user permissions benefits from a double entry point that is not logical to me. Can’t we have a unique manner to see all permissions and to add remove/members in an easy and clear manner? See my screenshots.

Save the drawing area in a certain zoom/positioning - almost like in Sketchup - This way we can easily navigate from one sketch into another without having to scroll manually. It will ease all the creation vs navigation process.

This post is a thank you message, The ruler in dev mode is amazing, the simple usage and the usefulness is beyond any other tool, it accelerates my job as a developer by a lot. Thank you Figma team 🙂

For better orientation when discussing screens, an overlay w/ a simple grid could be great. So one could say “Could you enlarge screen ‘H9’, please?”, and it would be clear which screen is meant. And no-one would have to place such marks upfront manually (which is a lot of work to maintain when the screen flow evolves and the screens become moved, and further screens are added). The grid could show up when pressing a defined key (e.g. “g” for “Grid”), and vanish when releasing the key again. Maybe an additional tool button could make sense for showing the grid permanently during a discussion. The lines of the grid could always be the opposite color of the color on the screen (like when pixels covered by a line are white, this part of the line appears black - and vice-versa). Note that this is not shown on the attached screens. The grid could e.g. be always 26columns (labelled a-z)/20rows (1-20), and resizing could shrink/stretch the columns/rows. This would allow to not having to find

Implement a “Refresh” button to update and display newly installed fonts within the system for improved accessibility and immediate visibility in the application.

Implementation of a “Selection typefaces” menu when selecting a frame. This feature would facilitate the seamless replacement of employed typefaces by utilising styles available in designated libraries.

A few improvements for the admin panel/setting up new users: When an invite is sent out, let us pick at that point what access the user will have for Design, Dev, and FigJam. It’s a pain in the butt having to go back to see if/when people have accepted the invite. Also at the new user set-up; would be helpful to have an option for length of time the user can have editor seat(s). Example: we are hiring many 12-18 month contract positions currently. Checking off that they’re a contract employee for 12 months and then admins get a notification around the contract end date as a reminder to adjust the access. Setting up notifications for users who have been been completely inactive for X amount of time - to prompt admins to review and see if user still needs Figma.

Duplicating (copy+paste) someone’s sticky note and turning on author shows the original sticky note’s author—I think it should show the new author. Is this the intended behavior?

Introduce a functionality to display all utilised styles within a file, enhancing the ease of examination of the full project and facilitating the straightforward replacement of incorrect library styles (colours, typefaces, effects).