From Claude Code Project to Google Play

When Claude Code has built most of your Android app, the remaining distance to Google Play is shorter than people expect, and also more bureaucratic. Code is the smaller part. Accounts, policies, testing and listings take the rest. Here is a practical route.

Identify the project type and build target

Claude Code can work across stacks, so the first step is to confirm what you have: a native Kotlin project, a cross-platform project such as React Native or Flutter, or a web app that needs a wrapper. For each, make sure a release build can be produced from a clean checkout on another machine. If it only builds in the agent's session, you do not have a release process yet.

Make the build reproducible

• Pin dependency versions and commit lock files.
• Keep secrets out of the repository and inject them at build time.
• Use separate debug and release configurations, with release minification tested.
• Record the exact commands that produce the .aab file.

This is also where continuous builds help; see CI/CD for AI-built apps.

A good habit is to ask the agent to produce a release checklist from your repository, then have a person verify each line against the actual build. The agent is useful for spotting forgotten items such as missing launcher icons or an outdated manifest entry, but only a human can confirm that the result behaves correctly on a device in a pocket rather than in a terminal.

Signing and Play Console

Use Play App Signing, keep the upload key backed up and create the app entry in Play Console. Company accounts need verification, which we describe in our Play Console setup guide. Then fill in the store listing, content rating, target audience, ads declaration and data safety form. The data safety answers must match the SDKs and network calls in the codebase, so it helps to have a human audit what the agent added.

Testing before production

Start with internal testing to catch crashes quickly. If your account type requires closed testing before production, plan for the calendar time it takes; see our closed testing article and confirm the current rules in Google's documentation. Use real devices from different manufacturers, plus at least one older Android version you support.

Where an agent needs a human

Release signing mistakes to avoid

The most expensive mistakes are quiet ones. Committing the keystore and its password to the repository exposes your signing identity. Losing the upload key slows down every future update, because Google has to process a key reset. Letting an agent regenerate signing files "to fix a build error" can break the update path for existing users. Treat signing files as human-controlled assets and keep a documented recovery path.

Also check the target and minimum Android versions in the build configuration. Google updates its target API level requirements regularly, so confirm the current one before you upload.

The apprat.io approach

Our Claude Code-to-App module and service team follow the principle of AI speed, human responsibility. Coding agents handle much of the implementation, while an AI Code Engineer plans, reviews every change, tests on real Android devices and manages the Google Play submission. If you already have a project and are unsure about its state, we offer code audits and rescue for AI-generated apps; book a call for free to talk about it.

Finally, document what the agent was asked to do and what was reviewed. A short note per release, listing the main changes, the reviewer and the test devices, is cheap to write and extremely valuable when something goes wrong three months later. It is also the kind of traceability that quality and security audits expect.

Final checks before rollout

1. Install the release build, not the debug build, on three or more devices.
2. Verify push notifications, deep links and login on each.
3. Confirm privacy policy and account deletion links are live.
4. Roll out in stages and watch crash and ANR reports.

iOS is next? Read From Claude Code project to Apple App Store.