The Play Store, step by step (and why you no longer have to do it)
What Google asks a first-time developer in India — the account, the identity check, the fee, the twelve-testers rule. We handle all of it under our own account; this is for founders who would rather own the listing themselves.
You do not have to do any of this. We submit apps built here to the Play Store under our own developer account: no console for you to open, no fee to Google, no identity check, no fortnight of closed testing. The release fee covers that work.
This post stays up because some founders want to own the listing themselves — a company buying software, an agency, anyone who wants the app in their own name from day one. That is a fair thing to want, we will help you set it up, and these are the four things Google will ask you for.
1. A Play Console account in your own name
A one-off fee of roughly two thousand rupees, and an identity verification — for a personal account, official ID; for an organisation, registration documents and a D-U-N-S number, which itself takes time to obtain.
The account must be yours, not your developer’s. If somebody offers to publish your app under their account, understand what that means: the app is theirs, the reviews are theirs, and the customers are theirs if the relationship ends.
2. The twelve-testers rule, if that account is personal
A personal Play Console account opened recently must run a closed test with at least twelve testers who stay opted in for fourteen continuous days before it can apply to go to production.
This is the requirement that derails timelines. It is not a queue you can pay to skip, and it starts when you have twelve real people with Google accounts willing to install your app — which for a single-branch business is a real errand.
3. The API level floor
Google refuses uploads built for an older Android version than its current minimum, and that minimum rises every August. One build setting decides whether an upload is accepted or rejected with a message that does not obviously explain itself.
4. The store listing itself
A description, screenshots at the sizes Google wants, an icon, a feature graphic, a privacy policy at a public URL, and answers to a data-safety questionnaire about what your app collects. The questionnaire is a declaration; answering it carelessly is a compliance problem rather than a form-filling one.
The order we recommend, either way
- Build the installable file and send it to twenty customers by link. It needs no account, no fee and no review, and it is free.
- Find out whether people use it. Most businesses learn something here that changes the app.
- If they do, tell us to put it on the Play Store and we get on with it — or, if you want the listing in your own name, open the console and start the twelve-tester clock early, because it is the long pole.
And the part people skip
Your signing key. Google remembers the first key an app was signed with, forever. Lose it and you cannot update your own app — the only way forward is publishing a different app, with no installs and no reviews.
The key your app is built with here is generated once, kept in your own project, never in a database, and leaves with you when you go. Whoever builds your app, ask them where that key lives and how you get a copy. If they cannot answer clearly, that is the answer.
Build the thing this is about
Ask for access and a person reads it. You start with 300 free sparks, about forty changes.
Request access Take the free founder test
Access is by invitation and a person reads every request. The founder test is free, takes a few minutes, and tells you what you are getting before you commit to anything.