★ SwiftUI Only Makes It Easy to Develop Bad Apps · Daring Fireball
Science, Technology & Innovation · Jun 8, 2026
Paulo Andrade’s macOS port of the iOS app Shopie shows that a 100% SwiftUI approach—chosen to maximize cross-platform code reuse—hits structural limits and “framework friction” that prevent achieving native Mac behavior, implying pure SwiftUI can force tradeoffs away from expected desktop quality unless AppKit/UIKit is integrated.
★ SwiftUI Only Makes It Easy to Develop Bad Apps · Daring Fireball
Science, Technology & Innovation · Jun 8, 2026
Seven years after launch, SwiftUI still falls short of Apple’s promise to make building idiomatic, complex native apps easy—missing built-in behaviors like Undo/Redo—so teams should expect ongoing hidden costs for native fidelity, QA, and framework workarounds rather than assuming annual platform updates will fix it.
★ SwiftUI Only Makes It Easy to Develop Bad Apps · Daring Fireball
Science, Technology & Innovation · Jun 8, 2026
On macOS 26 (Tahoe) in Apple Journal, a SwiftUI text-editing bug breaks Undo/Redo — deleting the word “brown” from “The quick brown fox” then Undo removes the entire sentence and Redo returns “The quick fox,” demonstrating lost text and that SwiftUI can regress AppKit-era undo behavior, meaning text/document workflows need extra scrutiny or fallback to mature components.
★ SwiftUI Only Makes It Easy to Develop Bad Apps · Daring Fireball
Science, Technology & Innovation · Jun 8, 2026
The article argues Apple picked the wrong technical sequencing—letting AppKit fossilize and leapfrogging to SwiftUI—so SwiftUI is pleasant for simple apps but fights established Mac interaction models when building high-quality Mac apps, raising the likelihood of persistent quality gaps, longer development cycles, and fallback to AppKit/UIKit bridges rather than full convergence.