> I think a big part of this in recent years is SwiftUI just not being fully-cooked and Apple trying to shove it into a bunch of areas without enough attention

> I think a big part of this in recent years is SwiftUI just not being fully-cooked and Apple trying to shove it into a bunch of areas without enough attention to performance. FWIW, SwiftUI got a huge performance boost for iOS/macOS 26+, and Instruments 26 has been nice for finding performance bottlenecks. You may find the SwiftUI performance auditor in a free/FOSS project of mine (https://charleswiltgen.github.io/Axiom/commands/ui-design/audit-swiftui-performance https://charleswiltgen.github.io/Axiom/commands/ui-design/au...) helpful as well. Why it took 4 years to get to near-UIKit levels of performance I couldnt say, but I've had a great experience working with it on an app that's 97% SwiftUI.