RC RANDOM CHAOS

SwiftUI at 7: Still a Perpetual Beta, and a Symptom of Apple's Decline

· via Hacker News

Original source

SwiftUI After 7 Years

Hacker News →

A senior Apple-platform engineer argues that SwiftUI, launched with fanfare in 2019 as the declarative, cross-platform future of Apple UI development, has failed to mature into a production-grade framework. Seven years on, the piece contends, the ‘still young’ excuse no longer holds: layout remains unpredictable, performance trails UIKit, and even Apple’s own first-party tutorial project (Landmarks) ships visibly broken on current Xcode and macOS. The author’s core complaints are structural — a churning data-flow model that lurched from @State/@Binding/ObservedObject to the newer Observation framework and @Observable macro without ever making view updates predictable, and a size-negotiation layout engine so fragile that developers fall back to GeometryReader and manual coordinate math, forfeiting the declarative benefits they were promised. Constant API churn forces codebases full of if #available shims and workarounds.

The more interesting thread is the business motive. The author frames SwiftUI less as a gift to developers than a defensive move: with React Native and Flutter making cross-platform, web-derived codebases attractive, Apple needed to keep developers inside the native ecosystem — and revive a neglected Mac App Store dominated by Electron wrappers — to protect its lucrative services and App Store fee business. Native lock-in, not developer happiness, is the read on why SwiftUI exists.

Zooming out, the critique is really about culture. It reads SwiftUI as evidence of a shift at Apple away from the exacting craftsmanship of the Cocoa, Aqua, and Auto Layout era toward a ‘good enough’ corporate mindset, where shipping convenient-looking abstractions matters more than engineering rigor — and where developers end up doing Apple’s QA for free. For engineering leaders weighing native SwiftUI against cross-platform alternatives, the takeaway is a pointed reminder that framework maturity and vendor incentives, not marketing, should drive the bet.

Read the full article

Continue reading at Hacker News →

This is an AI-generated summary. Read the original for the full story.