How to Publish Your Claude Code App to the App Store and Google Play
Built an app with Claude Code? Here's how to publish it on the App Store and Google Play — what to change, what to avoid, and how long it takes.
Inside this article
Why Claude Code Apps Aren't App-Store-Ready Out of the Box
Claude Code can build a working, deployed web app in minutes. The problem is that the App Store doesn't accept web apps — it accepts native binaries. Your Claude Code project runs at a URL. Apple wants an IPA file. Google wants an AAB file.
That gap is bridgeable, and thousands of developers cross it every month. The solution is a WebView wrapper: a thin native shell that loads your web app's URL inside a real iOS or Android container. The binary is native; the content is your existing Claude Code project. You don't rewrite anything.
What Makes Claude Code Apps Strong WebView Candidates
Claude Code typically produces React, Next.js, or similar web-app output, deployed to a public URL. That URL-based architecture is exactly what a WebView wrapper needs. Your app already renders in a mobile browser — wrapping it for the App Store is the logical next step, not a rebuild.
Before you wrap, verify two things on a real phone:
Custom domain. Your app must load from a custom domain — something like myapp.com, not a generic hosting subdomain like myapp.vercel.app or username.github.io. Apple's Guideline 4.2 (Minimum Functionality) requires this. Without a custom domain, reviewers classify the app as a thin web wrapper and reject it. A custom domain costs around $10–15/year and takes about 10 minutes to configure in Vercel, Netlify, or wherever your Claude Code app is deployed.
Mobile-responsive layout. Claude Code apps usually look good on mobile, but check on an actual device. If any screen requires horizontal scrolling, or if buttons are too small to tap, fix those before submitting. App Store reviewers test on real iPhones, and layout issues are a common rejection trigger.
From Claude Code to Live App: The Three Steps
Step 1 — Package your app as a native binary
A WebView wrapper takes your deployed URL and outputs a native app binary. You configure the app name, icon, splash screen, bundle ID, and permissions — the wrapper handles everything at the native layer.
The packaging step produces:
- An
.ipafile for the App Store (iOS) - An
.aabfile for Google Play (Android)
You don't need to install Xcode or Android Studio to generate these files. If you've published a vibe-coded app before — with tools like Cursor or Replit — the packaging process is nearly identical. Managed services like Webvify handle this step end-to-end and deliver submission-ready files.
Step 2 — Create your developer accounts
Publishing on both stores requires two accounts:
Apple Developer Program — $99/year. Required to submit anything to the App Store. Account approval takes 24–48 hours for most applicants. The account must be registered to an individual or a business entity, not a generic iCloud address.
Google Play Developer account — $25 one-time fee. Access typically comes within a few hours. Google Play also requires a closed testing phase with 12 real testers for at least 14 days before you can publish publicly.
Set these up in parallel while you're packaging the app so you're not waiting on account approvals after the binary is ready.
Step 3 — Submit and get reviewed
Apple's review takes 1–3 business days for first-time submissions. Google Play is often faster — a few hours to a couple of days for straightforward apps.
The review checks whether your app functions as described, meets content guidelines, and follows store policies. Most Claude Code apps pass without issues. There are two policies worth knowing before you submit, because they catch developers off guard.
Two Rules That Catch Claude Code Apps Off Guard
Apple's In-App Purchase Rule (Guideline 3.1.1)
If your Claude Code app lets users purchase digital goods inside the app — subscriptions, credits, courses, memberships, digital downloads — Apple requires those transactions to go through Apple's in-app purchase system on iOS. Stripe and other payment processors are not permitted for digital content inside an iOS WebView.
The fix is a redirect: when a user taps a purchase button, open Safari instead of completing the transaction inside the app. This is how Udemy, Coursera, and thousands of subscription apps handle it. Physical goods, in-person services, and restaurant ordering are not affected by this rule — only digital-only transactions.
If your Claude Code app doesn't collect payment inside the app at all, this rule doesn't apply to you.
Minimum Functionality (Guideline 4.2)
Apple rejects apps that appear to be "essentially just a website." Your app needs at least one feature that a browser doesn't provide. Push notifications are the most practical way to satisfy this — and they're also the highest-ROI feature you can add after launch.
A push notification that reaches a user's lock screen converts at 60–90%, compared to 20–30% for email. Adding push capability to a WebView wrapper doesn't require any changes to your Claude Code codebase; the native layer handles registration and delivery.
For a complete list of what triggers rejection and how to avoid each one, this App Store rejection prevention guide covers the full checklist.
Timeline: Claude Code App to Live in Both Stores
Here's a realistic schedule for a Claude Code app that's already deployed to a custom domain:
Day 1: Configure the WebView wrapper, set up developer accounts, generate the native binaries.
Days 2–3: Apple Developer account approval (if new). Submit to Apple once approved.
Days 4–6: Apple review completes (1–3 business days). Google Play review often comes through faster, sometimes on the same day as submission.
Most developers have their Claude Code app live on both stores within a week of starting this process. If you use a managed service for packaging and submission, the active work on your end is under a day.
FAQ
Do I need to modify my Claude Code app to publish it on the App Store?
Usually not. If your app is deployed to a custom domain and is mobile-responsive, it wraps cleanly as-is. The one common change is routing digital purchase flows through Safari instead of completing them inside the app — this only applies if your app sells digital goods directly to users.
Can I publish my Claude Code app on both iOS and Android at the same time?
Yes. A WebView wrapper generates an iOS IPA and an Android AAB from the same underlying web app. You submit them to Apple and Google separately — different accounts, different portals — but the app content is the same. Most developers go live on both platforms within the same week.
What happens to my app when I update the Claude Code project?
Because the app loads your deployed URL, any update you push to your Claude Code project is reflected in the app immediately — no new App Store submission required. The native binary only needs resubmission if you change app-level settings: the app name, icon, permissions, or App Store listing details.
Your Claude Code project is closer to an App Store app than you think. Webvify handles the full process — wrapping, building, submission to both stores, and the admin panel to manage it afterward.