macOS Golden Gate Developer Beta 3 feels like a step backwards

[lmaodzedun]

I tested macOS Golden Gate Developer Beta 3, and the UI feels noticeably worse than it did before. Apple seems to be reacting to loud feedback from people with very little experience using desktop software, and the result is a system that is harder to read and harder to use.

In Light Mode, Apple has weakened the contrast of toolbar buttons significantly. They now blend into the background far more than they used to. Meanwhile, the same controls remain clearly visible in Dark Mode. The two themes no longer feel balanced or equally considered.

Apple also removed the subtle bright edge around windows in Dark Mode. That thin line made the outline of each window much easier to see, especially for people with imperfect eyesight or on darker wallpapers. Without it, windows blend into the desktop and it takes longer to understand where one surface ends.

The transparent app icons have also become less readable. Their outline details are weaker, so the icons look softer and less distinct in the Dock. Apple appears to be chasing a flatter, lower-contrast look at the expense of clarity.

The new video wallpapers are another weak point. Many of them look like generic Shutterstock footage with little visual character or composition. On my 6K monitor, they also look extremely poor: low resolution, heavy compression, visible artifacts, and no detail. They are distracting in the worst way because they look expensive at first glance, then immediately fall apart on a high-resolution display.

Beta 3 left me with a very bad impression. Golden Gate was supposed to improve on Tahoe, where many of these visual issues were already present. Instead, Apple has pushed the system further toward low-contrast decoration and away from the clear, professional desktop interface macOS used to have.

Apple needs experienced senior interface designers who understand desktop UI, visual hierarchy, accessibility, and high-resolution displays.

 

[Apple Knowledge Navigator]

Apple seems to be reacting to loud feedback from people with very little experience using desktop software

I agree with your points, but from what I gather, the entire opposite is true and it is the people with very little desktop software experience who seem to think that Liquid Glass is cool purely on the basis of being different.

 

[lmaodzedun]

I agree with your points, but from what I gather, the entire opposite is true and it is the people with very little desktop software experience who seem to think that Liquid Glass is cool purely on the basis of being different.

That is exactly what bothers me. Liquid Glass seems to be judged mainly by whether it looks new and visually impressive in screenshots, rather than by how it holds up during a full day of desktop work.

A desktop interface has to make controls easy to find and boundaries easy to read. If toolbar buttons blend into the background, window edges disappear, and icons lose definition, then the visual effect is taking priority over the job the interface has to do.

I do not think everyone who likes Liquid Glass is inexperienced. I think Apple is treating visual novelty as a success metric while overlooking how these choices affect clarity and long-term use.

 

[2638se]

There were no white edges when Dark Mode got introduced in Mojave and It's beautiful and perfectly legible.

Apple added those edges in Catalina and It became stupidly brighter in Tahoe (while being uneven, the upper edge is even brighter). It really is just too bright and unnecessary, Apple is right to remove those.

 

[lmaodzedun]

There were no white edges when Dark Mode got introduced in Mojave and It's beautiful and perfectly legible.
View attachment 2643710
Apple added those edges in Catalina and It became stupidly brighter in Tahoe (while being uneven, the upper edge is even brighter). It really is just too bright and unnecessary, Apple is right to remove those.

Mojave may have looked fine to you, but Apple’s own design history shows that this has never been fully settled. Since the first Tahoe betas, Apple has repeatedly adjusted the strength of Liquid Glass, transparency, contrast, highlights, and window separation. That suggests they are still trying to find a balance between visual effect and usability.

I do not think Mojave proves that window boundaries are unnecessary. Apple added more visible separation in later releases for a reason: enough users likely had trouble distinguishing dark windows from dark wallpapers or other dark surfaces. Tahoe may have pushed that treatment too far in some places, but Golden Gate is now moving in the opposite direction and weakening the separation again.

