App Publishing

Table of Contents

• 0 Publishing Overview
• 1 Generating Signed APK
• 2 App Bundle
• 3 Play Console Setup
• 4 Uploading App
• 5 Store Listing Optimization
• 6 Hands-On Exercises
• 7 MCQ Practice
• 8 Basic MCQs
• 9 Advanced MCQs
• 10 Interview Q&A

Publishing Overview

Publishing an Android app means building a signed release, uploading it to Google Play Console, completing store metadata, and submitting for review. Google Play is the primary distribution channel for Android apps worldwide.

1Generating Signed APK

Release builds must be signed with a keystore. Google Play uses your signing key to verify app updates — losing the keystore means you cannot update the app ever again.

Create a keystore

You will be prompted for a keystore password, key password, and certificate details (name, organization). Store the .jks file and passwords securely — never commit them to Git.

Configure signing in Gradle

Generate signed APK in Android Studio

1. Build → Generate Signed App Bundle / APK
2. Select APK (or App Bundle — preferred)
3. Choose existing keystore or create new
4. Select release build variant
5. Click Create — output in app/release/

Build from command line

2App Bundle

An Android App Bundle (AAB) is the publishing format required by Google Play. Play generates optimized APKs per device — smaller downloads, only the resources and CPU architecture the device needs.

AAB vs APK

Enable App Bundle in Gradle

Test App Bundle locally

Play App Signing

Enroll in Play App Signing when uploading your first release. Google manages your app signing key; you upload with an upload key. If you lose your upload key, Google can reset it — but the app signing key stays safe with Google.

3Play Console Setup

Google Play Console is the developer dashboard for publishing and managing apps. A one-time $25 registration fee gives lifetime access to publish unlimited apps.

Account setup steps

1. Go to play.google.com/console
2. Sign in with Google account → pay $25 registration fee
3. Complete developer profile (name, email, website)
4. Verify identity if prompted
5. Create a new app → enter app name and default language

Required Play Console sections

versionCode and versionName

Release tracks

4Uploading App

Upload your signed AAB to a release track, add release notes, complete all policy requirements, and submit for Google review. Review typically takes a few hours to a few days.

Upload workflow

1. Play Console → Your App → Release → Production (or Testing track)
2. Click Create new release
3. Upload app-release.aab
4. Enter release name and release notes (what's new)
5. Review warnings — fix any errors before proceeding
6. Click Review release → Start rollout to Production

Pre-launch checklist

Release notes example

Staged rollout

Use staged rollout to release to a percentage of users first (e.g. 10% → 50% → 100%). Monitor crash reports in Play Console Vitals before full rollout.

Common rejection reasons

5Store Listing Optimization

App Store Optimization (ASO) improves your app's visibility and conversion rate on Google Play. A compelling listing with the right keywords, visuals, and descriptions drives more installs.

Store listing assets

Writing effective descriptions

ASO keyword strategy

• Research keywords users search for in your category
• Place primary keywords in title and short description
• Repeat important keywords naturally in full description
• Use Google Play's Custom store listing for A/B testing titles/descriptions
• Localize listing for major markets (Hindi, Spanish, etc.)

Screenshot best practices

• First screenshot is most important — show core value immediately
• Add text overlays explaining each feature
• Use device frames for a polished look
• Show the app in action, not empty states
• Include a screenshot with social proof (ratings, user count) if available

Metrics to track post-launch

6Hands-On Exercises

App Publishing MCQ Practice

App Publishing Interview Q&A

15 topic-focused questions for interviews and revision.