How to Publish Your Android App to Google Play

Snapp now publishes your Android app to Google Play for you — no computer, no command line. You tap Publish, and Snapp builds the app and sends it to your Play Console. This guide covers exactly what you need and the steps to get there.

---

What you'll need (one-time setup)

1. A Google Play Developer account — a one-time $25 fee. → How to create a Google Play Developer account 2. Your app created in Google Play Console and the first release uploaded manually (Google requires the very first .aab to be uploaded by you — after that, Snapp handles every release automatically). 3. A Google Play service account key (a small JSON file) so Snapp can upload on your behalf.

Sounds like a lot, but each step is one-time. After this, publishing is a single tap.

---

Step 1 — Create your app in Play Console

1. Open the Google Play Console and click Create app. 2. Enter your app name, language, and confirm it's an App, not a game (or vice-versa). 3. Complete the store listing basics (description, icon, screenshots) — you can refine these later.

---

Step 2 — Upload the first release yourself

Google requires the first app file to be uploaded manually. In Snapp:

1. Open your app → Publish → Android → Just build the file → choose AAB. 2. When it's ready, download the .aab. 3. In Play Console → Test and release → Testing → Internal testing (or Test and release → Production) → Create new release → upload the .aab → roll it out.

Not sure about APK vs AAB? → APK vs AAB: getting your Android app file

---

Step 3 — Connect a service account (for automatic publishing)

So Snapp can upload future releases for you:

1. Go to Google Cloud Console → IAM & Admin → Service Accounts → Create service account. 2. Create a JSON key and download it. 3. In Play Console → Users and permissions → Invite new user → paste that service account's email → grant it release access. 4. In Snapp → Publish → Store credentials → Google Play → Connect → paste the whole JSON.

> New permissions on Google can take a little while to take effect — if the first automatic publish is rejected for permissions, wait a bit and retry.

---

Step 4 — Publish, hands-free

From now on: open your app → Publish → Android → "Publish to Google Play for me". Snapp builds the .aab, uploads it to your Internal testing track, and notifies you (push + email) when it's done. Then finish in Play Console — complete your listing and roll out to production → Complete your Google Play listing & submit for review.

---

Common questions

Why do I have to do the first upload manually? It's a Google rule — the very first release for a new app must be uploaded by the account owner. Every release after that is automatic through Snapp.

Where does my app land? On the Internal testing track first (safe to verify). You promote to Production in Play Console with one click.

How much does it cost? Google Play: $25 once. On the Snapp side, publishing needs a Starter plan or higher, and each successful publish uses one of your plan's monthly publishes (failed attempts are free).

---

What's next

Don't have a developer account yet? → Create a Google Play Developer account
Just need the file to test on a phone? → APK vs AAB
Made a small change after publishing? → What is OTA?

How to Publish Your Android App to Google Play