SwiftUI
Ranked 4 of 45 GUI frameworks by recommenders
Apple's declarative UI framework; people praise its concise code and adaptive layouts, but critics agree documentation is weak and UIKit/AppKit fallbacks are often needed.
Apple's declarative UI framework; people praise its concise code and adaptive layouts, but critics agree documentation is weak and UIKit/AppKit fallbacks are often needed.
196 people gave an opinion
- recommend it
- 75
- criticize it
- 121
- approval share
- 38%
Recommended in 11 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Owned for 4 years
Median of the 8 owners who said how long they have had it.
Each square is one year.
Why it doesn’t carry the badge
- 75 people recommend itNeeds 10 or more, met.
- 0.6 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 11 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Less code, clean APIs
“The APIs seem well thought-out, I needed less code than I would have to do the same thing in React”
Comment from 3 Mar 2026 in “Claude is an Electron App because we've lost native” “for most things you can build so much with just SwiftUI and a few Apple frameworks”
Comment from 22 Jan 2026 in “2 years building a kids audio app as a solo dev – lessons learned” “SwiftUI is undeniably clean in a lot of ways, it presents beautifully and fits on slides well, but that matters less and less”
Comment from 2 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” Adapts across devices and screen sizes
“The abstraction is huge advantage, especially when targeting different devices and screen sizes.”
Comment from 11 Sep 2026 in “Shopify is moving from React Native back to Swift and Kotlin” “Cocoa and SwiftUI are more consistent in the sense that a lot of stuff automatically adapts when Apple changes styling”
Comment from 6 Apr 2026 in “Microsoft Hasn't Had a Coherent GUI Strategy Since Petzold” Good performance on recent iOS
“SwiftUI became "very good" as of iOS 26 (in part because the performance gap mostly evaporated)”
Comment from 2 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” “the most complete UI framework that is native, fast, performant and works very well”
Comment from 29 Dec 2025 in “Developing a Beautiful and Performant Block Editor in Qt C++ and QML” Used in many real apps
“There are hundreds of thousands of apps in the App Store that are 100% SwiftUI. They are real.”
Comment from 2 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” “In my current app, my views are 100% SwiftUI. One of them uses a SwiftUI List which typically has hundreds of thousands of items”
Comment from 17 May 2026 in “Native all the way, until you need text”
What people warn about
Each mark is one comment
Poor documentation
“There is poor documentation. The biggest trick — small views, think about what values are going to trigger a refresh.”
Comment from 2 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” “mostly because of the lack of documentation, and the gaps where you still need to drop down to AppKit/UIKit.”
Comment from 2 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” “AI makes up for SwiftUI's biggest weaknesses: Apple's wonky documentation and the need to know when to fall back to AppKit/UIKit.”
Comment from 2 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” - Comment from 20 Mar 2026 in “Be intentional about how AI changes your codebase”
Gaps requiring UIKit/AppKit fallback
“for complex and performance first, I will just use UIKit instead, it save a log of time”
Comment from 3 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” “It's not unusual to have to drop down to the UIKit version for some little thing that Apple couldn't be arsed to port over.”
Comment from 3 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” “mostly because of the lack of documentation, and the gaps where you still need to drop down to AppKit/UIKit.”
Comment from 2 Aug 2026 in “SwiftUI After 7 Years: A Story of Mediocrity” Performance and polish lag
“SwiftUI just not being fully-cooked and Apple trying to shove it into a bunch of areas without enough attention to performance”
Comment from 20 Apr 2026 in “Tim Cook to become Apple Executive Chairman” “it results in a lot of things just feeling janky, because one-size-fits-all rule and precise polish are fundamentally at odds”
Comment from 14 Jun 2026 in “Every Frame Perfect” “Apple has made a similar transition recently from the relatively efficient AppKit/UIKit to the bloated dog that is SwiftUI”
Comment from 6 Apr 2026 in “Microsoft Hasn't Had a Coherent GUI Strategy Since Petzold” - Comment from 17 May 2026 in “Native all the way, until you need text”
Works well only on newest OS
“Problem with SwiftUI is that it only works well on macOS 26, maybe one version prior.”
Comment from 3 Jan 2026 in “2026 will be my year of the Linux desktop” “Layouts will not magically be not dog shit on iOS because Apple put out another version of SwiftUI that you can't use in prod because nobody has the update.”
Comment from 10 Sep 2026 in “iPhone Duo” “Layouts will not magically be not dog shit on iOS because Apple put out another version of SwiftUI that you can't use in prod”
Comment from 10 Sep 2026 in “iPhone Duo”
Other GUI frameworks people recommend
The four most recommended other GUI frameworks, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Qt | 191 | 133 | 59% | 12 | 15 yrs7 owners | — |
| GTK | 85 | 118 | 42% | 12 | — | — |
| Windows Forms | 76 | 33 | 70% | 12 | 15 yrs3 owners | Approved |
| SwiftUIThis page | 75 | 121 | 38% | 11 | 4 yrs8 owners | — |
| Tcl/Tk | 61 | 21 | 74% | 12 | 15 yrs5 owners | Approved |
What people said
40 of the 295 comments that mention it, newest first. Each links to the original comment.
“The abstraction is huge advantage, especially when targeting different devices and screen sizes.”
“Layouts will not magically be not dog shit on iOS because Apple put out another version of SwiftUI that you can't use in prod”
“Layouts will not magically be not dog shit on iOS because Apple put out another version of SwiftUI that you can't use in prod because nobody has the update.”
“SwiftUI is at least the right idea for a UI framework, it's just been implemented horribly.”
“SwiftUI has a bunch of problems but almost none of them have anything to do with what this guy has to say”
“There are still a lot of rough edges when it comes to look and feel on Apple platforms”
“Toolbars are very inconsistent between platforms and the compiler timeouts are a real pain”
“SwiftUI has a lot of failings, but it can also do a lot of things that are really tricky in UIKit.”
“for complex and performance first, I will just use UIKit instead, it save a log of time”
“It's not unusual to have to drop down to the UIKit version for some little thing that Apple couldn't be arsed to port over.”
“SwiftUI became "very good" as of iOS 26 (in part because the performance gap mostly evaporated)”
“There is poor documentation. The biggest trick — small views, think about what values are going to trigger a refresh.”
“SwiftUI is undeniably clean in a lot of ways, it presents beautifully and fits on slides well, but that matters less and less”
“SwiftUI while nice in many ways tries to Reactify native macOS development and made it worse”
“There are hundreds of thousands of apps in the App Store that are 100% SwiftUI. They are real.”
“AI makes up for SwiftUI's biggest weaknesses: Apple's wonky documentation and the need to know when to fall back to AppKit/UIKit.”
“mostly because of the lack of documentation, and the gaps where you still need to drop down to AppKit/UIKit.”
“it's been surprisingly easy to animate things, I've spent way too long trying to synchronize the movement of different components”
“it results in a lot of things just feeling janky, because one-size-fits-all rule and precise polish are fundamentally at odds”
“In my current app, my views are 100% SwiftUI. One of them uses a SwiftUI List which typically has hundreds of thousands of items”
“It's great for test harnesses and admin dashboards, but the apps I make for general end-users are”
“iOS 26 is very late to have acceptable performance in the framework that Apple promotes as what you should use.”
“without deeper knowledge about SwiftUI, I find it a bit odd to expect so much from a novel concept”
“Actually knowing SwiftUI meant it was trivial for me to just close out that remaining 20% by hand”
“There's a lot of realy brilliant stuff in their system frameworks, and in SwiftUI, Cocoa, and UIKit.”
“SwiftUI just not being fully-cooked and Apple trying to shove it into a bunch of areas without enough attention to performance”
“Cocoa and SwiftUI are more consistent in the sense that a lot of stuff automatically adapts when Apple changes styling”
“Apple has made a similar transition recently from the relatively efficient AppKit/UIKit to the bloated dog that is SwiftUI”
“Apple would turn an LLM loose on the header docs for their SwiftUI codebase. It would drastically improve their docs”
“The APIs seem well thought-out, I needed less code than I would have to do the same thing in React”
“Maintaining three separate UI stacks (WinUI, SwiftUI, GTK/Qt) is dramatically more expensive and slower to iterate on”
“for most things you can build so much with just SwiftUI and a few Apple frameworks”
“Most of the mainstream UI frameworks are under licenses like that and for good reasons.”
“trying to shoehorn good interactivity into a SwiftUI component always ended in horrible code”
“Problem with SwiftUI is that it only works well on macOS 26, maybe one version prior.”
“where it makes sense; often on Apple platforms the imperative frameworks are better suited”
“declarative SwiftUI is used where it's a good fit, which gives you the benefits of both wherever they're needed”
“the most complete UI framework that is native, fast, performant and works very well”
“which is a lot of fun though it did have its share of "gotchas", especially in combo with SwiftData”
“I couldn’t get anywhere with serious Apple platforms development until SwiftUI came along.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.