My use case is not a single full-screen app with a tiled layout. During a 10–15 hour workday I often have more than fifteen windows open: browsers, Figma, VS Code, Finder windows, mail, chat, video calls, documents, and reference material. I resize them manually and switch between them quickly while presenting work in meetings.

In that situation, I need to identify each window and its boundaries immediately. I should not have to stare at a dark desktop trying to determine where one surface ends, or hunt for a low-contrast toolbar button during a presentation.

I want macOS to remain beautiful. I just do not want Liquid Glass, reduced contrast, or softer edges to make the default interface harder to use. A professional desktop OS should provide strong readability by default, without forcing users into accessibility overrides simply to make ordinary controls and windows clear.

 

[lmaodzedun]

I do not dislike Golden Gate overall. I like much of the new visual language, including Liquid Glass. My issue is that Apple keeps letting the glass effect take priority over readability and long-term desktop usability.

This is not just about one Finder toolbar. It is about the whole system losing small visual signals that make a desktop easy to operate for hours: clear control shapes, enough contrast, distinct icon silhouettes, readable window boundaries, and good separation between layers.

Apple has gone through this cycle before. Yosemite made parts of macOS too pale and washed out, then El Capitan restored more definition. Mojave Dark Mode did not need a visible bright outline around every window because Finder had a denser, more dimensional gradient treatment. The window itself had enough visual weight to stand apart from the desktop. Later Apple kept experimenting: Catalina added stronger window edges, Tahoe made them more visible, and Golden Gate weakens them again. Apple has clearly never fully settled on how dark windows should separate from dark wallpapers.

That experimentation is normal in a beta. The issue is the direction. Golden Gate often removes structure instead of refining it. In Dark Mode, some controls remain reasonably distinct, but window separation has become weaker. In Light Mode, the glass treatment makes parts of the interface softer and harder to scan. The two themes no longer feel equally resolved.

Native tiling does not solve this. A professional desktop workflow is not always one full-screen app or two perfectly snapped windows. During a long day, I may have browsers, design tools, editors, chat, video calls, documents, mail, several Finder windows, and reference material open at once. They all need different sizes and positions. I need to identify windows, boundaries, active surfaces, and controls immediately, without stopping to inspect the screen.

The aerial screensavers show the same problem from another angle. Older landscape videos from Mojave, Catalina, and Big Sur still look sharp, calm, and properly composed on a large display. Some newer Golden Gate aerial videos look heavily compressed on a 6K monitor, with weak detail and visible artifacts. They may look dramatic in a small preview, but desktop wallpapers need to hold up for hours on a large screen.

Liquid Glass can be beautiful. I am not asking Apple to remove it. I am asking Apple to stop sacrificing contrast, edge definition, and image quality just to make the system look softer or more modern. A beautiful desktop OS should still be immediately readable and comfortable to use all day.

 

[2638se]

My use case is not a single full-screen app with a tiled layout. During a 10–15 hour workday I often have more than fifteen windows open: browsers, Figma, VS Code, Finder windows, mail, chat, video calls, documents, and reference material. I resize them manually and switch between them quickly while presenting work in meetings.

If that’s your use case you are an advanced user and should expect to tweak the system to work better for you really. That new accessibility setting that enables distinct outlines is prepared for you. It’s unreasonable to wish the system to look drastically worse to normal people (when it’s already distinctive enough without those white outlines in normal use cases) just because you don’t want to change your wallpaper or enable one setting.

 

[lmaodzedun]

If that’s your use case you are an advanced user and should expect to tweak the system to work better for you really. That new accessibility setting that enables distinct outlines is prepared for you. It’s unreasonable to wish the system to look drastically worse to normal people (when it’s already distinctive enough without those white outlines in normal use cases) just because you don’t want to change your wallpaper or enable one setting.

I disagree with the premise that this is an unusual or specialist workflow. Working with many independently sized windows, reference material, editors, browsers, calls, and files is normal desktop work for designers, developers, analysts, researchers, and many office roles.

