Disclosure: I work at ZoopCoder, an Indian development shop that sells a paid Play Store submission service. That price is at the bottom. Everything above it is the same thing I would tell you for free, and every fee in this post is paid to Google or Apple, not to us.
Someone asks "how much does it cost to publish an app on the Play Store" roughly every day. They get told "$25", they pay the $25, and then three weeks later they are still not live because of a rule nobody mentioned. Here are the real numbers as of September 2026, from doing this repeatedly for Indian clients.
1. The fee is US$25, once, and that is genuinely all of it
A Google Play developer account costs a one-time US$25 registration fee — about ₹2,400 on an Indian card at today's rate, plus whatever forex markup your bank adds. There is:
- no annual renewal — you pay once and the account is yours;
- no per-app charge — one account can hold as many apps as you want;
- no charge to push updates.
This is the single biggest difference from Apple, which charges US$99 every year and delists your app if you stop paying. If you are choosing which platform to ship first on a tight budget, that asymmetry matters more than any development cost.
The one thing Google does take is a service fee of 15–30% on in-app purchases and subscriptions — 15% on the first US$1M of yearly earnings for most developers. If your app takes money for physical goods or services delivered outside the app, that fee does not apply.
2. The cost that is not money: the 14-day, 12-tester clock
This is the one that ruins launch dates.
If your developer account was registered as a personal account after 13 November 2023, Google will not give you production access until you have run a closed test with at least 12 testers who stay opted in continuously for 14 days.
Read that carefully, because each clause bites:
- 12 testers — real Google accounts that actually opt in. Not 12 email addresses you own.
- 14 continuous days — the clock starts when the test starts, not when you apply.
- If testers drop below the threshold, the clock effectively restarts.
Organisation accounts (a registered company, D-U-N-S verified) are exempt from this entirely. If you are a registered company and you have a choice, register the developer account as the organisation on day one, not at the end of the project. It is free and it saves you two to three weeks.
Nobody can shorten this for you. Any service that offers to "provide testers" is offering you a policy violation — Google treats fake tester accounts as exactly that.
3. You cannot upload an APK, and you cannot target an old SDK
Two hard technical gates that catch people using app builders and free converters:
| Requirement | Since | What it means |
|---|---|---|
| Android App Bundle (.aab) | August 2021 for new apps | A plain .apk will be rejected at upload. |
| Target API 36 (Android 16) | Current Play requirement | Building against an older targetSdk blocks the upload, not just new features. |
If you exported your app from a free "website to app" tool, check both of these before you pay for anything else. A large share of those tools still emit an APK built against an older target API, and some do not let you supply your own signing key — which means you could never publish an update under your own account even if the first upload succeeded.
4. The five declarations that actually cause first rejections
The upload is the easy part. First submissions get bounced on paperwork far more often than on code:
- Data safety form that does not match reality. You declare what the app collects and shares. If your app pulls the advertising ID or device identifiers through an SDK you forgot about, and the form says it collects nothing, that is a mismatch and a rejection.
- Missing or unreachable privacy policy URL. It must be a live, public URL, on your own domain, reachable without a login.
- Wrong target-audience answer. Answering "children" pulls in a whole extra set of Families policy requirements. Answering it carelessly is a policy problem, not a form problem.
- App access credentials the reviewer cannot use. If any part of the app is behind a login, you must give a working demo account. Expired or 2FA-protected demo logins are a very common bounce.
- Content rating questionnaire (IARC) answered inconsistently with what the app actually does.
None of these need a developer to fix. All of them need someone to actually read the app's behaviour instead of clicking through the form.
5. A realistic end-to-end budget (Indian solo founder, app already built)
| Line item | Cost | Paid to | Frequency |
|---|---|---|---|
| Google Play developer account | US$25 (≈ ₹2,400) | Once, forever | |
| Privacy policy page | ₹0 if you write it yourself | — | Once |
| Store listing copy + screenshots | ₹0–₹5,000 | Designer, or yourself | Once |
| Console submission work | ₹0 if you do it yourself | — | Per app |
| Apple, if you also want iOS | US$99 (≈ ₹9,500) | Apple | Every year |
So: an Android-only launch for an app that already exists can genuinely cost you one payment of about ₹2,400 and a fortnight of waiting. That is the honest answer, and it is why I think "how much does it cost to publish an app" is usually the wrong question — the expensive parts are the app and the fourteen days, not the fee.
6. Where we fit, since I said I'd be upfront
If you would rather not spend an evening inside Play Console:
- ZoopCoder submits an app to Google Play for a fixed ₹1,999 — store listing, IARC content rating, Data safety form, target audience, app access declarations, the release itself, and the first round of Google's review feedback. Typically sent for review within 1–2 working days of getting the files. Details and scope: https://zoopcoder.com/services/play-store-app-publishing.php
- If what you are publishing is an existing website, we build it into a signed, Play-ready AAB targeting API 36 for a fixed ₹4,999: https://zoopcoder.com/services/website-to-android-app.php
The US$25 is still yours to pay to Google, the app is published under your account, and nobody — us included — can guarantee that Google approves it. Anyone who tells you otherwise is selling you something they do not control.
If the part you are actually worried about is the calendar rather than the console, we wrote up where the tester window fits into a real Android launch plan here: https://zoopcoder.com/guides/how-long-to-build-app-website-india.php
Numbers checked September 2026. If Google has changed a threshold since, the Play Console policy pages win over this post — tell me in the comments and I will correct it.
Top comments (0)