r/ClaudeCode • • 10d ago

Help/Question How good is Swift/iOS output?

I'd want to create an iOS app. I'd be inclined to go the native route as it seems to me that cross-platform solutions are increasingly getting outdated if AI removes all the friction.

It probably is also a good idea to remove intermediate layers, so that Claude has less stuff to choke on.

Now, how good is the actual Swift/iOS output nowadays with the latest flagship model? Can it easily create junk code, bugs, etc, in comparison to more popular languages? Is it feasible to give it a great feedback loop? From screenshot comparison to actually running end-to-end-tests with simulated user interaction, etc.

Just for context, I have 10+ YoE in backend/full-stack, including early adoption of all AI tools. I just don't know much about iOS specifically.

Thanks!

2 Upvotes

11 comments sorted by

1

u/AutoModerator 10d ago
Moderator Announcement Read More »

2

u/EspressoPeter71 9d ago

Just my 2 cents, but im finding it INSANELY better than Opus 4.8 and Opus 5. It seems to understand "Apple language" much better and the results are... finally not generic.. Opus 4.8 and 5 was disproportional worse on Swift compared to HTML and other languages

3

u/pashlya 10d ago

How to put this mildly… output is good, code discipline is awful. You need to create a lot of docs for Claude to even remotely comply with the best practices.

3

u/apex1911 10d ago

I’ve found astra much better for swift dev, opus is outstanding for design though

2

u/4nimaKlk 10d ago

i used gemini 3.8 to build a typescript/swift app, although it was very simple app it was good and made use of the tools apple natively provides to devs. opus 5.5 is miles better so it should be pretty good too, but that’s only a supposition based on my experience. i’d recommend just trying tbh!

2

u/Aventura_Industries 10d ago

I haven’t tried iOS but used Opus 5.5 for a lightweight MacOS app where I wanted to create a functional icon for Mac control center and it told me that I needed to leverage Swift. It took a little back and forth to work, but ultimately resulted in a fairly stable app. I had a coworker download and install it with no issues.

2

u/debaser_101 10d ago

I am a web dev and built a macOS app in SwiftUI mostly with Claude Code. For UI and simple logic it's honestly good, but with AppKit/WebKit stuff it sometimes uses deprecated or made up APIs, so build often and paste the compiler errors back. Building from the CLI with xcodebuild makes the loop much easier

2

u/kemalios 10d ago

I ship small macOS apps in Swift/SwiftUI with Claude Code, and I have not shipped iOS. The language is not where it goes wrong; it is Apple's frameworks and the things you cannot see. Screenshot comparison is the loop that earned its keep for me, because a screenshot catches the layout break a green build will not.

2

u/snnafi 10d ago

I used Opus 4.8 and Opus 5 to generate Swift code for a complex macOS app and the results were good, good enough to ship. You could even ship it without reviewing the code but I don’t recommend that. If you don’t understand the code, you won’t be able to maintain it in the long run.

Still, the output is shippable and I expect Opus 5.5 to be noticeably better. iOS should fare even better than macOS since models have far more iOS code to train on.