Does anyone actually vibecode native iOS? Everything I read assumes React.

by•

Just finished an iPhone app — native Swift, Apple Watch target, voice logging through App Intents. Built most of it with AI tooling driven off markdown specs.

What struck me: almost every vibecoding post, tool demo and tutorial assumes a web stack. React, Next, Tailwind. The models are visibly better at it — more training data, instant feedback loop, errors you can read in a browser console.

Native iOS is a different experience. Xcode errors are worse to feed back in, SwiftUI changes enough between versions that the model confidently writes last year’s API, and there’s no quick way to show it what the screen actually looks like.

Still faster than writing it by hand, but the gap between “works for web” and “works for Swift” is wider than the tooling marketing suggests.

Anyone else building native with this workflow? What are you doing about the version-drift problem — pinning docs into the context, or just catching it in review every time?

14 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.