Skip to main content
click_Mao
New Member
July 3, 2024

UI3 Feedback

  • July 3, 2024
  • 426 replies
  • 10410 views
  1. What I can’t stand the most is that the panels of the new UI can’t be attached to the edges. They leave some gaps, wasting the space to display the main design and operation area. And visually, these gaps are also distracting my attention.
  2. The toolbar at the bottom also interferes with the main operation space, especially if its color is the same as my design draft. By the way, is it just for the convenience of novices to move it from the top to the bottom? If someone who uses Figma more frequently, he will use shortcuts instead of mouse clicks to trigger these functions.
    So I hope that adjustments can be made in time in the official version of UI3, otherwise these redesign will seem like a subjective conjecture of someone who doesn’t use Figma much.
This topic has been closed for replies.

426 replies

Bauke_Schildt
Active Member
July 8, 2024

I’ve been using UI3 for 3 days now and I am slowly getting used to the fact that my tools have moved to the bottom. I’ll get used to it, but for now I have tasks to do and assets to deliver and the change for accessing the basic tools is too big.

Overall: I think removing the top toolbar was not the best choice. I get wanting to align with FigJam and Figma Slides but those are much simpler tools. Getting rid of the toolbar has created a lot of problems because you’ve had to move the contextual tools within the constraints of the UI panels.

Toolbar

  • Moving the toolbar to the bottom may have freed up a few pixels (The toolbar was 48px high), but half of that that gain is negated by the spacing around the “floating” panels (2x 12px).
  • The top bar also had the F menu and the File menu in it, which have moved to the top of the Left panel, which means they are now further away from the OS Figma menu (in the Desktop App, which all of my team uses) which gives it a cognitive disconnect.
  • Having the Toolbar at the bottom on a Mac means that every time I overshoot, my (Hidden) Mac Dock pops up
  • Vector editing
    Vector editing has become a little harder: Before, when going into node editing mode, the tools were grouped (Select, Pen, Bend, Fill). Now the Direct select (Move) tool is 3 tools away from the other tools and you need to switch between those two for some types of editing.
  • Toasts now show up above the toolbar, but they’re the same color as the toolbar, and when using the pen tool, there are sometimes 3 layers of white boxes taking up a lot of screen space
  • Switching to Dev-mode triggers an animation on the toolbar that will look cool for about 3 times. Especially since Shift-D triggers it too.

“Floating” panels

  • The gap between the panels and the viewport give me a ton of visual noise just outside my field of vision. I’m usually looking at the middle of the screen, but when I move around the canvas I can see things moving in the gap, which is really distracting. Not good for people with ADHD…
    Couple that with the fact that while the panels LOOK floating, they can’t actually be moved, just resized, makes it a purely aesthetic choice, making me wish i could at least turn off “floating” to have the old style full-height, flush panels back. Figma is a tool, and I want functionality, not meaningless aesthetics.

  • The File dropdown menu and the F menu are now taking up valuable vertical space in the File/Assets panel on the left.

  • Left panel

    • File
      Nothing much has changed, but I wonder why I still have to horizontally resize the panel to be able to see all the nested layers instead of having horizontal scroll

    • Assets
      I’m glad you’ve kept the option of a list for the libraries, because I like keeping the panels as thin as possible to have as much use of the canvas as possible and that means I could only see 4 Libraries in Grid view…

  • Right Panel
    Design

    • Context sensitive tools
      The context sensitive tools have moved here from the top toolbar, but the right panel doesn’t have as much horizontal space available, so sometimes those tools are now hidden behind the “…” icon. A little frustrating, especially because this is 100% caused by the fact that you got rid of the top bar.

    • Instance/variant properties
      Nice improvement on the affordance of the text field being visually different from the other variants.
      Moving the properties up means that with complex components with a bunch of properties the Position/Layout panels end up almost on the bottom of the screen…

    • Position

      • Not sure if we really needed the rotate 90º and flip horizontal/vertical tools there, but sure.
      • Rotation being grouped with Position is an odd choice.
      • Separating Position from Width and Height is strange to me. Position and the size of what I selected are linked to me, and in a tool like FigJam it’s not that big of a deal, but for UI design it’s pretty important to place objects in exact positions.
    • Layout

    • With Layout now being separate from position the distance between the Position and Size is really big.

      • I really don’t like the choice of hiding the Width or Height under a hoverstate when layer is set to Fill or Hug. I do not want to move my mouse from the layer I selected over the sidebar, and we’ve lost the “Fixed” indication, which is super helpful when you’re trying to figure out why your nested autolayouts are not behaving like you thought they would.
      • Rotation should be linked to the object I selected
      • Show/Clip Content should NOT be a dropdown, the checkbox is semantically better, especially since the default is “Show content” while the old checkbox was “ Clip content” (Higher cognitive load for people switching to the new UI)
    • Fill and Stroke - no comments

    • Effects
      No idea why this moved up, above selection colors? Effects colors don’t show up in the Selection colors. Unless that’s a future feature?

    • Selection colors
      Selection colors are linked to fill and stroke colors. Having Selection colors below Effects implies that Effects colors will show up in the Selection colors. Effects colors do not show up in the Selection colors.

    • Layout Grid has moved all the way to the bottom, away from “Layout”, which is an odd choice.

    Prototyping
    The Prototyping Interaction pane has improved a lot, but I still feel that it should be possible to see the full set of interactions, especially Set Variable, in one go, and not have to click each one to figure out what they do.

