DEV Community

Cover image for How I Published My First App on Google Play: A Developer's Honest Guide
Kaloovaloo
Kaloovaloo

Posted on

How I Published My First App on Google Play: A Developer's Honest Guide

#android #tutorial #beginners #mobile

Publishing your first app on Google Play sounds simple — until you're three hours deep into signing configs, version codes, and policy violations you didn't know existed.

This is the guide I wish I had.

1. Start With the Right Mindset

Google Play isn't just a file upload. It's a review process, a policy ecosystem, and a long-term relationship with Google's infrastructure. Your app will be rejected at some point. That's normal.

2. Prepare Your App for Release

Before you touch the Play Console, make sure:

  • minSdkVersion and targetSdkVersion are set correctly (target the latest stable API level)
  • All debug flags and logs are removed
  • Your applicationId is final — you can never change it
  • Permissions in AndroidManifest.xml are minimal and justified

3. Generate a Signed APK / AAB

Google requires a signed release build. Use Android App Bundle (.aab) — it's smaller and required for new apps since August 2021.

./gradlew bundleRelease
Enter fullscreen mode Exit fullscreen mode

Generate your keystore once and back it up. Losing it means losing the ability to update your app forever.

keytool -genkey -v -keystore my-release-key.jks \
  -keyalg RSA -keysize 2048 -validity 10000 \
  -alias my-key-alias
Enter fullscreen mode Exit fullscreen mode

4. Set Up Google Play Console

  • Create a developer account at play.google.com/console ($25 one-time fee)
  • Create a new app, fill in the store listing: title, short description, full description, screenshots, and feature graphic
  • Screenshots matter more than you think — they're your storefront

5. Fill Out the Required Declarations

This is where most first-timers get surprised. You'll need to complete:

  • Data safety form — what data your app collects and why
  • Target audience — especially important if any users could be under 13
  • Content rating questionnaire — answer honestly, incorrect ratings get apps removed
  • App access — provide test credentials if your app has a login

6. Internal Testing → Closed Testing → Production

Don't launch straight to production. Google's rollout model is designed for safety:

  1. Internal testing — up to 100 testers, instant review
  2. Closed testing (Alpha/Beta) — wider audience, still controlled
  3. Production — full rollout, can be staged (10% → 50% → 100%)

Start with internal testing. Get real feedback. Fix what breaks.

7. Common Rejection Reasons

  • Missing privacy policy URL (required even for simple apps)
  • Permissions not matching app functionality
  • Misleading store listing
  • App crashing on launch (Google runs automated tests)
  • Target API level too old

8. After Publishing

Publishing is not the finish line. Monitor:

  • Android Vitals — crash rate, ANR rate
  • Reviews — respond to negative ones professionally
  • Policy emails — Google will email you about violations; act fast

Final Thoughts

The Play Store has gotten stricter over the years, but for good reason. The review process protects users — and eventually, it protects your reputation too.

Ship something real. Even a simple utility. The experience of going end-to-end is worth more than any tutorial.

Have you shipped an app on Google Play? Drop your biggest lesson in the comments.

Top comments (0)