The official Google Play documentation makes launching an app look like a five-step process. It is not a five-step process. Here is what it actually looked like for Shift Desk — every step, including the parts that tripped me up.
Step 1: Developer account
You pay a one-time $25 fee to create a Google Play Developer account. Straightforward. What nobody tells you is that identity verification can take several days, and you can't publish anything until it clears. Plan for this delay before your planned launch date.
Step 2: Prepare your store listing
This took longer than I expected. You need:
- A short description (80 characters) — harder to write than it sounds
- A full description (4000 characters) with keywords
- At least 2 screenshots per supported screen size
- A feature graphic (1024x500px banner)
- A high-res icon (512x512px)
- Privacy policy URL — mandatory, even for simple apps
Step 3: Build a release AAB
Google now requires Android App Bundles (.aab) instead of APKs for new apps. In Android Studio: Build → Generate Signed Bundle. You'll need a keystore file — generate one and back it up immediately. If you lose your keystore, you cannot update your app. Ever. New listing required.
Step 4: Content rating questionnaire
Fill out a questionnaire about your app's content. Takes about 10 minutes. You get a rating at the end (Shift Desk is rated Everyone). Skip this and your app won't go live.
Step 5: Review
First-time submissions go through a longer review process. Google says up to 7 days. Mine took 4. During this time you can see the app in your console but it isn't live. There's nothing to do but wait.
What I'd do differently
- Start the developer account earlier — don't leave identity verification to the last week
- Write store listing copy before the app is finished, not after
- Take screenshots on a real device, not an emulator — they look better
- Back up the keystore to at least two separate locations on day one
The process is manageable. It just has more waiting than you'd expect, and more assets to prepare than the docs suggest. Build that time into your launch plan and it won't catch you off guard.