[0]: https://security.apple.com/blog/memory-integrity-enforcement...
I have called and opened tickets, and I keep hearing it'll be fixed real soon now.
Really wish Apple would get their software quality up from the gutter.
[1] https://www.macrumors.com/2025/12/18/macos-tahoe-studio-disp...
When I connect my laptop to a projector, I can select an individual window, or at least I used to be able to select a window and just project that. However, now when I try to select the window, as soon as the mouse cursor gets near the selection button, the button disappears!!! It has been driving me absolutely insane.
This sounds overly dramatic. You may not like the design but its 100% usable.
The flickering was so bad in my case that the pixels got stuck for some minutes when it happened.
Weird green tints for no reason.. bubbles that take so long to inflate, you think your tap was dropped. Round edges that no longer fit the text content. Stupid ellipses at the edges of wrapped text. And all the functions that now take two taps when one used to do it. Text rendered on top of text for crying out loud! Whole view panes clobberin* each other. WebKit is a mess of wasted black bars where menus were hidden. Multiple flashes of white and black between content changes. It hits Apple apps as well as trashing third party layout.
Too many defects to list.
Headline: Apple celebrates 50th anniversary by burning down 40 years of human interface knowledge.
But it's especially obvious when it dims itself based on ambient room brightness, I can actually see the vertical refresh happening as I move from a fully bright room to a dim one.
I suppose it’s not really working, or is the product of a team and no other internal team actually use it.
https://daringfireball.net/2025/11/software_update_tahoe_con...
My hope was that Apple would be forced to course correct in subsequent releases but that doesn't seem to be happening.
Now I have heard about issues on MacOS and things but not really anything around the phone.
Also the placement of buttons and functionality is completely scattered around the UIs, which severely reduces usability. What do all the mystery meat buttons do now? One has to relearn all the UX. There's a ton of improvement needed, it's about first-draft level quality.
Dark mode UI elements are almost invisible too, frequently.
It has a "my first redesign project" feel everywhere. On macOS I upgraded right away and it was a huge downgrade on performance. On iPhone I waited until 26.2, and merely had to suffer far lower usability.
On the Mac it’s much rougher than on iOS.
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.
Sounds like you need to spend some money for a new Apple device! /s
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.
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.
Wednesday February 11, 2026 10:51 am PST by Eric Slivka
Apple today released iOS 26.3, iPadOS 26.3, and macOS Tahoe 26.3, all of which largely focus on bug fixes and security improvements. Apple says that the updates address dozens of vulnerabilities, including one that is known to have been actively exploited.

That vulnerability in the dyld dynamic link editor could allow for the execution of arbitrary code, and Apple says the bug may have been exploited in an "extremely sophisticated attack" against targeted individuals on versions of iOS before iOS 26.
An attacker with memory write capability may be able to execute arbitrary code. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 26.
Apple says the memory corruption issue was fixed with improved state management.
There are numerous other vulnerabilities that were also fixed across not only iOS, iPadOS, and macOS, but also Apple's other platforms that saw updates released today.
Now that these vulnerabilities have been publicized by Apple, even those that were not exploited before might be taken advantage of now. Apple recommends all users update their devices to iOS 26.3, iPadOS 26.3, and macOS Tahoe 26.3 as soon as possible.
Saturday February 7, 2026 9:26 am PST by Joe Rossignol
Apple today shared an ad that shows how the upgraded Center Stage front camera on the latest iPhones improves the process of taking a group selfie. "Watch how the new front facing camera on iPhone 17 Pro takes group selfies that automatically expand and rotate as more people come into frame," says Apple. While the ad is focused on the iPhone 17 Pro and iPhone 17 Pro Max, the regular iPhone...
In select U.S. states, residents can add their driver's license or state ID to the Apple Wallet app on the iPhone and Apple Watch, and then use it to display proof of identity or age at select airports and businesses, and in select apps. The feature is currently available in 13 U.S. states and Puerto Rico, and it is expected to launch in at least seven more in the future. To set up the...
Tuesday February 10, 2026 6:33 am PST by Joe Rossignol
It has been a slow start to 2026 for Apple product launches, with only a new AirTag and a special Apple Watch band released so far. We are still waiting for MacBook Pro models with M5 Pro and M5 Max chips, the iPhone 17e, a lower-cost MacBook with an iPhone chip, long-rumored updates to the Apple TV and HomePod mini, and much more. Apple is expected to release/update the following products...
Tuesday February 10, 2026 4:27 pm PST by Juli Clover
Apple is planning to launch new MacBook Pro models as soon as early March, but if you can, this is one generation you should skip because there's something much better in the works. We're waiting on 14-inch and 16-inch MacBook Pro models with M5 Pro and M5 Max chips, with few changes other than the processor upgrade. There won't be any tweaks to the design or the display, but later this...
New MacBook Pro models with the M5 Pro and M5 Max chips could arrive as soon as Monday, March 2, according to Bloomberg's Mark Gurman. In today's "Power On" newsletter, Gurman said that the release of new MacBook Pro models is tied to the release of macOS Tahoe 26.3. The launch is said to be slated for as early as the week of March 2. He added that the M4 Pro and M4 Max models on sale today...
Personally I prefer the new behaviour.
But eitherways: it’s just an option.
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???
You can report an issue by typing applefeedback:// into Safari if you want.
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.
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.