| name | android-deployment |
| displayName | Android Deployment & CI |
| description | Android app deployment workflows covering Play Store releases, CI/CD pipelines, code signing, and Tauri mobile distribution.
|
| category | mobile |
| tags | ["android","deployment","play-store","ci-cd","code-signing","tauri-mobile"] |
| agents | ["android-kotlin","devops-engineer"] |
| toolkit_refs | ["gradle","mobile"] |
Android Deployment & CI
Build Types
Debug Build
./gradlew assembleDebug
- Auto-signed with debug keystore
- Suitable for local testing and CI verification
Release Build
./gradlew assembleRelease
- Requires signing config in
build.gradle.kts
- ProGuard/R8 enabled for minification
- Generate signed bundle:
./gradlew bundleRelease
AAB (Android App Bundle)
./gradlew bundleRelease
- Preferred format for Play Store distribution
- ~40% smaller than universal APK
Code Signing
Keystore Setup
android {
signingConfigs {
create("release") {
storeFile = file("../keystore/release.keystore")
storePassword = System.getenv("KEYSTORE_PASSWORD")
keyAlias = System.getenv("KEY_ALIAS")
keyPassword = System.getenv("KEY_PASSWORD")
}
}
}
Best Practices
- Store keystore encrypted in CI secrets, never in git
- Use different keystores for staging vs production
- Rotate keys annually, migrate gracefully via Play Console
CI/CD Pipeline (via Workflow)
The android-build-test-deploy workflow orchestrates:
- Build → Gradle MCP assembles APK
- Test → Unit + instrumented via Gradle + Mobile MCP
- Deploy → Release build with signing, upload to Play Store
For full pipeline, run: /workflow android-build-test-deploy
Tauri Mobile Distribution
- Tauri generates Android project at
src-tauri/gen/android/
- Build Tauri Android:
cargo tauri android build
- The resulting APK is at
src-tauri/gen/android/app/build/outputs/apk/
- Tauri bundles Rust binary inside the APK — no separate distribution needed