Why would that be your conclusion? If you were to slap any UI framework elements together without a design in mind, especially for a form, they'd look like that.
This is just the author putting together the elements and discussing them. They're not trying to design something.
There's tons of SwiftUI apps out there that are gorgeous looking. As with any UI framework, it's up to the developers who use them to make pretty or not.
It's an academic exercise app. Those always look fairly primitive.
I'm pretty sure that some of the new versions of the Apple standard apps are in SwiftUI. They may be a better example.
Polish takes a great deal of effort, and often detracts from the lesson.
Having done a number of things like this, I can attest to how much work it is, and appreciate the effort.
All that said, I am still not entirely comfortable with committing to SwiftUI for a major app development project. I'm in no hurry. AAA apps are still using ObjC codebases, so there's no real urgency.
The defaults being inconsistent and ugly is a failure of the component system. Like, why does the date field
s month (6) have a space in the middle, and the up/down arrows are different from the select box’s up/down arrows ? And squared corners instead of round ones ?
It might be from the options the author is setting, but I’m not sure why it would end up that way.
The date picker is the only thing I see as wrong with the components displayed here.
And, from the perspective of a developer, I don't think it's a big deal.
This date-picker design is used consistently across the system.
So I assume someone at Apple will eventually get a 16 man-hour ticket to fix it system-wide, including third party apps.
All the things that don’t look nearly or exactly identical to Catalina-era Cocoa (i.e. the “switch” toggles, “grouped” sub-form, oversized “capsule” button) are explicitly declared in the source code[1]. I’d wager those toggles will become more common as they get more first-party usage, grouped sub-forms probably less so. Huge oversized buttons? Pretty unlikely.
So, you scrolled the article just to attack a random screenshot out of context?
Open up Xcode and drag various AppKit/UIKit's components onto the screen. Now ask yourself if this is the future of iOS/macOS apps just because you were able to cobble it together out of curiosity.
Not sure why you are getting downvoted. There are so many basic fundamental things wrong there...
A UI framework should at least get some of the very basic things correct with out of the box defaults. Bootstrap, for example, largely gets this right. You can slap something together and it at least looks vaguely cohesive. The screenshot you posted, should have taken somebody a lot of effort to demonstrate how a UI should NOT look. It's a visual version of a new HTML form framework where the labels aren't clickable...
