Comment by ben-gy
2 days ago
I second this article - I built twelve iOS/Mac apps in two weeks with Opus 4.5 - four of them are already in the App Store - I’m a Rails Engineer and never had the time to learn Swift but man does Opus 4.5 make that not even matter - it even handles entitlements, logo & splash screen generation, refactors to remove dead code, edge case assent and hardening, Multiplatform app design, and more - I’m yet to run into a use case it can’t handle for most general use cases - that said, I have found some common mistakes it makes (by common I mean almost every time); puts iOS line list line items in buttons making them blue when they should not be, doesn’t set defaults for new data structure variables which crashes the app when changing the data structure after the fact, design consistent after the first shot (minor things like white background instead of grey background like all the other screens already, etc) - the one thing that i know it cant do well (and no other model that I know of can do this well either) is ASTM bi-directional communications (we work with pathology analysers that use this 1995 frame-based communication standard), even when you load it up with the spec and supporting docs - I suspect this is due to a dirty of available codebases that tackle this problem due to its niche and generally proprietary nature…
Are there a lot of manual steps in managing an xcode project? E.g. does it say "now go into xcode and change this setting" instead of changing the setting directly? Or are you using a tool like xcodegen?
Very few - the only manual things I do are; - clicking the distribute button to push the bundle to the App Store - filling in the compliance survey and App Store listing content - linking some components together e.g. for creating a VPN installer and tunnel i had to click some things in the Xcode UI I automate as much as possible; -“create 12 app icons for this in SVG and present them to me in a HTML page so I can choose one and then use that for the app icon and splash screen” - “create a demo mode toggle in settings and populate the app with fake data and then open up simulators for the correct image dimensions for the App Store listing so I can crate screenshots” - sometimes it tell me I have to other things like set up the entitlements to which is say “no - you do it and don’t forget to fill in the description that gets shown to the user so the feature actually works” I knew very little about Swift or Xcode profile to this and TBH I still don’t know that much about it, but I’m experienced enough to know when I’m being fed something that doesn’t look or feel right programmatically or architecturally.
Can you please share the links to these apps in the app store?
https://apps.apple.com/au/app/events-canberra/id6756598656 - you can access the other ones by clicking the developer name in the listing
how did you use Opus to build the apps? I tried using Claude Code ~6 months ago to build an iOS app and I was not that impressed with the results, especially compared to this blog post, where the apps look polished and very professional.
My biggest issue was limitations around how Claude Code could change Xcode settings and verify design elements in the simulator.
Opus 4.5 got released ~3 months ago - Claude Code started using it automatically (for me anyway) - I also tried iOS prior to that and had a similar experience to you
what claude plan are u on?
Max