# Can you submit an app built with Claude Code to the App Store?

Canonical page: https://acceptmy.app/guides/submitting-a-claude-code-app-to-the-app-store

Yes. Apple's review guidelines don't ask how an app was written, and there's no rule against AI-assisted development. What actually determines approval is the same thing it's always been: does the finished app meet the guidelines. Here's what that means in practice for something built largely by Claude Code.

## Apple doesn't review your tooling, it reviews your app

There is no guideline that flags or penalizes AI-assisted or AI-generated code specifically. App Review evaluates the submitted binary and metadata against the same guidelines regardless of whether a human typed every line or an agent wrote most of it.

Where AI-assisted apps do run into trouble is indirect: Claude Code (like any fast code generator) makes it easy to ship a working app before you've thought about privacy, account deletion, or depth of functionality — the things reviewers actually check.

## What to verify before you submit, specifically for a Claude Code build

Check what auth and backend scaffolding Claude Code set up by default — many generated stacks include account creation without a matching account deletion flow, which is a guaranteed rejection if left as-is.

Check for hardcoded secrets. Agentic coding sessions sometimes inline an API key or service credential directly into client code to get something working quickly; confirm nothing sensitive shipped in the binary.

Check the generated Info.plist and any permission usage strings — generated placeholder text like "This app needs access to your camera" reads as vague to a reviewer and is worth rewriting to state the specific, real reason.

## The real risk: functionality depth, not authorship

Guideline 4.2 (Minimum Functionality) and 4.2.6 (Commercial templates and app generators) are where AI-built apps most often get flagged — not because Claude Code was involved, but because a fast build-out session tends to produce a single clear flow without the saved state, personalization, or native integration that separates a real product from a demo.

Before submitting, ask honestly: does this app do something meaningfully useful beyond what the first working version did? If Claude Code got you to a working prototype fast, that's the right moment to spend real time on depth, not to submit immediately.

## Ownership and originality

Make sure any generated branding, icon, or UI style is actually yours to use — Claude Code can generate placeholder assets quickly, and it's worth swapping anything that looks like a stock template before it reads as generic or, worse, resembles an existing app closely enough to trigger a copycat concern.

You're responsible for the submitted app regardless of how it was built — App Store Connect agreements and content ownership requirements apply the same way they always have.

## Before you submit

Run through a real pre-submission pass: privacy manifest present, account deletion works, permission strings are specific, screenshots match the shipped build, and the app offers more than a single shallow action.

None of this is about proving the app was "hand-coded" — it's the same bar every iOS submission has to clear, AI-assisted or not.


## Related pages
- [From prompt to App Store: the submission process for vibe-coded iOS apps](https://acceptmy.app/guides/vibe-coded-ios-app-submission-process.md)
- [The App Store checklist built for AI-generated apps specifically](https://acceptmy.app/guides/vibe-coding-app-store-checklist.md)
- [iOS Privacy Manifest Validator](https://acceptmy.app/free-tools/privacy-manifest-validator.md)

Last updated: 2026-09-09