From Claude Code to Google Play: Publishing Your Android App

By jocapps4 min read

Short answer: To publish an Android app built with Claude Code, create a Google Play developer account, build a signed Android App Bundle, enroll in Play App Signing, move through internal and closed testing tracks, complete Data safety, content rating and target audience, then release with a staged rollout. Keep the upload key safe and outside the repository.

On this page

The short path from Claude Code to Google Play

Google Play is often the faster store to launch on, but it has its own sharp edges. The process revolves around Play Console: you upload a signed Android App Bundle, distribute it through testing tracks, fill in several policy declarations and then promote a release to production.

Claude Code handles the Gradle configuration, manifest and release scripts well. The parts that need a human owner are the developer account, the signing keys, the policy declarations and the decision when to roll out to everyone.

Developer account and testing requirements

Google Play has a one-time 25 USD registration fee. Register as an organization if the app belongs to a company; identity verification applies to both account types and can take a few days.

New personal developer accounts must run a closed test with a minimum number of testers for a minimum period before they can apply for production access. The exact numbers have changed over time, so check the current requirement in Play Console when you start. Organization accounts are handled differently, which is one more reason companies should not publish from a personal account.

Recruit testers early. A closed test with real users is also the most valuable feedback round you will get before launch.

Building and signing the App Bundle

Google Play requires the Android App Bundle format for new apps. With Play App Signing, Google holds the app signing key, and you sign uploads with a separate upload key. If the upload key is lost, it can be reset through support; losing the key in a setup without Play App Signing is far worse.

Ask Claude Code to set up a release build type that reads keystore credentials from environment variables or a local properties file that is ignored by git. A common mistake in AI-generated projects is a keystore path or password hard-coded into build.gradle and committed. Review this before the first push.

  • applicationId set to a permanent, unique package name; it cannot change after publishing.
  • versionCode incremented for every upload, versionName readable for users.
  • targetSdkVersion meeting the current Google Play target API level requirement.
  • Minification and resource shrinking enabled and tested, because R8 can strip classes used via reflection.
  • Upload keystore backed up in a password manager or secrets vault, never in the repo.

Need a hand? appsubmitter.io helps with exactly this. Book a call for free and get a clear plan in 15 to 30 minutes.

Policy declarations that block releases

Most first-release delays on Google Play come from App content declarations rather than technical issues. Each must be completed before production access.

The Data safety section asks which data types the app collects and shares, for what purpose and whether data is encrypted in transit and deletable. Third-party SDKs count, so check what your analytics, crash reporting and ad libraries collect. The content rating questionnaire, target audience and content, ads declaration and, if relevant, permissions declarations for sensitive permissions such as background location or SMS follow. Apps with accounts need an account deletion path in the app and on the web.

From internal test to staged rollout

Play Console offers several tracks. Use them in order instead of jumping to production.

  1. Upload the first bundle to the internal testing track and install it via the opt-in link on several devices.
  2. Check the pre-launch report for crashes, accessibility warnings and security notes.
  3. Move to closed testing, recruit testers and collect feedback for the required period.
  4. Fix issues in Claude Code, increment versionCode and re-upload.
  5. Apply for production access if your account type requires it.
  6. Release to production with a staged rollout, starting with a small percentage of users.
  7. Watch Android vitals for crash and ANR rates before increasing the rollout percentage.

Keeping releases routine

The first release is a project; every later release should be a routine. That means a pipeline that builds, signs and uploads bundles automatically, release notes prepared alongside the code, and someone watching vitals after each rollout.

appsubmitter.io sets up this routine in your own Play Console: CI/CD for Android, Data safety and content declarations, testing track management and help when a policy issue or rejection appears. Because appsubmitter.io combines AI-assisted checks with human release experts, recurring releases need far less of your attention.

If testers in the closed track report crashes on specific devices or the codebase needs a review before production, apprat.io adds senior AI Code Engineers who test on real Android hardware and review Claude Code changes. A free call is a quick way to map out the remaining steps for your app.

Frequently asked questions

Is Play App Signing mandatory?

For new apps published as Android App Bundles, Play App Signing is required. Google manages the app signing key and you upload with your own upload key. This protects you from losing the signing key permanently, since a lost upload key can be reset through Google support.

Why can I not publish to production immediately?

New personal developer accounts must complete a closed test with a minimum number of testers over a minimum period before applying for production access. The thresholds have changed in the past, so check the current requirement in Play Console. Organization accounts follow different rules.

Can Claude Code fill in the Data safety form?

Claude Code can help by listing SDKs, permissions and network calls in your project, which is a good starting point. The declaration itself is a legal statement by your organization, so a responsible person should verify it against what the app and backend actually do before submitting it.

What is a staged rollout and should I use it?

A staged rollout releases an update to a percentage of users first, so you can watch crash and ANR rates before everyone gets it. It is strongly recommended for apps built quickly with coding agents, because device-specific issues often appear only at scale.

Also useful for this

Talk to an AI Code Engineer, free of charge

Tell us where you are and where you want to go. In a short call we map out the fastest path, whether that is a workshop, a launch in the App Store and Google Play or a full AI-native product.

No obligation. English or German. Run by jocapps, ISO 27001 and ISO 9001 certified. Prefer the phone? 24/7 call support: +49 761 519 751 50

Book a call for free

Related guides

Book a call for free