Deploy & App Stores
Shipping a Claude Code App to the Google Play Store
Claude Code is well suited to Android because the entire toolchain runs from the command line on any OS: it can add Capacitor or scaffold Expo, configure Gradle, build a signed .aab and automate uploads through the Google Play Developer API. You still own the Play Console account, the 14-day closed test for new personal accounts and the policy declarations.
Why does Android suit an agentic workflow?
Android builds run headless on Linux, macOS or Windows with Gradle, which means Claude Code can build, test and fix the app in a loop without a GUI. That is a real advantage over iOS, where signing and some steps tie you to Xcode on macOS.
Claude Code can also run Android emulator commands and read logcat output, so it can reproduce crashes rather than guessing at them.
- ./gradlew bundleRelease to build an .aab
- adb and logcat for device debugging
- Lint and unit tests runnable in CI
How should CLAUDE.md describe the Android project?
Write down the package name, SDK levels, build commands and the rules about secrets. This keeps every Claude Code session consistent and stops it from changing the applicationId or committing a keystore.
Add a rule that targetSdk changes must be deliberate, because Google Play's target API level requirement rises over time and behavior changes come with each new level.
- applicationId and how versionCode is derived
- Build: npm run build, npx cap sync android, ./gradlew bundleRelease
- Keystore path and passwords come from environment variables only
- Handle the back button and edge-to-edge insets in every new screen
How do you build and sign the release bundle?
Let Claude Code wire Gradle signing to environment variables, then build the .aab locally or in CI. You create the upload keystore yourself and enroll in Play App Signing so Google holds the app signing key.
Ask Claude Code to add R8 minification rules for any libraries that need them and to verify the release build on an emulator, since minification bugs only appear in release mode.
- Generate an upload keystore with keytool and store it in a secret manager
- Have Claude Code add a signingConfigs block reading from environment variables
- Run ./gradlew bundleRelease and install a test build via bundletool or internal testing
- Create a CI workflow that builds the .aab on every tagged release
How do you handle the 12 testers, 14 days closed test?
If your Play developer account is a new personal account, you must run a closed test with at least 12 opted-in testers for 14 consecutive days before you can apply for production. Claude Code cannot shorten this, but it can make the period productive.
Automate uploads to the closed track with fastlane supply or the Play Developer API using a service account, so testers get frequent updates. Note that the very first upload of a new app is usually done manually in Play Console before API uploads work.
- Collect tester feedback in an issue tracker Claude Code can read via MCP
- Ship fixes during the test window to show real iteration
- Answer the production access questionnaire with concrete learnings
How can Claude Code prepare the Data safety form?
Ask Claude Code to inventory what data the app and every SDK collects, then turn it into a draft for the Data safety form. It can scan dependencies, network calls and storage code far faster than a manual review.
A human must verify and submit the answers, because Google holds you accountable for accuracy, and the form must match your privacy policy. Remember account deletion: in-app and via a web link if users can create accounts.
- Firebase, analytics and crash reporting SDKs
- Location, contacts, photos and files access
- Whether data is encrypted in transit and can be deleted
What Android-specific features should Claude Code add?
Focus on the features that make an app feel native on Android: push via Firebase Cloud Messaging, App Links, a correct back stack and the Android 13+ notification permission. Ask Claude Code to implement them one at a time with tests.
If you sell digital content, Google Play Billing is generally required; Claude Code can integrate a billing plugin, but test purchases with license testers before release.
How do you roll this out in a team?
Standardize the workflow so anyone can cut an Android release with the same commands and agent rules. neooutput's agentic coding workshops cover exactly this kind of CLAUDE.md, hooks and CI setup, and our AI Code Engineers can implement the pipeline for you; appsubmitter.io supports the store submission side.
Not every web app needs a custom Capacitor pipeline. If the product is a stable web app and speed matters more than deep native integration, WebViewGold converts it into native Android and iOS apps without code, with push notifications, in-app purchases and deep links configurable; Claude Code can then focus on the web app itself. The wrapped app still needs genuine native value, especially for Apple's guideline 4.2.
Frequently asked questions
Can Claude Code upload directly to Google Play?
Yes, via fastlane supply or the Google Play Developer API with a service account key you configure. Keep the key in a secret store and limit its permissions in Play Console.
Can Claude Code create my Play Console listing?
It can draft descriptions, release notes and Data safety answers, and upload listing text through the API. Account creation, verification and policy declarations should be done by a human.
Is Expo or Capacitor better for Android with Claude Code?
Both work well. Capacitor reuses an existing web app; Expo is better for mobile-first apps and its EAS services can build and submit Android apps from the cloud.
Do I need Android Studio at all?
Not strictly, since Gradle and the SDK command-line tools can do everything. Android Studio is still useful for layout inspection, profiling and debugging.
