Liquid Glass looks pretty from a distance, but my biggest gripe with the design language is just how difficult so many things become to read or interact with. Given that the whole raison d'être of liquid glass is transparent effects, the options to limit that or otherwise increase contrast simply do not go far enough. I also balk at how much extra computing power is needed to generate effects I find no value in and would prefer to disable.

My hope was that Apple would be forced to course correct in subsequent releases but that doesn't seem to be happening.

▲

Reason077 3 hours ago | parent | next [-]

> “My hope was that Apple would be forced to course correct in subsequent releases but that doesn't seem to be happening.”

I’m optimistic that they will eventually course correct on Liquid Glass, but we’ll have to wait until iOS/macOS 27, or perhaps longer.

There are parallels to Apple’s butterfly keyboard fiasco on the hardware side. Sleek looking on the surface but an objective step backwards in usability. Unfortunately it took Apple several years to reverse course on that one.

	▲	kergonath 2 hours ago \| parent [-]
		> There are parallels to Apple’s butterfly keyboard fiasco on the hardware side. There are also parallels with the original pinstripes-and-transparency-everywhere aqua UI. I am also optimistic that it will be toned down over time but retaining the responsiveness.

▲

bs7280 3 hours ago | parent | prev | next [-]

My biggest frustrations with it aren't even related to the look of things, its the all around disregard for user experience. The new screenshot UX on iOS is an insanely bad downgrade.

	▲	SchemaLoad 2 hours ago \| parent \| next [-]
		I think it makes sense. They refocused it on sharing or extracting information from screenshots. Which is what people want more than saving them to the camera roll. Being able to copy text or translate the text in a screenshot is super useful.
	▲	jimsmart 2 hours ago \| parent \| prev [-]
		Just go to Settings > General > Screen Capture, and turn off Full-Screen Previews - which fully restores the previous behaviour. Personally I prefer the new behaviour. But eitherways: it’s just an option.

▲

ibejoeb 3 hours ago | parent | prev | next [-]

The Windows ME/Fisher Price look. I can get past the drag handle problem. It's like every window is now the damn ios simulator.

▲

tailnode 4 hours ago | parent | prev | next [-]

They almost certainly will course-correct in the next release now that the culprit responsible for Liquid Glass is no longer at the company. But they won't chuck it out wholesale; it will be a gradual evolution back to sanity.

▲

dylan604 3 hours ago | parent [-]

They reacted pretty quickly to the butterfly keyboard fiasco. By the time users received the shipping products of the first gen, the second gen were already in the pipeline so there was a slightly modified with only a dust cover being added. There was no third gen.

Hopefully iOS 26.x releases will continue to correct Liquid Glass, but I'm guessing iOS 27 is well down the path with it still integrated. Maybe iOS 28 will see sanity return???

▲

procaryote 3 hours ago | parent [-]

Second gen butterfly keyboard broke a lot too. And then there was the no-esc touch bar, and the removal of inverted-T arrow keys... It took a few years of no good mac laptops before they backpedalled enough to get back to where they started

	▲	zer0zzz 3 hours ago \| parent [-]
		I’m pretty sure butterfly keyboard was made worse when it came to the hotter rubbing higher power Mac’s. I rarely saw folks with the original 12” low power model having issues. It was not an entirely bad concept for the device it was conceived for, but Apple has a habit of unifying their technologies to all their products and sometimes, like with Liquid Glass, that seriously doesn’t work.

▲

derefr 4 hours ago | parent | prev | next [-]

> I also balk at how much extra computing power is needed to generate effects I find no value in and would prefer to disable.

I mean, "computing power" in a literal sense maybe, but does that matter if it doesn't translate to either "workload contention" or "electrical power"?

I think the Liquid Glass effects, similar to smooth scrolling, are mostly just running as pixel shaders on a spare tile of one of the SoC's GPU's Streaming Processors — a tile that likely likely would have been idle-but-burning-power-anyway, given that GPU power management occurs on the level of entire SPs. It's the same reason that ProMotion "smooth viewport scrolling" doesn't really cost anything.

▲

loloquwowndueo 3 hours ago | parent [-]

Workload contention. My iPhone 17 visibly struggles to render components with evident lagging - this is user-noticeable, if it were all done by an otherwise spare core I wouldn’t notice these things.

	▲	derefr 3 hours ago \| parent \| next [-]
		AFAICT, the steady-state Liquid Glass effects (think: the address bar in Safari, staying static itself while you scroll the page under it) cost nothing. That's what I meant above. Animating the Liquid Glass widgets (i.e. changing their position or shape), on the other hand, does seem to cost a lot / produce lag. I get the impression that this is down to the UI toolkit not being optimized for whatever Liquid Glass is doing in terms of recalculating constraints during animations. (When the GPU overruns its time budget while computing shaders for the compositor, the visual effect is of [double-buffered] texture buffers dropping/repeating frames, not slowdown. Actual "lag" in a GPU-composited UI is either from CPU work, or from one-shot CUDA-type GPU "prerender jobs".) I get the sense that Apple rushed out some shitty code that has some of these components re-evaluating a bunch of their placement and sizing constraints on every non-static animation frame (rather than just giving the Liquid Glass shaders the ability to do declarative tweens.) Or maybe the shaders already do declarative tweens, but Apple are doing tons of redundant on-CPU per-frame recalculations, to re-do any constraint-based layout for everything around the component during the animation, that might be impacted by the component's current tweened state. I dunno. Either way, it's definitely silly, and could be re-engineered to work a lot better. But it's also not really "Liquid Glass's fault" (i.e. something inherent to the visual design); it's just (AFAICT) bad implementation engineering, rushed to give Apple something to talk about besides its failure to launch Apple Intelligence.
	▲	astrange 2 hours ago \| parent \| prev \| next [-]
		It's a very complicated system. Performance issues are bad but they're not necessarily caused by how the UI looks. You can report an issue by typing applefeedback:// into Safari if you want.
	▲	procaryote 3 hours ago \| parent \| prev [-]
		And even if they reserved a core, that would be a waste of a perfectly good core

▲

rdtsc 3 hours ago | parent | prev [-]

> I also balk at how much extra computing power is needed to generate effects I find no value in and would prefer to disable

Sounds like you need to spend some money for a new Apple device! /s