Living.Security.Andy
July 8, 2024

I think as a first impression, I’m liking the more nuanced changes to UI3 so far, but my only complaint is that it’s floating now, rather than docked to the edges of the viewport.

It feels really distracting with Dark Mode on because most of our files have a light background and we prefer to work that way. This creates a “framing” effect where the floating UI creates an odd feeling when panning around the document, since I can see various design elements flying in and out of the gap area — which is why it’s distracting.

It also makes it feel like the floating UI is mistakenly part of the document, as odd as that sounds.

Please consider adding an option to dock the panels and remove the gap 😃

Bauke_Schildt
Active Member
July 9, 2024

Yeah, my ADHD brain does NOT like that gap.

djv
Figmate
Community Support
July 9, 2024

Hey All, thanks for the feedback!

We’ll ensure our UI3 team has eyes on this topic for improvements.

We completely understand how hard it can be to adjust to the new changes. Be sure to take a look at our Help Center article to learn more about Navigating Figma’s New UI.

July 10, 2024

Overall UI3 makes Figma a less efficient tool. When I heard of this new UI release iI was excited for a new and improved Figma experience but unfortunately everything is less organised more visually complex and needs more clicks to achieve which is very disappointing to see, especially coming from a tool made for UI/UX/product design. @Bauke_Schildt really pointed out everything perfectly.

My only hope is that they keep the option of using the old UI2 even after UI3 gets released in full.

Simon31
Active Member
July 10, 2024

Hi @Morten_Stig_Christensen, I like your suggestions. I very much like the look of the new UI (not tried it out just yet). I was concerned a little about more screen space being used up because of the new padding around the sidebars etc for those on smaller displays. It would be great as you have mentioned to have something like Adobes layout selector. You can have the “UI3” and “UI Classic” for example, so you still get the new features just old UI.

July 11, 2024

Exactly the same feeling, like you said about Microsoft. And all of useful tutorials become unusable with these changes. Constraints, components, everything. And too many changes to get used to. As if they wanted to make our lives a bit harder

Drew_Rod
July 11, 2024

and while we’re at it, can we please get a movable UI.

Things like, switching the left & right vertical tools & moving the top tools around or down… pinning them together, to eachother… ect.

Reith_Tracy_164
July 11, 2024

After working with the new UI for a few days, switching back and forth, I’m going back to the old UI. For the new UI, I actually prefer the look of it: it’s more compact with a cleaner presentation. I readily adapted to the placement, but “floating” palettes that don’t truly float/aren’t moveable are frustrating. When I hide the sidebars I need them hidden, not taking screen space (I take a lot of screencaps - don’t judge me 😉 ). The last straw is the gap around the palettes - it’s visually disturbing.

FullTrucker
New Member
July 11, 2024

This seems like the primary UI3 feedback thread, so I’ll add comments here. I agree with much of the feedback from @Bauke_Schildt and what doesn’t resonate with me (e.g. rotation grouped with position seems fine to me) is minor.

It appears that inserting components from libraries is entirely driven by a “search” in UI3, in UI2 one could also “browse” for components by looking through a library. This was important to me in my workflow as I don’t always know what a component is named. For example, inheriting a UI kit from a previous designer or using an extensive public icon library. To go a bit deeper, I use Material icons for many of our projects and I may not always know what the icon is named. In UI2 I could generally “discover” a suitable icon by browsing the pages of the icon library file, which is organized like categories.

This is how it used to be in UI2:

Even if you didn’t enter a search term, you could still click through files and pages and frames to discover what you need. I find this super useful even when using libraries that I curate, as I may not always recall exactly what something was named. And if another designer adds something to our UI kit, the problem is exacerbated.

And now this is UI3, I don’t see a way to discover components by looking at a specific page in a specific file:

It seems that in an effort to simplify this feature or make it “easier” to use, it has become more difficult for me to find things unless I know (or have a general idea) of what the component is named.