Launch Roadmap

Building the app is the easy part. Getting it live on Google Play has one rule that catches everyone off guard — so here's the realistic roadmap, start to finish, with the waiting periods built in. Follow it and you ship. Skip it and you stall.

The one thing to know up front: a brand-new personal Play Console account can't go straight to production. Google requires a closed test with 12+ testers, opted in for 14 continuous days, before you can even apply for production. So "launch this weekend" isn't a thing — launch is ~3 weeks out. That's normal. Plan for it.


The timeline at a glance

DAY 0 (before you build)     Create Play Console account ($25) + verify identity  (1–3 days)
WEEKEND                      Build the app + finish the store listing + upload to CLOSED TESTING
DAY 3–4                      Get 12 testers opted in
DAY 4 → DAY 18               14-day test clock runs  ←  fix tester feedback + marketing prep
DAY ~18                      Apply for production access
DAY ~21–25                   Google review → LIVE on Play 🎉

Three weeks from build to live. Heads up: you must finish the store listing (screenshots, descriptions, Data Safety, privacy) before you can start the closed test — Play won't let you start one until "Set up your app" is complete. So the 14-day wait isn't for the listing; it's for tester feedback + marketing prep.


Phase 0 — Before you build (do this first, it's the long pole)

  • Create a Google Play Console account — $25 one-time. Do this days before you build: identity verification can take 1–3 days, and you can't publish until it clears.
  • Personal vs Organization account: personal accounts have the 12-tester rule. Organization accounts skip it but need a D-U-N-S number (harder to get). For a first app, personal is fine — the roadmap handles the tester rule.
  • Set up your machineSetup macOS, Setup Windows, or Setup Linux, then /kit-env-check until it's green.

Phase 1 — Build (the weekend)

This is where NowKit does the heavy lifting:

  1. /kit-start-setup — rename, brand, auth, paywall, analytics, first run
  2. /kit-design-app — your screens (layout → data)
  3. /kit-run-app — running on your device

End of weekend = a working app on your phone. Not live yet — that's expected.

→ Pick the path closest to your app from the Example Recipes.


Phase 2 — Upload to closed testing (weekend / day 3)

/kit-publish-to-play

It walks signing, the listing, screenshots, Data Safety, and the upload. Upload to the Closed testing track (not production). This is the build your testers will install.


Phase 3 — Get your 12 testers (day 3–4)

This is the step that stops most people. The fix: don't recruit 12 strangers — use a shared tester pool. Full how-to (Play Console steps, Google Group, pitfalls): Closed Testing.

  • Join the cohort tester Google Group (your group will share the address).
  • On your app's Closed testing track → Testers → add that Google Group email.
  • Everyone in the cohort does the same → everyone instantly has 12+ testers.
  • Each tester opens the opt-in link once and installs the app. That's it.

The 14-day clock only counts days where you have 12+ testers opted in. Get everyone opted in early so the clock starts on day 4, not day 10.


Phase 4 — The 14-day wait (day 4 → 18) — work, don't idle

The clock is running. Your store listing is already done (that's what let you start the closed test). Use these two weeks for the rest:

  • Collect tester feedback → fix the top 3 issues → push updates to the closed track.
  • Marketing prep — plan your launch posts, socials, and any landing-page copy.
  • /kit-plan-release-analytics — wire your funnel events before launch (if not done).
  • /kit-pre-register-setupoptional, but this is the moment. Put the app on Google Play pre-registration so it's public before launch, collecting sign-ups (and auto-installs on launch day). It reuses the AAB you already uploaded and can attach a reward. Turn it on 3–6 weeks before launch; you must then launch within 90 days.

By day 18 you want: tester feedback addressed, a stable build, marketing ready.


Phase 5 — Apply for production (day ~18)

Once you've had 12+ testers for 14 continuous days, Play Console shows the "Apply for production" option. Fill the short form (why your app is ready). Submit.


Phase 6 — Live (day ~21–25)

Google reviews production access + your first release (hours to a few days). When it clears, your app is live on the Play Store. 🎉


Your launch checklist

  • Play Console account created + identity verified
  • Machine green (/kit-env-check)
  • App built + running on device
  • Screenshots + store listing + privacy policy + landing page done (before the test)
  • "Set up your app" checklist 11/11 complete
  • Signed AAB uploaded to Closed testing
  • 12+ testers opted in (shared group)
  • 14-day clock started
  • (Optional) Pre-registration turned on (/kit-pre-register-setup)
  • Tester feedback addressed
  • Applied for production
  • Live on Play

Stuck on any step for more than a day? That's the signal to ask — in the cohort group, or the NowKit community. Most stalls are one stuck setting, not a real wall.