Accessibility settings are useful when someone needs additional support. They should not become the default answer whenever the base interface loses visual structure. Clear boundaries and readable controls help everyone, including people who never touch accessibility settings.

You also describe the old treatment as making the system “drastically worse” for normal users, but that is your visual preference, not an objective rule. A subtle, consistent window edge does not have to be a bright white border. Apple can preserve clean aesthetics while still making windows immediately distinguishable from dark wallpapers.

Changing my wallpaper or enabling a system-wide override does not address the design issue. The default interface should work well across common desktop workflows, including multi-window work, without requiring users to compensate for weaker contrast themselves.

 

[2638se]

I disagree with the premise that this is an unusual or specialist workflow. Working with many independently sized windows, reference material, editors, browsers, calls, and files is normal desktop work for designers, developers, analysts, researchers, and many office roles.

Accessibility settings are useful when someone needs additional support. They should not become the default answer whenever the base interface loses visual structure. Clear boundaries and readable controls help everyone, including people who never touch accessibility settings.

You also describe the old treatment as making the system “drastically worse” for normal users, but that is your visual preference, not an objective rule. A subtle, consistent window edge does not have to be a bright white border. Apple can preserve clean aesthetics while still making windows immediately distinguishable from dark wallpapers.

Changing my wallpaper or enabling a system-wide override does not address the design issue. The default interface should work well across common desktop workflows, including multi-window work, without requiring users to compensate for weaker contrast themselves.

Have you tried window managers like amethyst/yabai/aerospace? I sincerely think your workflow (with 10-15 windows in the same desktop at the same time IS advanced although you don’t admit it) would be much smoother with one of those rather than fiddling with window resizing/positioning manually all the time.

 

[tomtattoo]

First hour on GoldenGate.
Apple still stuck in their "dark mode hell" - on iOS I could write a thousand words.

But here we are in MacOS..
WHY is the battery widget not the same as the other ones? Looks horrible.

 

[Lounge vibes 05]

Accessibility settings are useful when someone needs additional support. They should not become the default answer whenever the base interface loses visual structure. Clear boundaries and readable controls help everyone, including people who never touch accessibility settings.

This feels like an extremely narrow minded view of accessibility settings. They aren’t just for those who need them, they’re for anyone who wants to use them.

I have absolutely never understood this fear or embarrassment people have over using a system setting that’s labeled “accessibility.
Do you want the window borders, window borders is an accessibility option, use the accessibility option called window borders.Uggh.

 

[fisherking]

beta 3 is faster here, pretty stable... in places. i can't export 'clean-up' edited photos from photos app. stem splitter crashes logic pro. some other quirks.

like all betas, things get fixed, others break. so it goes, it's what we signed up for (if we're running betas).

 

[vbctv]

Only issue I'm seeing in Beta 3 on the Neo is the Finder icon in the dock is missing, only in Dark icons. Otherwise the beta is very stable...

 

[Killerbob]

With Beta 3 I have found a number of new issues:

• Some videos no longer play in Safari or in Chrome (so not application dependent). They just start and freeze.
• I have a 2 screen setup with my Mac Studio, and a 2 screen and built-in screen setup with my MacBook Pro, and quite often if I go to File, or Edit in the Menu Bar, it doesn’t open on the screen the app is open in, but rather one of the others.

I know they will most likely be fixed in Beta 4, but why the step backwards…

 

[fisherking]

With Beta 3 I have found a number of new issues:

• Some videos no longer play in Safari or in Chrome (so not application dependent). They just start and freeze.
• I have a 2 screen setup with my Mac Studio, and a 2 screen and built-in screen setup with my MacBook Pro, and quite often if I go to File, or Edit in the Menu Bar, it doesn’t open on the screen the app is open in, but rather one of the others.

I know they will most likely be fixed in Beta 4, but why the step backwards…

every beta brings new fixes, and new issues... it's never a straight line forward 🤷

haven't seen either of those issues (altho not watching many videos). as for the menu bar thing... perhaps try changing (& changing back) some settings is the display options.

 

