Revert the new UI update or allow use the old one

[latra]

I'm sorry to whoever worked on the recent UI update in Coolify, but I honestly think it was one of the worst design decisions.

I recently updated my Coolify instance, and I was really disappointed with the new UI. The previous design was cool, simple, original, and very functional. The new one feels like an AI-generated interface: everything takes up more space, there are rounded elements everywhere, and the traditional view has been lost.

For me, this is a clear UX downgrade. The previous UI was much more compact, intuitive, and information-dense. Now, simple things require more space and feel less efficient.

I really hope you consider bringing back some of the simplicity and density of the previous design, or at least provide an option to use the traditional view.

[Cinzya]

provide an option to use the traditional view.

Mainting two different views is a lot of overhead which is most likely not something the devs want to do.

I really hope you consider bringing back some of the simplicity and density of the previous design

That option is still possible. Do you mind sharing more specific what exactly felt more simple and dense to you compared to the previous designs?

[EddieZell]

What I've noticed, the settings tab to the left containing General, Domain, Advanced, etc... is too long. Finding anything there just takes too much time. For example, if i press on "Webhooks" i get to the webhooks page, then if i press "Deploy webhook" below it i get to the same page. It doesn't really have a purpose. For General and Advanced it's understandable why the sub tabs are there, but even for those i don't find them useful. Just having the first tab levels is plenty enough. Also, the new domain page isn't that useful either. Just having an input field on the General settings page with a small option button next opening a popup would probably be better. I don't want to be too picky, but also the text below the domain on the settings page "Manage DNS checks and redirect settings", is just cluttering the space and makes it look AI generated. Just keeping it simple overall with optional buttons to popups with further settings keeps it quite simple.

[Cinzya]

@latra friendly reminder about the above. We are still interested in hearing your thoughts and getting more specific feedback. 😄

[latra]

Hi! Apologies for the late response.

Well, specifically, the main issue is that you can no longer see everything at a glance. The submenu for a service (at least when the source is a Git repository) is significantly longer than before, which makes everything harder to find.

The UI now has too many emojis, like when I ask Claude to build something for a weekend-boredom project and it ends up looking like a frontend made for kids.

The background colors have changed slightly, but they’ve lost the Coolify essence and turned into a generic palette, at least in dark mode.

But my problems with the new versions don’t stop at the UI. They also affect member permissions, and now everyone who needs to redeploy an app because of an update (we work with an internal self-hosted GitLab, so using apps is not an option) has to be an admin.

So, at the moment, I think we’ll probably just downgrade to an older version.

I see people around here who are happy with the new UI, so maybe it’s just us. You can’t please everyone, after all.

In any case, thanks to all the maintainers for keeping this amazing project alive! ❤️

[latra]

Ok, let me be more specific and go through my concerns side by side. Maybe you agree with some of these points and we can find a middle ground :D

This is not a priority order, just the order in which I noticed things.

1. The new environment creation flow

When you create a new project (with only one environment), both the old and new UIs show the current environment (production). However, creating a separate environment feels more intuitive in the old UI: click on production → create/edit.

The new one feels a bit more convoluted: configuration → clone environment → form to create the new one.

2. Creating a new resource

Besides the fact that everything is now inside rounded boxes (which is related to my initial concern about the "AI-prompted UI" feeling), we can no longer choose the environment when selecting the resource. You can't see the selected environment either.

I personally prefer getting rid of the "Deploy" buttons, but the Docs button in the new UI is a nice addition.

3. Resource view

The old one looks much clearer, simpler, and easier to navigate to me. The new one feels oversized, or maybe it's just that there are too many "sections" in the first view, which makes things harder to find.

Simple things (that I use quite often, at least) are harder to find quickly.

Also, there's a lot more scrolling because of all the space the rounded boxes take up.

There are many other things similar to these points that I feel are hurting the UX, but after writing all this, I think 80% of it might just be my box-phobia 😅

[nightintoxicated]

second for the old UI, the new one feels overwhelming and hard to navigate, its do able, but it feels like im having to navigate a puzzle every time i use coolify currently, its getting in the way, whereas it used to "just work"

[Cinzya]

Do you mind going more indepth what parts specifically feel harder to navigate? As previously mentioned, the old UI probably won't return, but the team is willing to make improvements where they can. We just like to know what exactly users don't feel comfortable about it.

[striker561]

The UI overhaul is solid overall, but it breaks long-term muscle memory in ways that slow down daily workflows.

Like:
Navigation: Previously, hovering over the breadcrumbs at the top let you quickly switch between services in an environment or open them in a new tab.
Layout & Discovery: Finding core items like deployment logs and environment variables takes an extra second because their positions changed. Locating primary actions (deploy, start, stop) becomes even less intuitive as it requires extra clicks.

We’re basically paying the redesign tax through this friction right now. The new design looks cleaner, but restoring those friction-free navigation shortcuts would go a long way for power users.

[nightintoxicated]

of course, and just to be clear, i don't want to take away anything from the project, its heavily impressive and we love it :)
the things that stand out are things like the http(s) link, having to now click through to another window to use it and locate the small cog to edit it, not a big issue, just feels like a new extra step than hovering over for a link, the left column for settings on a project referring to a section of the general page and not being collapsible makes it a little overwhelming at first, there's a lot of options, its useful to see them but hard to find what's needed, perhaps if they were collapsed at default it'd be easier to work with (in my opinion), though, were still getting used to the layout so maybe that opinion will change, i much prefer the new environment variable system :)