SwiftUI’s promise still ends at the UIKit boundary
Seven years after its debut, SwiftUI remains productive for many screens and frustrating precisely where an app stops being a demo.
A retrospective on SwiftUI argues that declarative syntax did not erase the need to drop into UIKit or AppKit. The HN thread added a more practical split: solo developers praise the speed, while complex applications expose the framework’s seams.
The declarative surface is not the whole platform
SwiftUI After 7 Years reviews Apple’s UI framework through the gap between its attractive first experience and the work required when platform APIs, documentation, or edge cases intervene. The criticism is about completeness, not whether declarative UI can be pleasant.
Developers recognize the same boundary
The HN discussion brought out both sides. Some developers said SwiftUI plus its surrounding tools is their best environment; others described the recurring need to fall back to older frameworks. For teams choosing a UI stack, the relevant test is not the simplest screen but the first unsupported capability they cannot postpone.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
eBay’s harassment case ends with a $56M payout
The settlement brings a corporate-security scandal back into view: the people tasked with protection were convicted of targeting critics.