How to Publish an Android App in 2026: A Developer’s Checklist

The short version

Publishing on Google Play in 2026 takes 4 to 8 weeks. Google killed the old “upload an APK and go live” workflow in late 2023. Every new personal account now needs identity verification, a real 14-day closed test with 12 active testers, and a production access questionnaire that punishes vague answers. Here’s the checklist, in the order you’ll actually do it.

Phase 1: Before you write code

1. Validate first. Spend a week on Play Store hunting your idea and reading 1-star reviews on competitors. Talk to five real users. Cheap insurance against months of dead code.
2. Pick your stack. Native Kotlin if you want full Android APIs and no surprises. Flutter or Kotlin Multiplatform if you’re shipping both platforms from one codebase. React Native if your team already lives in JS. Cordova in 2026 is a no.
3. Define the MVP, then cut half of it. Whatever you think “minimum” is, it isn’t. Cut. You can always add features after launch. You can’t get launch time back.

Phase 2: Get the Play Console ready

4. Create your Play Console account at play.google.com/console. $25 one-time. Use a card you actually own.
5. Kick off identity verification on day one. Google checks your name, address, and gov ID before letting you publish. Could be 24 hours, could be 3 weeks. Assume 3 weeks.
6. Personal or organization? Solo dev = personal. Registered business = organization (you’ll need a DUNS, which is its own annoyance, but it makes your listing look legit).

Phase 3: Build (and actually test)

7. Ship the MVP. Whatever framework you picked, build the smallest thing that solves the problem. No gold-plating.
8. Generate a signed AAB. Run ./gradlew bundleRelease or use Android Studio’s “Generate Signed Bundle” flow. AAB only. Google Play doesn’t accept APK for new apps anymore.
9. Back up your signing key. Then back it up again. Lose this and your app is dead forever. Password manager. Cloud drive. Offline copy. All three.

Phase 4: Store listing prep

10. App title (30 char max). Lead with your primary keyword. “Note Taking” beats “Memorable Moments” every time for ASO.
11. Short description (80 char max). Your elevator pitch on the search results page. Don’t waste it.
12. Full description (4000 char max). Open with the problem you solve. Features in scannable lists. Social proof if you have it.
13. Icon (512×512 PNG). Simple. No text. Test that it reads at 48px because that’s how users see it.
14. Screenshots (min 2, ideally 8). Phone, 7-inch tablet, 10-inch tablet sets. Add captions inside the screenshots. Apps that do this convert way better.
15. Feature graphic (1024×500 PNG). The banner at the top of your listing. One clear value prop, not a busy collage.
16. Privacy policy. Generate one at termly.io if you don’t have one. Host on your own domain or GitHub Pages. Google rejects Google Docs URLs.
17. Content rating questionnaire (IARC). Be honest. UGC features? Say so. Get this wrong and you’ll be reuploading.
18. Data safety form. Declare every data type you collect, where it goes, whether it’s shared. Match exactly what your privacy policy says or you’ll get flagged.
19. Target audience and age group under Policy. This decides what ads, features, and content rules apply to your app.
20. Pricing and distribution. Free or paid? Which countries? You can change later, but pick something for launch.

Phase 5: The 14-day closed testing wall

This is where most first-time Android devs eat it. Google’s closed testing rules require 12 active testers for 14 consecutive days before production access. Recruiting them through Reddit or Telegram is slow and unreliable.

Testers Community handles this entire phase for you:

21. Upload to Internal Testing first to validate your build before sharing externally.
22. Hand the closed test to TC. Free credit-based community of 50,000+ devs, or $15 for 25 verified testers in 6 hours with automatic drop-off replacement.
23. Get a feedback report + production form help, backed by a 100% Production Access Guarantee. Money back if Google rejects.

Phase 6: Request production access

24. Submit the request. Play Console → Setup → Production access.
25. Answer the questionnaire properly. This is where ~60% of rejections happen. Be specific: who tested (count, demographics, devices), how they tested (features, frequency), what you changed. “We tested with 12 users and fixed bugs” gets rejected instantly.
26. Wait 3 to 7 days. Sometimes faster, sometimes slower.
27. Handle rejection feedback if it comes. Most rejections are “not enough testing detail.” Reread the response, give specifics, resubmit. Don’t argue with the bot.

Phase 7: Ship it

28. Start your rollout at 20%. Catch crash issues before they hit everyone. Wire up Firebase Crashlytics if you haven’t.
29. Monitor daily for the first week. Read every review. Respond to every review. Patch critical bugs same-day.
30. Bump to 100% once crash-free user rate is above 99% and reviews look stable.

What about iOS?

Most teams ship both. iOS is similar but quicker:

• Apple Developer Program is $99/year, not one-time
• No mandatory 14-day testing window like Android has
• App Review usually takes 24 to 48 hours, way faster than Google
• Stricter rules on design and anything that competes with Apple’s payment revenue

Flutter, React Native, or KMP let you ship from one codebase. The per-platform work is mostly signing, certificates, and store listings.

How long it actually takes

Step	Time
Identity verification	1 to 3 weeks (start this first)
Build and internal test	Your dev time
Store listing prep	1 to 3 days
Closed testing	14 days minimum
Production access review	3 to 7 days
Minimum past development	~4 weeks

First-time publishers: 6 to 8 weeks. Second time around you’ll cut that in half because you’ll know where the friction is.

5 ways devs eat it on first submission

Patterns across 50,000+ apps published through Testers Community:

1. Closed testing doesn’t hit 12 active testers for the full 14 days
2. Privacy policy missing or hosted somewhere Google rejects (Google Docs included)
3. Content rating questionnaire answered carelessly
4. Production access form filled with vague answers
5. Signing key lost (app becomes permanently un-updatable)

Avoid these and your first-submission approval odds jump from around 30% to over 90%. Start ID verification on day one. Budget 4 to 8 weeks between “ready to publish” and “live on Play Store.”

Stuck on closed testing? Testers Community helps devs clear the 14-day requirement fast. Free credit-based community of 50,000+ devs, Pack of Wolves for fast free testing, or $15 for 25 testers in 6 hours with a 100% Production Access Guarantee.