Key takeaways
- Claude Code can run every Gradle task an Android release needs, from unit tests to bundleRelease, without a Mac or any special machine.
- The applicationId is permanent after the first upload – write it into CLAUDE.md and block the agent from touching signing files and keystore passwords.
- With Play App Signing, Google holds the app signing key; your upload key stays out of the repository and out of agent transcripts.
- New personal developer accounts need a closed test with at least 12 opted-in testers for 14 days in a row before production – schedule it before the code is finished.
- Data safety, account deletion, target API level 36 and Play Billing are the policy gates agents rarely think about on their own.
Why Android suits a terminal agent – up to the Play Console
Claude Code works where Android builds already happen: in a shell. The Gradle wrapper in your project runs the same way on a Linux laptop, a Windows workstation or a CI container, so the agent can call ./gradlew testDebugUnitTest, read the failure, change the Kotlin code and try again until the suite is green. With an emulator or device attached, it can install a debug build through adb and read logcat. There is no equivalent of the Mac-and-Xcode requirement that shapes iOS releases.
The limits start where your identity starts. Claude Code cannot open a Google Play developer account, pass identity verification, accept the Developer Distribution Agreement, decide what goes into the Data safety form or recruit testers. It also should not see the secrets that prove a build came from you. A good release plan therefore has two tracks running in parallel: the agent hardens the code and the build, and a person works through the Play Console.
Write the Android release facts into CLAUDE.md
Agents guess when facts are missing, and some guesses are expensive on Google Play. State them in CLAUDE.md at the root of the repository:
- The applicationId. Once the first bundle is uploaded, it can never change. Spell out that the Gradle
namespace(used for the R class and code packages) may be refactored, but theapplicationIdmay not. - SDK levels.
compileSdkandtargetSdkat 36, plus your chosenminSdk. Agents sometimes lower a target to make a deprecation warning disappear. - Versioning. Who increments
versionCode– ideally the release pipeline, never an ad-hoc session. - Commands. The exact tasks for tests, lint and the release bundle, including the build variant names if you use flavors.
- Protected files. The signing block in
app/build.gradle.kts,keystore.properties, manifest permissions, R8 keep rules andgoogle-services.json.
Instructions are advice; settings are enforcement. Add deny rules to the project's Claude Code settings so the agent cannot read the keystore or its properties file at all, and consider a hook that stops edits to the signing configuration. Our guide to CLAUDE.md and AGENTS.md for mobile projects has a template, and Claude Code for Kotlin and Jetpack Compose covers the day-to-day build loop.
Talk to an AI Code Engineer about shipping your app to Google Play.
In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.
Upload key, app signing key – and who holds which
New apps on Google Play ship as Android App Bundles, and Play App Signing is part of that: Google stores the key that signs the APKs users actually install. You sign each upload with a separate upload key. The key that matters most never touches your machines.
| Key | Where it lives | Role of Claude Code |
|---|---|---|
| App signing key | Google, via Play App Signing | None |
| Upload key | A keystore outside the repo, a password manager and your CI secrets | Writes the Gradle config that reads it from environment variables |
| Debug key | Each developer machine | Uses it freely for local builds |
Generate the upload keystore yourself with keytool or Android Studio's wizard, store the passwords in your password manager and give CI the file as an encrypted secret. Claude Code can then write the workflow step that decodes it at build time. If the upload key is ever lost or leaked, the account owner can request a reset in the Play Console – see Google's Play App Signing help.
The Play Console work that only you can do
The app record asks for a default language, the app name, whether it is an app or a game and whether it is free or paid – and a free app cannot later be switched to paid. After that comes the App content area, where every declaration must match the build:
- a privacy policy URL that loads and names your app,
- app access instructions with a working test login if anything sits behind sign-in,
- the ads declaration, the content rating questionnaire and the target audience,
- the Data safety form, which describes every data type the app or its SDKs collect or share.
Claude Code helps as a research assistant: ask it to list every SDK in the Gradle files and what each transmits, then verify against the vendors' disclosure pages. Our playbook on Data safety with AI agents describes that workflow.
Plan around the 14-day closed test
If your developer account is a new personal one, production is locked until you have run a closed test: at least 12 testers must be opted in, and they must stay opted in for 14 consecutive days. Only then can you apply for production access, and Google asks how the test went. Organization accounts are exempt, but a real test still pays off.
Use the tracks as a ladder:
- Internal testing for your own team – builds are available within minutes, which makes it the right place to verify that the signed bundle installs and the login works.
- Closed testing with the 12+ outside testers. Start it as soon as the app is usable, not when it is perfect.
- Production, ideally as a staged rollout.
The two weeks are not waiting time. Collect tester feedback and the pre-launch report, turn each finding into a small, reproducible task for Claude Code and ship updates to the closed track. Google looks for signs of an engaged test, and a sequence of updates is one of them. Details are in our closed testing playbook and the 12 testers / 14 days guide.
Policy gates to clear before production
Run through these before you request production:
- Target API level. New apps and updates must target Android 16 (API level 36). Raising the target can surface behaviour changes, so let the agent fix them with tests, not by suppressing warnings – see the target API level guide.
- Account deletion. If people can create an account, they need a way to delete it inside the app and a web page where they can request deletion without reinstalling.
- Payments. Digital goods and subscriptions go through Google Play Billing.
- Permissions. Sensitive ones – background location, SMS, call log, broad file access – need a declaration and a core-feature justification. Review every manifest diff.
- Generative features. If the app creates text or images with AI, Google expects a way for users to report offensive output.
The Google Play review checklist for AI-built apps covers the rest.
Automating releases with headless Claude Code
Once the first release is out, Claude Code's non-interactive mode (claude -p) and its GitHub Actions integration fit neatly into a release workflow. Practical jobs: checking that versionCode went up, turning merged pull requests into release notes and flagging manifest or dependency changes that affect Data safety. The upload itself is ordinary tooling – the Gradle Play Publisher plugin or fastlane supply with a service account that has only the permissions it needs. Promotion from testing to production stays a human click.
Shipping on iOS as well? The repository habits carry over, the store work does not – compare with Claude Code app to the App Store. And if you would rather not run the Play Console side yourself, our AI Code Engineers set up signing and CI/CD, prepare the listing and declarations and handle review in your own account through the Android submission service.
Google Play release checklist for a Claude Code app
- CLAUDE.md fixes the applicationId, SDK levels, versioning rule, build commands and protected files.
- Claude Code settings deny reads of the keystore and keystore.properties.
- The upload keystore lives outside the repository; CI receives it as an encrypted secret.
- ./gradlew bundleRelease produces a signed App Bundle that installs from the internal track.
- compileSdk and targetSdk are 36 and behaviour changes are covered by tests.
- The Data safety answers match every SDK listed in the Gradle files.
- In-app account deletion works, and a public deletion request page is linked in the Play Console.
- For a new personal account: 12 or more testers have stayed opted in to the closed test for 14 days.
- App access instructions include a working reviewer login.
Frequently asked questions
Can Claude Code publish my app on Google Play by itself?
It can build the App Bundle and run the tool that uploads it to a testing track, once you have created the app in the Play Console and set up a service account. Creating the developer account, completing the declarations, running the closed test and promoting a release to production remain your decisions.
Should Claude Code generate my upload keystore?
Better not. Create it yourself so the passwords never appear in a session transcript, keep a backup in a safe place and give CI an encrypted copy. The agent only needs to know the names of the environment variables that hold the values.
How long does the first Google Play release take?
For a new personal account, at least the 14 days of the closed test plus the review of your production access application and the app itself. Organization accounts can go to production sooner. Review times vary, so plan buffer before any launch date.
Can you take over the Google Play release?
Yes. Book a free call and an AI Code Engineer reviews your project with you. If you hand it over, we handle signing, CI/CD, the store listing, the declarations and the review conversation in your own Play Console account.
Free, 15 minutes, no obligation
Get your app from agent output to approved release.
Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.
AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.