[Killerbob]

every beta brings new fixes, and new issues... it's never a straight line forward 🤷

haven't seen either of those issues (altho not watching many videos). as for the menu bar thing... perhaps try changing (& changing back) some settings is the display options.

Oh, I know the Alpha/Beta testing path very well. Just annoyed that basic things seems to be jeopardized this time around.

I'll give it a try and flip a few switches in display options.

 

[Killerbob]

Here's another one;

Try and have two apps open on two different screens. Select one app, and you can click on the menu item, say the app's name for instance, and the menu opens up. Click again, and the menu closes.

Now try that for the other app, on the other screen, without selecting the app first. The menu items are not highlighted, but you can still open up the menu, clicking the app's name for instance, but you can't close it again...

 

[fisherking]

Here's another one;

Try and have two apps open on two different screens. Select one app, and you can click on the menu item, say the app's name for instance, and the menu opens up. Click again, and the menu closes.

Now try that for the other app, on the other screen, without selecting the app first. The menu items are not highlighted, but you can still open up the menu, clicking the app's name for instance, but you can't close it again...

just tried this, and not experiencing that... does it happen with any 2 apps?

 

[Killerbob]

The ones I have tested it with; MS Teams, Outlook, Safari, Messages, yes. And it extents to that I can move through the menu items on the menu bar, and they open without me clicking on them, as I am moving my cursor... I just can't close the menu item by clicking on the menu item again. I click anywhere else, and the end item closes.

As for the menu items openning up, on another screen, or even on the other side, see this:

 

[Apple Knowledge Navigator]

every beta brings new fixes, and new issues... it's never a straight line forward 🤷

The original poster never suggested otherwise.

 

[fisherking]

The ones I have tested it with; MS Teams, Outlook, Safari, Messages, yes. And it extents to that I can move through the menu items on the menu bar, and they open without me clicking on them, as I am moving my cursor... I just can't close the menu item by clicking on the menu item again. I click anywhere else, and the end item closes.

As for the menu items openning up, on another screen, or even on the other side, see this:

View attachment 2644302

so... i just experienced this, first time. ouch! hope this gets fixed soon (life on the betas is so... beta...) 🤔

 

[Killerbob]

I have a question… These Developers’ Betas, are they not actually Alphas?

Developer Beta 1, 2, and 3 = Alpha
Public Beta = Beta

A lot of folks do not seem to understand this process, and expect fully working solutions on the first go, and yes, it is annoying when things work, and then they do not, but that’s why these “releases” are Alphas and Betas… Not until Beta (at least) can/should you expect most things to work, and even then, don’t complain if something is still cooking.

In software development we call this Development -> Unit Testing -> Integration Testing -> End-to-End Testing -> Release. In other words, Alpha -> Beta -> Release Candidate -> General Availability.

 

[Jakimo]

I have a question… These Developers’ Betas, are they not actually Alphas?

Historically, I've understood that alpha builds were in-house only.. and beta builds were for outside-help testers

Honestly, the 'dev beta' builds we get are WAY high quality to call them 'developer betas' - alas, many on these forums think otherwise =/ =)

 

[Killerbob]

Historically, I've understood that alpha builds were in-house only.. and beta builds were for outside-help testers.

I hear that. But, if Developers’ Betas are indeed Betas, then what is the Public Beta? Gamma, based on Alpha (α), Beta (β), Gamma (γ), Delta (δ), Epsilon (ε) and Zeta (ζ)?

 

[Situationen]

I hear that. But, if Developers’ Betas are indeed Betas, then what is the Public Beta? Gamma, based on Alpha (α), Beta (β), Gamma (γ), Delta (δ), Epsilon (ε) and Zeta (ζ)?

Well, the Public Beta will as far as I know be the same build as the then latest developer beta. Both are Betas, just the general public only get to test every third or fourth beta build as the developers get. Beta is beta.