I can see that “bias”- sure, alot of negatives here. But i feel that the negative is genuinely developers trying to tell you something. There is resent against a certain thing, but you take that as “biased negative” and it ends up not reading as the community wants it to be read. Sure, theres some bias. Everything is biased. Human nature. The community would & has given feedback on things. There are plenty of threads with positive messages, tips on how Roblox could improve, and alot of people are frustrated because they genuinely feel unheard. Theres no proof they’ve been listened to, and no signs either. I am starting to warm up to the new UI, dare i say, and if you turn off Compact Toolbar (which i think everyone should) it does actually get alot better, adressing the strange button sizes.
Yeah the old UI was great i got used to it despite the previous changes and now that,now their UI is not Userfriendly at all i get that they wanted to add more customizable functionality but now when i test or want to find something specific,its just extremely slow and frustrating compared to what i got used to its not cool!!
to be honest i was pushing against the new ui harder than I should’ve (see: my previous posts lol)
I’m starting to get used to the new ui, but this would’ve all been much easier with accessibility options. changing the color scheme would be incredibly beneficial for my acclimation.
id still use the old ui if given the chance tho
I unfortunately have to agree! I’ve been trying out the new Studio UI for a while now and it feels incredibly lacking compared to the old layout. The more I use it the more unnecessary the revamp feels ![]()
Tools became harder to find and, ironically, I actually feel a major step backwards in customizability. One great thing about the old toolbars was that they offered easy access to nearly every tool Studio has to offer. With the new toolbars however, I noticed they lean towards modernized looks at the expense of raw utility.
- The layout feels bloated and unconventional, there’s a lot of space wasted with padding and spacing on buttons, and things like rounded corners add to visual noise;
- tools are hidden away by default, making it really hard to use as an already experienced user, and presumably making Studio really unfriendly to grasp and explore as someone new;
- as I mentioned before the color changes end up being really uncomfortable, but I’m glad to be assured that’s being worked on;
- the behavior of the new collapsible toolbars is really annoying really frequently, and features like the Quick Access bar become more prominent once you can’t use them anymore.
While a UI refresh coming along with the backend reword did sound really exciting on paper, the way it was delivered had been really disappointing from the start, and didn’t improve over time. I understand there’s no going back to the old UI, which I would still undoubtedly prefer to use, I do feel like this UI could still be made work given some major tweaks and changes. And I hope this doesn’t come along too negatively, it’s just genuine feedback from my experience that I wanted to share.
@MeshOfPaul
You can help mitigate this by l-clicking the toolbar then clicking Compact Toolbar. Makes the buttons bigger.
There’s actually virtually no padding between the buttons. But I understand the perception and our design team is working on some tweaks we hope to land before late March.
This includes some changes to the collapsing toolbars. The difference here from the old collapsing is the toolbar “floats” so it doesn’t thrash/bounce your layout. So if we didn’t autohide the toolbar it would obscure the UI elements behind it. But we think we have a good idea for enabling similar to the old behavior (while also keeping the autohide/floating option for those that like it)
So thank you for the feedback and patience. I’m sorry it’s not living up to your expectations but we are continuing to chip away at it.
I am not discounting the feedback nor am I saying it’s all bad/negative. All I was trying to explain is you can’t look at the feedback on DevForum and assume it represents a majority of the creators using Studio.
Compact was not the default mode for many months, but we were asked to change that based on feedback. ![]()
If you can’t look at both negative and positive feedback and assume it represents the majority then isn’t it better to find common ground? Perhaps by making it customizable enough to the point that we can make it look very close to the old version (maybe via a legacy preset)
I just feel like Roblox has a history of pushing updates without finding any middle ground, forcing changes onto users based on what appears to be confirmation bias and only after heavy backlash do they seem to consider changing them.
does anyone have a solution to get rid of the new forced UI that works right now?
The source code of the old ribbon has been removed from the application. It is recommended that you try to get used to the new UI.
i literally cant. the ui hurts my eyes
any info on the release date of studio themes?
still looking for one
Summary
This text will be hidden
The ribbon is more responsive after v709. Good.
But there’s still critical regressions in the nextgen interface.
-
Information Density:
The padding and margins (assuming it’s the size of the buttons/containers) are significantly higher than professional tools like Blender or the 2008-2012 Studio UI. Large internal padding and high minimum heights for Ribbon components result in a “solid wall” of UI that wastes screen real estate. Power users need a high-density mode with smaller hitboxes and sharp corners to match the efficiency of tools mentioned above. -
Chromatic Fatigue (Theme):
The new blue-tinted black theme causes more eye strain over long sessions than what we had in the old UI. Releasing this without custom theme support is a step back for developer health. -
Performance Overhead:
The Luau/React stack introduces “middleman” latency.I noticed ReactFiberWorkLoop collapses and GlyphProvider invalidation errors in the output windownvm, possibly causing CPU spikes and UI hangs that native C++ implementations simply don’t suffer from.
Furthermore, the reliance on Edge WebView2 for windows like the Toolbox/Creator Store creates massive bloat. Mid-range hardware (Ryzen 5000-series mobile) experiences significant latency. We are essentially running a web browser inside an engine just to view assets, which is unacceptable for a professional IDE.
Professional developers need an interface that prioritizes native speed, crisp rendering, and information density over corporate aesthetics. Please prioritize theme customization, component scaling, and the optimization (or replacement) of these browser-based abstraction layers.
we still need one. anyone know?
Summary
anyone? please? help pls ![]()
![]()
![]()
![]()
![]()
![]()
Exactly why the new UI isn’t beneficial. Couldn’t have put it better. Even makes me wonder - if the backend rewrite was ‘necessary’ because the old one was ‘restricting’ them, what sorts of features are they even planning? It’s scary to think what the future of Studio (and Roblox as a whole) might be.