Sparround

What must be ready before launch

With vibe coding an app can be ready in a week. But getting into the store is not the same as the app being ready. The gap often takes weeks, and people are not prepared for it.

The two biggest surprises:

1. Google Play's personal-account rule. Google's documentation states it plainly: personal developer accounts created after 13 November 2023 must run a closed test with at least 12 testers, opted in continuously for at least 14 days, before the app is eligible for public distribution. Only then can you apply for production access. So on Play, "wrote it today, published tomorrow" is not possible — budget those two weeks into your plan.

2. Creating the accounts themselves takes time. Apple Developer Program membership is 99 USD per membership year; enrolling as an individual requires an Apple Account with two-factor authentication turned on, while enrolling as an organization additionally requires a D-U-N-S Number. On the Google Play side, registration is a one-time 25 USD fee.

ItemWhy it is neededHow early to start
Developer accountsVerification can take time; the D-U-N-S Number is a separate processAt least 3-4 weeks ahead
12 testers (Play only, new personal account)Google's explicit requirement: 14 continuous daysAt least 3 weeks ahead
A privacy policy pageBoth stores require it; you need a working URL1 week ahead
Data safety / privacy questionnaireYou must declare exactly what data the app collects1 week ahead
Store assets (icon, screenshots, copy)This is marketing work, not coding work — it takes time2 weeks ahead
A support channel (email / page)Shown on the store page; missing it risks rejection1 week ahead

Readiness on the product side. From a marketing point of view there are three questions to answer before launch:

  • What happens in the first 60 seconds after the app opens? If people see an empty screen, all your marketing spend is wasted
  • Does it crash? A single "won't open" comment in your first reviews keeps the rating down for a long time
  • Where does a user write when something goes wrong? An unanswered review is bad for both rating and ranking

These look like technical questions, but all three turn directly into marketing outcomes.

Practice. Plan backwards on a calendar: pick a launch date, then place every row of the table above onto it. If you have a new personal Play account, put the 12 testers + 14 days block at the very front. Done means: every item has a concrete date on the calendar, and the names of the 12 testers are written down.

📚 Sources and documentation