How to launch an Android app on Google Play as a solo developer

Publishing on Google Play as an individual is cheap but no longer instant. New personal developer accounts must run a closed test with real testers for two weeks before they can publish to production, and identity verification is part of sign-up. Planning for those steps is the difference between a launch date you hit and one that slips by a month.

This guide follows Google’s official Play Console documentation. Requirements were checked on the “last verified” date above.

Timeline at a glance

Budget at least three to four weeks from account creation to a public listing.

Step 1: create the developer account

• The registration fee is a one-time US$25. Google accepts Mastercard, Visa, American Express, Discover (US only) and Visa Electron (outside the US); prepaid cards are not accepted.
• You must be at least 18.
• Choose Personal or Organization. Google may ask for a valid government ID and a credit card in your legal name. If the information is found invalid, the fee is not refunded.
• Personal accounts must also verify access to an Android device through the Play Console mobile app.

Personal or organization? Organization accounts are meant for businesses and other organizations, and the verification asks for organization details. A personal account is the usual route for an individual, but it comes with the testing and device verification requirements below. If you already run a registered company, compare both options in Play Console before you pay.

Step 2: meet the technical requirements

Since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher to be submitted, with exceptions for Wear OS, Android Automotive OS, Android TV and Android XR apps. Existing apps must target at least Android 15 (API level 35) to stay available to new users on newer devices. Google allows an extension request to November 1, 2026.

In practice:

// app/build.gradle.kts
android {
    compileSdk = 36
    defaultConfig {
        targetSdk = 36
        minSdk = 24 // pick based on your audience
    }
}

Build an Android App Bundle (.aab), use Play App Signing when you create the app in Play Console, and keep your upload key backed up somewhere other than your laptop.

Step 3: prepare the store listing

Google’s character limits:

• App name: 30 characters
• Short description: 80 characters
• Full description: 4,000 characters

Graphic assets:

• App icon: 512 × 512 px, 32-bit PNG with alpha, up to 1,024 KB
• Feature graphic: 1,024 × 500 px, JPEG or 24-bit PNG (no alpha)
• Screenshots: at least 2 across device types; each side 320–3,840 px, and the long side no more than twice the short side. Google recommends at least 4 screenshots at 1080 px or higher for apps to be eligible for screenshot-based recommendation formats.

Also prepare:

• A privacy policy URL (a page on your website works well; see how to pick a domain name)
• Data safety form answers: what data the app collects, why, and whether it is shared
• Content rating questionnaire answers
• Target audience and whether the app contains ads

Step 4: run the closed test (the 12 × 14 rule)

Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before applying for production access. Testers who leave and rejoin restart their own 14-day count.

How to make this go smoothly:

1. Recruit 15–20 testers, not exactly 12, so one dropout does not reset your timeline.
2. Create a Google Group or email list for testers and add it to the closed testing track.
3. Send testers the opt-in link and ask them to install the app and keep it installed.
4. Ship at least one or two updates during the 14 days, and act on feedback, so you can describe a real test when you apply for production access.
5. Keep notes: what testers reported and what you changed.

Good sources of testers are friends, colleagues, and communities around your app’s topic. Avoid paying for fake testers; it does not help your app and risks your account.

Step 5: apply for production access and release

After the 14 days, apply for production access from the Dashboard in Play Console. Once approved:

• Start with a staged rollout (for example 10–20% of users) so a crash affects few people.
• Watch the Android vitals and crash reports for a few days before going to 100%.
• Reply to early reviews; it is one of the few things a solo developer can do every day that users see.

Distribution outside Google Play

Google is introducing Android developer verification for apps installed on certified devices. Protections start on September 30, 2026 for users installing from participating stores in Brazil, Indonesia, Singapore and Thailand, with global expansion planned for 2027. Google states that Play automatically registers about 99% of apps; apps distributed outside Google Play may need manual registration in Play Console or the Android Developer Console.

Launch checklist

• Developer account created, $25 paid, identity and device verified
• App targets API level 36; release built as an .aab with Play App Signing
• Upload key backed up in two places
• App name ≤ 30 chars, short description ≤ 80, full description ≤ 4,000
• 512 px icon, 1024 × 500 feature graphic, 4+ screenshots at 1080 px+
• Privacy policy URL live; Data safety and content rating completed
• Payments decided (see Stripe vs Google Play Billing)
• 15–20 testers recruited; closed test running for 14+ days
• Production access requested; staged rollout planned
• Crash reporting and a support email ready

Common reasons launches slip

• Starting the developer account late. Identity verification, device verification and the 14-day closed test add up to weeks. Create the account as soon as you commit to the project.
• Testers dropping out. If fewer than 12 testers stay opted in continuously, the clock effectively restarts for them. Recruit extra testers and check the count in Play Console every few days.
• Target API level surprises. A dependency that does not support API level 36 can block your build. Update the Android Gradle Plugin, Kotlin and key libraries early.
• Data safety mismatches. Answers must match what the app and its SDKs actually collect. Review the data practices of every analytics, crash reporting and ads SDK you include.
• Missing privacy policy URL. Publish it on your own domain before you submit.

FAQ

Can I skip the 14-day test with an organization account? The testing requirement documented by Google applies to personal accounts created after November 13, 2023. Organization accounts have their own verification requirements.

Can testers be friends and family? Yes. They need a Google account, must opt in to the closed test and should keep the app installed for the full 14 days.

Do I need a website? You need a privacy policy URL, and a simple website also gives you a support page and a place to link from the store listing.

Sources

1. Google Play: Get started with Play Console (registration fee and account types)
2. Google Play: App testing requirements for new personal developer accounts
3. Android Developers: Target API level requirements
4. Google Play: Store listing character limits
5. Google Play: Preview assets (icon, feature graphic, screenshots)
6. Android developer verification

Last verified: October 9, 2026. Prices, limits and policies come from the official pages listed under Sources, not from hands-on testing. Providers change them often, so confirm on the provider's own page before you buy. Spotted something out of date? Tell us.