From Claude Code Project to Apple App Store

Claude Code is a coding agent that works in your repository: it reads files, edits code, runs commands and can iterate on test failures. It can produce a surprising amount of a working app. Publishing is a different kind of task, because it touches accounts, signing identities, legal text and a human review process at Apple. This guide separates what the agent does well from what a person must own.

First question: what did the agent build?

The route to the App Store depends on the project type:

• Native Swift/SwiftUI project: already has an Xcode target; focus is on signing, testing and review.
• React Native or Expo project: needs a native build pipeline, usually through Xcode or a cloud build service.
• Flutter project: similar, with its own build tooling.
• Web app: needs a native wrapper plus native features; see our website-to-app overview.

Review before you ship

An agent-written codebase can look tidy and still hide problems: hard-coded API keys, unvalidated inputs, unhandled offline states, or logic that works only in the happy path. Before building a release candidate, do a human review of the diff, scan for secrets, check dependency choices and run the test suite. Our guide on security review for AI-generated code lists what we look at.

Getting the iOS build ready

1. Bundle identifier and capabilities: match what you register in the Apple Developer portal, including push notifications or sign-in if used.
2. Signing: distribution certificate and provisioning profile, or automatic signing managed carefully.
3. Privacy manifest and permission strings: every requested permission needs a clear usage description.
4. Archive and upload: build in Release configuration and upload to App Store Connect.
5. TestFlight: test on physical devices across iOS versions you support.

Agents are helpful for editing project files and fixing build errors, but they cannot own the Apple account or see the physical device in your hand.

Common review blockers

• Crashes or blank screens on launch in the reviewer's environment.
• Placeholder content, broken links or features that are announced but not implemented.
• Missing account deletion or missing demo credentials.
• Privacy answers that do not match the actual SDKs and network calls.
• Thin functionality under Guideline 4.2; see our 4.2 guide.

Check Apple's current guidelines before every submission, because they change.

A word on agent instructions

Coding agents follow the instructions in your repository. A clear project file that states build commands, code style, forbidden shortcuts and the release checklist makes the agent's output far more predictable. We cover how to write such files in our guide on AGENTS.md and CLAUDE.md. For release work, include rules such as never committing secrets, never changing signing settings without review and always running the test suite before proposing a build.

Test like a user, not like a developer

Install the TestFlight build on a phone that has never seen your development environment. Create a fresh account, break the network, rotate the screen, deny permissions and put the app in the background for an hour. These checks find problems that automated tests rarely catch, and they are exactly the checks a reviewer might stumble into by accident.

How apprat.io fits in

The Claude Code-to-App module is designed for exactly this handover. We use coding agents, including Claude Code, for much of the implementation, but a senior AI Code Engineer plans the work, reviews every change, tests on real devices and submits to the App Store. If your project is already built, we can audit it first; see our development service or book a call for free. Our ISO 9001 and ISO 27001 certified processes cover how changes are reviewed and documented.

One more practical point is versioning. App Store Connect expects each uploaded build to have a unique build number, and a marketing version that makes sense to users. Agree on a simple scheme, for example incrementing the build number automatically in your build pipeline, so that nobody has to guess which build is in review and which is live.

Do not forget the account

An Apple Developer account for a company needs identity verification, and that can take longer than the code. Read our account setup guide early. On Android, the equivalent is covered in From Claude Code project to Google Play.