Loading…
CompareOpen in Google Play
This app isn't in any of our charts yet.
Internal testing.
Reference Android app: from a single push to Play Store, fully automated.
What is this app? AndroidCiCd is a working reference project that shows how a modern Android app travels from a Git commit all the way to a tester's phone — without anyone touching a build menu in Android Studio. What's inside Two GitHub Actions pipelines do the work: • Push to the staging branch → a signed staging APK is built, uploaded to Firebase App Distribution, and the QA group gets an email link to install it. A Slack message lands with the version, the commit, and a one-click tester URL. • Push to the main branch → a signed release AAB is built, uploaded to Google Play, and a Slack notification fires with a Play Console link. What gets automated • Version code and name pulled from versioned property files — no more forgotten version bumps. • Per-variant keystores decoded from base64 secrets at build time — nothing sensitive is ever checked in. • Output APKs renamed to a predictable pattern: AppName-vX.Y(buildNumber)-variant.apk. • Release notes for Firebase and Play Store live alongside the code. • Slack messages adapt to the build — tester links for staging, Play Console links for production. Why it exists Most Android tutorials stop at "click Build > Generate Signed Bundle." Real teams ship dozens of times a week and can't afford to do that by hand. This project is a starting point that drops into any Android repo: copy the workflows and the ci/ folder, swap a few package names, set a handful of GitHub secrets, and your project ships itself. Tech inside GitHub Actions • Gradle Kotlin DSL with AGP 9.1 • Firebase App Distribution • Google Play Publisher API • Slack Incoming Webhooks The app itself is intentionally minimal — the value is in the pipeline that delivered it.