SwiftUI After 7 Years: A Story of Mediocrity
Seven years post-launch, SwiftUI is lambasted as a "perpetual beta" framework, plagued by performance woes, unpredictable layouts, and API instability that force developers into constant workarounds. The author argues that initial promises of declarative simplicity have dissolved into deep professional frustration, signifying a worrying "good enough" philosophical shift at Apple. This critical analysis resonates deeply with developers grappling with the realities of building robust applications on Apple's flagship UI toolkit.
The Lowdown
This story presents a scathing critique of Apple's SwiftUI framework, arguing that despite seven years of development, it remains a mediocre, production-unready tool that has failed to live up to its initial hype. The author, Yakov Manshin, details systemic issues that lead to persistent developer frustration and concludes that SwiftUI embodies a concerning decline in Apple's software quality.
- Persistent Beta State: SwiftUI, announced with great fanfare in 2019, is described as feeling like a perpetual beta, with new features often breaking existing functionality and requiring extensive workarounds.
- Problematic Data Flow: The declared "single source of truth" has devolved into a confusing maze of property wrappers and macros, making predictable view updates nearly impossible and often leading to black-box reactivity.
- Unpredictable Layout System: The layout engine is criticized for its fragility and inconsistency, forcing developers to resort to
GeometryReader, which negates the benefits of declarative UI and adds complexity. - API Instability & Feature Parity Gaps: Developers are burdened with frequent API changes and a lack of basic functionalities (like keyboard dismissal on scroll or robust image caching) that have long existed in older frameworks, necessitating extensive
if #availablechecks and multiple implementations. - Subpar Performance: Despite Apple's promises, SwiftUI's performance is consistently inadequate, often requiring obscure optimizations to achieve acceptable fluidity, even on modern hardware.
- "Cross-Platform" Myth: The "learn once, apply anywhere" promise is debunked, with the author highlighting significant inconsistencies and adaptation required for different Apple platforms, leading to UIs that feel alien.
- Philosophical Shift: Manshin attributes SwiftUI's shortcomings to a broader, concerning shift in Apple's corporate culture towards a "good enough" mentality, where velocity trumps uncompromising craftsmanship, leading to widespread quality issues even in first-party apps.
Ultimately, the author asserts that SwiftUI's story is one of mediocrity and lowered standards, forcing engineers to choose between debugging an unstable framework or shipping broken apps. This reflects a fundamental decline in Apple's commitment to quality that the author refuses to accept.