Skip to main content

Publishing a Claude Code App on Google Play

By the OnlineAppCreator editorial team4 min read

Short answer

To publish a Claude Code app on Google Play you need a Play Console developer account (one-time USD 25 fee), a release-signed Android App Bundle that targets a recent Android API level, a completed store listing, content rating and Data safety form, and, for new personal accounts, a closed test with at least 12 testers over 14 days before production access is granted.

On this page
  1. Choose the account type before you write a line of release code
  2. What Claude Code should prepare in the repository
  3. Signing without giving the agent your keys
  4. From first upload to production
  5. The Data safety form is a code question
  6. Typical rejection and policy issues
  7. Getting help with the store side

Google Play is often the easier store for an agent-built app: Android builds run on Linux, so Claude Code can produce a release bundle in the same environment where it writes the code, and the review is less focused on how native an app feels. The friction sits elsewhere. Account verification, the closed testing requirement for new personal accounts and the Data safety form trip up more teams than the code itself. This article walks through the full path and shows which parts to hand to the agent.

Choose the account type before you write a line of release code

The Play Console offers personal and organization developer accounts. Registration currently costs a one-time USD 25. Organization accounts require a D-U-N-S number and verification of the organization, which takes time but signals a business behind the app. Personal accounts created recently are subject to a testing requirement: currently, before you can publish to production, you must run a closed test with at least 12 testers who stay opted in for at least 14 continuous days. Organization accounts are not subject to this rule at the time of writing. Check the current Play Console Help before you plan your launch date, because this policy has changed before and our article on the Google Play closed testing requirement tracks the details.

What Claude Code should prepare in the repository

Whatever framework the agent used, Google Play expects an Android App Bundle (.aab), not an APK, for new apps. Ask Claude Code to verify these points in the Gradle configuration and the manifest:

  • A unique, final applicationId. It cannot change after the first upload.
  • versionCode as an integer that increases with every upload, and a readable versionName.
  • targetSdkVersion that meets Google's current target API level requirement, which moves up roughly once a year.
  • Only the permissions the app really uses. Each sensitive permission, such as location in the background or SMS, triggers additional declarations in the Console.
  • Code shrinking and obfuscation rules that do not break reflection-based libraries, tested on a release build rather than a debug build.

If the Claude Code project is a web app rather than an Android project, a native shell such as WebViewGold provides the Android project, push notifications and file uploads, and you configure it to point at your web app.

Signing without giving the agent your keys

New apps use Play App Signing: Google holds the app signing key, and you sign uploads with a separate upload key. Generate the upload keystore yourself, store it outside the repository and inject the passwords through environment variables or a CI secret store. Claude Code can write the signingConfigs block that reads those variables, but it should never have the keystore or the passwords committed or pasted into the conversation. If an upload key is lost, it can be reset through Play Console support; a leaked key is a harder problem. More on this split in our guide to code signing and certificates for AI-built apps.

From first upload to production

  1. Create the app in the Play Console with name, default language, app or game, and free or paid. Free apps cannot later be switched to paid.
  2. Complete the App content section: privacy policy URL, ads declaration, app access (with test credentials if there is a login), content rating questionnaire, target audience, and the Data safety form.
  3. Upload the first bundle to internal testing. It becomes available to up to 100 internal testers quickly and validates signing, versioning and the manifest.
  4. Run the closed test if your account requires it, with at least 12 opted-in testers for 14 days, and collect feedback.
  5. Apply for production access where required, answering Google's questions about your testing.
  6. Release to production with a staged rollout, for example to a small percentage of users first, and increase it as crash rates stay low.

The Data safety form is a code question

The Data safety form asks what data the app collects, whether it is shared, whether it is encrypted in transit and whether users can request deletion. The honest answer depends on the code and on every SDK in it, which is exactly where Claude Code is useful. Ask it to produce an inventory: every network call, every analytics or crash reporting library, every permission and every field sent to your backend. Map that inventory to the form's categories, then have a human confirm it. Google compares declarations with app behavior, and a mismatch can lead to a rejection or a policy warning. If users can create an account, Google also requires a way to request account deletion, both inside the app and through a web link.

Typical rejection and policy issues

Agent-built Android apps tend to fail on a few predictable points: a crash on an Android version the agent never tested, login screens without test credentials in App access, broken links to the privacy policy, or permissions that the app requests but never explains. Run the release bundle on at least one older and one current Android device or emulator before submission, and use the pre-launch report in the Play Console, which runs your app on test devices automatically.

Getting help with the store side

If you want the build handled by your team but the store process handled by specialists, AppSubmitter.io supports the full Google Play publishing process, including account setup, the closed testing phase, listings, the Data safety form and responses to policy issues, until the app is live. For the iOS half of the same project, read from Claude Code project to the Apple App Store.

Frequently asked questions

Can Claude Code build the Android App Bundle itself?

Yes. Android builds run on Linux, macOS and Windows, so the agent can run the Gradle bundleRelease task. Keep the upload keystore and its passwords outside the agent's reach and inject them at build time.

Do I really need 12 testers for 14 days?

Currently yes for new personal developer accounts before production access. Organization accounts are not subject to this requirement at the time of writing. Check the current Play Console policy before planning dates.

What happens if my Data safety answers are wrong?

Google can reject an update or issue a policy warning if the app's behavior does not match the declaration. Base the form on an inventory of the actual code and SDKs, not on assumptions.

Want this done right, the first time?

OnlineAppCreator takes products from idea to operation. Tell us where you stand and get a concrete plan in a free 15-minute call.