Anecdotes from a Liquid Glass workshop with Apple teams & dev relations:

• Liquid Glass is not gonna be rolled back, Apple loves it, and thinks y'all are crazy
• << those who don’t adopt it now “are gonna find themselves in a tough position later.”>>
• "Xcode 27 will absolutely not have the [UIDesignRequiresCompatibility] flag, and it will not respect it if you leave it there"

The source blog reeks of LLM-speak, but I think that's just the writer's choice

https://captainswiftui.substack.com/p/talking-liquid-glass-with-apple

Talking Liquid Glass with Apple

I spent three days talking Liquid Glass with Apple in NYC. Here’s what you need to know.

Captain SwiftUI
@stroughtonsmith You mean UIBoycottLiquidGlass? I bet a lot of these devs put that key in hoping to never update to it

@stroughtonsmith “are gonna find themselves in a tough position later.”

Is such mafioso rhetoric.

@stroughtonsmith It makes sense that Apple isn't going to 180 on Liquid Glass after one year, but if the reaction is truly "genuine shock" that people don't like it… that's an extremely bad sign. I have to assume this person is poorly relating PR-isms, not that Apple is so insular and thick to be unaware of the outside world. Right?
@gavinanderegg @stroughtonsmith I had the same reaction to that. I find it hard to believe that they are so insular that they are completely unaware of the negative reception Liquid Glass has received amongst developers and people who care about UI.
@stroughtonsmith This claim is very weird: "The List vs. ScrollView Reality Check - Many of us have been defaulting to List the second we need a scrolling column of data. The team made a point to clarify that List should really be reserved for highly specific, uniform data structures, or when you absolutely need built-in swipe actions. For almost everything else? You should be reaching for a ScrollView paired with a LazyVStack or LazyHStack."
#SwiftUI
@stroughtonsmith The two main reasons to use List's are:
a) reusable rows
b) row actions
[c) standard editing behaviours]
It's more like you _have to_ reach for ScrollView, because SwiftUI List is still weirdly b0rked after all those years.

@helge SwiftUI is semantic, except when it's not. Use the view that best describes your purpose, except when it's broken for years with no explanation. So easy to learn about things like this, not by reading the API docs or watching videos - no, the information doesn't exist in these places - only by visiting an in-person event in New York.

Time to rip out all the Lists from my app, I guess. I knew there were problems, but I didn't know what I was doing wrong, and there was no way to find out.

@stroughtonsmith rolled back, perhaps not, but it is being severely audited and redressed.

https://twipped.social/@twipped/116129736158640867

Jocelynephiliac :reclaimer: (@[email protected])

> The keys to the iPhone’s soul have now been handed to Stephen Lemay, a 26-year veteran of the original Aqua design era. Lemay’s mission for iOS 27 is reportedly a “Snow Leopard” style intervention—a radical “taming” of the interface [...] reintroducing high-contrast borders and “Physical Depth” to ensure the eye never has to “hunt” for a button. Oh thank the gods, Lemay is bringing back button bevels. https://webdesignerdepot.com/how-liquid-design-broke-the-iphone-and-forced-apples-great-reset/

Twipped Social (Private)
@twipped @stroughtonsmith I’m actually more positive towards them trying to make something good out of it anyway. I never liked flat design, and trying to hve depth in UIs is *good*, they just didn’t execute right. In particular: they need to remember there are more materials than glass and add back colour too. (In addition to fixing contrast, etc).