Claude Code to Google Play: Shipping an Android App Built by an Agent

Ship an app built with Claude Code to Google Play: wrapper or native Kotlin, a Gradle feedback loop for the agent, sensitive permissions and Play uploads.

Short answer

Android builds run on Linux, so Claude Code can compile, test and lint an Android project itself, which makes native Kotlin work far more practical than on iOS. For a web app built with Claude Code, a native wrapper such as WebViewGold is still the fastest route to Google Play. Either way, watch the sensitive permissions agents like to add, keep the upload key and Play credentials in CI, and run Play's testing tracks.

On this page
  1. Why Android suits an agent workflow
  2. Route 1: the fast path with a wrapper
  3. Route 3 in practice: native Kotlin with a closed loop
  4. Sensitive permissions agents like to add
  5. Signing and uploading without handing over the keys
  6. Play Console checklist
  7. Who does what
  8. FAQ
  9. Tools from the jocapps ecosystem

Why Android suits an agent workflow

An agent is only as good as its feedback loop. On iOS, that loop requires macOS and Xcode. On Android, the toolchain (JDK, Android SDK, Gradle) runs on Linux, macOS and Windows, including in containers and CI runners. Claude Code can run ./gradlew assembleDebug, unit tests and lint, read the errors and fix them without a human relaying messages.

That changes the economics. For a team that built its web product with Claude Code, three Android routes are realistic:

RouteWhat Claude Code doesGood for
Native wrapper around your web appBackend for push, app-context detection in the web app, small wrapper adjustmentsGetting to Play fast with an existing web product
Wrapper now, native screens laterSame, then native Kotlin screens for the parts that need itProducts where one or two flows need native performance
Native Kotlin with Jetpack ComposeMost of the app, with a human reviewing architecture and UXOffline-first, hardware-heavy or high-polish apps

Route 1: the fast path with a wrapper

WebViewGold is an Android Studio template: set your production URL, package name, icon, splash screen and enable native features such as push notifications, offline handling, file downloads and native share, then build a signed App Bundle. It is a one-time payment and the project is yours.

Useful Claude Code tasks around it:

  • Add an endpoint that stores push tokens per user and sends notifications on real events.
  • Detect the app context from the user agent and hide web-only elements.
  • Make every screen of the web app work with the Android back gesture and a 360 dp wide viewport.
  • Build an account deletion flow plus the public deletion page Google Play asks for.

The device-side pieces (push registration, file chooser, download handling) already exist in the WebViewGold project, so the agent's work stays in your web codebase, where its feedback loop is strongest.

If you want the wrapper configured for you instead, WeSetupYourWebViewApp delivers it with full source code in about 72 hours.

Route 3 in practice: native Kotlin with a closed loop

When you go native, set up the project so Claude Code can verify its own work.

  1. Create a clean project skeleton with Kotlin, Jetpack Compose, a single-activity architecture and your chosen dependency injection and networking libraries. Decide these yourself; do not let the agent pick a new pattern per feature.
  2. Document commands in CLAUDE.md: how to build, run unit tests, run lint and run instrumented tests if an emulator is available.
  3. Define done: a task is complete only when build, tests and lint pass.
  4. Generate the API client from your backend's schema where possible, so the agent does not hand-write networking code that drifts from the server.
  5. Review UI on real devices. Compose previews and screenshots help, but a person still needs to judge whether a screen feels right.

A short CLAUDE.md section might read:

## Android
- Build: ./gradlew assembleDebug
- Unit tests: ./gradlew testDebugUnitTest
- Lint: ./gradlew lintDebug
- Do not change applicationId, signing configs or keystore paths.
- New permissions require a comment explaining the user-facing feature.
- Prefer the system photo picker over broad media permissions.

For a comparison of agents on mobile stacks, see agentic coding tools for iOS and Android development.

Sensitive permissions agents like to add

Agents solve problems with whatever works, and on Android that sometimes means a permission that Google Play restricts. Several permissions need a declaration form in the Play Console or are allowed only for specific use cases. Watch for:

  • Broad media access (reading all photos and videos) when the system photo picker would do. Google expects apps with occasional media needs to use the picker.
  • Querying all installed packages, which is restricted to apps with a core need.
  • Exact alarms, which are limited to apps whose core function requires them, such as alarm clocks and calendars.
  • Foreground services without a declared type matching what the service actually does.
  • Background location without a strong, user-visible reason.

Make "new permission" a mandatory review point in every pull request touching AndroidManifest.xml.

Signing and uploading without handing over the keys

Use Play App Signing: Google holds the app signing key, you hold an upload key. Keep the upload keystore and its passwords in CI secrets, not in the repository and not in the agent's working environment.

For uploads, tools such as Gradle Play Publisher or fastlane can push bundles to a testing track through the Google Play Developer API using a service account. Grant that service account only the permissions needed for release management. A good split: Claude Code can write and change the release workflow; a human merges it, and CI holds the credentials. Our guide to CI/CD for AI-built mobile apps goes into the setup.

Play Console checklist

  • Internal testing track first, then closed testing.
  • New personal developer accounts: closed test with at least 12 testers for 14 continuous days before production. Organization accounts are exempt.
  • Data safety form that matches what the code really sends, including SDKs the agent added (analytics, crash reporting, ads).
  • Privacy policy, content rating, target audience.
  • Account deletion in the app and via a web link if users can register.
  • Target API level as currently required; Google raises it every year.

Who does what

appsubmitter.io handles Play Console setup, listings, submissions and rejections in your own account. For an Android codebase that needs ongoing work, apprat.io combines AI-assisted development with human developer hours. And if your engineers want to build this workflow themselves, neooutput runs hands-on Claude Code workshops on your own repository. For the web side, see deploying an app built with Claude Code.

FAQ

Can Claude Code build a signed Android App Bundle?

It can run the Gradle tasks that produce one. We recommend producing signed release bundles only in CI, where the upload key is stored, and letting the agent work with debug builds locally.

Is a native Kotlin rebuild with Claude Code realistic?

Yes, more so than on iOS, because the agent can build and test on Linux. Plan for architecture decisions and UX review by experienced people; generated code still needs review.

Which permissions cause Google Play trouble most often?

Broad photo and video access, querying all installed packages, exact alarms, background location and foreground services without the right type. Use narrower alternatives where possible.

Do I need Android Studio if Claude Code does the work?

Not strictly, but it remains the best tool for layout inspection, profiling and emulator management. Many teams use both.

Tools from the jocapps ecosystem

Want this done right, and fast?

Talk to our AI Code Engineers and AI architects. In a free 30-minute call we look at your idea, prototype or roadmap and tell you honestly what it takes to ship it.

24/7 call support in English and German.

Free call

Free intro call

Tell us which task an AI agent should take responsibility for. We show how our platform, AI Code Engineers and operations plug into your stack.

  • 30 minutes, no obligation
  • Honest feasibility check
  • Concrete next step
Rather talk now? 24/7 call support in English and German+49 761 519 751 50