We put an app through both stores this year. The build was the easy part. This is the rest of it — the accounts, the fees, the testing gate nobody warns you about, and what review is really checking.
There is a specific disappointment that hits the week after an app is finished. The thing works. It is on your phone. And it turns out that was the fast part.
This article is about the slow part, written by a team that has just been through it: Oppermind’s own app went live on the App Store in late August 2026 and is listed on Google Play. What follows is the process as it actually stands, with every figure taken from Apple’s and Google’s own pages on the date shown.
Ask this before spending a cent. If your app can run in a browser, a progressive web app installs to a phone’s home screen from a URL, with no store, no fee, no review and no waiting. For a great many small tools it is the right answer, and publishing to the web is the shorter road.
Go to the stores when you need what only they offer: presence in the device’s own search, push notifications on iOS, in-app purchase through the platform, access to hardware a browser cannot reach, or simply the credibility of a listing. Those are real reasons. “Because that is what apps do” is not.
| Apple App Store | Google Play | |
|---|---|---|
| Programme | Apple Developer Program | Google Play Console developer account |
| Fee | US$99 per membership year | US$25 one-time registration |
| Fee waiver | Eligible non-profits, accredited educational institutions and government entities can request one | Not stated on the registration page |
| Identity | Verification during enrolment | Verification during setup; new personal accounts must also verify access to an Android device via the Play Console app |
| Before you can publish | Submission and review | New personal accounts: closed test with 12+ testers for 14 continuous days, then apply for production access |
| Testing tool | TestFlight, included | Internal, closed and open testing tracks |
Both fees are in US dollars. What lands on an Australian card depends on the rate on the day, plus whatever your card issuer adds for a foreign transaction.
This is the step that catches solo developers. If your Google Play developer account is a personal one created after 13 November 2023, you cannot go straight to production. Google’s own requirement is precise: “At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days.” After that, you answer questions about your testing process, your app’s design and its production readiness before access is granted.
Read that as a calendar, not a checkbox. You need twelve real people with Android devices who will install a test build and leave it installed for two weeks, and you need them lined up before the app is finished, because the fortnight cannot start until it is. Organisation accounts are treated differently; if you are publishing for a business, that is worth knowing before you create the account.
Both stores publish their guidelines and both expect you to have read them. In practice the first-submission rejections cluster around a short list:
An unglamorous list, and a surprisingly large amount of work if you leave it to the end.
| Step | Plan for |
|---|---|
| Account creation and identity verification, both stores | Days; sometimes longer if verification queries |
| Google closed test (new personal accounts) | 14 continuous days minimum, plus the time to recruit 12 testers |
| Assets, listing copy, privacy policy, declarations | A solid week if you are doing it properly |
| First review, each store | Usually days; sometimes longer |
| At least one rejection and resubmission | Normal. Budget for it. |
Add that up and “finished on Monday, live by Friday” is not a plan for a first submission. Weeks is the honest unit.
Oppermind does not submit apps to the stores for you — nothing does; that happens in Apple’s and Google’s own consoles under your own account. What the workspace covers is everything around the submission that eats the week: the icon and screenshot sets from one master in the image editor, the caption frames in the design canvas with your Brand Kit applied when you tag it, the store listing and privacy policy as documents, the release-notes pattern you reuse every version, and the tester-recruitment tracker as a sheet. For the app itself, if a progressive web app is the right first step, the code editor’s live preview and zero-setup static deploy get you to an installable URL without a store at all.
The Academy’s build live artefacts and custom tools covers the build side; one prompt, multiple files is the fastest way to get the listing copy, the policy and the notes out of one brief.
Free with no card, then Starter A$9.95, Pro A$29.99 and Pro Plus A$59.99 a month. Unlimited documents, spreadsheets, decks and designs on every plan.
Whatever you’re here to make, make more of it.
Store rules change, and they change without asking you. Fees, testing requirements, guideline wording and review behaviour are all Apple’s and Google’s to alter, and this article is a snapshot from the date shown, taken from their own pages. Before you commit money or a launch date, read the current versions. And keep your tester group: you will want them again for version two.
Apple’s Developer Program is US$99 per membership year. Google Play charges a US$25 one-time registration fee. Both are in US dollars, so the amount on an Australian card depends on the exchange rate on the day. Apple offers fee waivers for eligible non-profits, accredited educational institutions and government entities.
Not with a new personal account. Google requires personal developer accounts created after 13 November 2023 to run a closed test first: at least 12 testers opted in continuously for the preceding 14 days before you can apply for production access, plus questions about your testing and readiness. Budget those two weeks into the plan.
That the app does what the listing says, does not crash on first launch, handles the data it collects the way it declares, and complies with the store’s published guidelines on content, payments and privacy. Reviewers use a real device with a real account, so a demo login that works and clear instructions for the reviewer save a rejection.
If the app can live in a browser, a progressive web app gets you onto phones with no store, no fee and no review, and it is the right first step for most small tools. Go to the stores when you need what only they offer: presence in search on the device, push notifications on iOS, in-app purchase, or the credibility of a listing.
Plan for weeks, not days, even with a finished app. Account verification, Google’s 14-day closed test, first-submission review on each store, and at least one rejection-and-resubmit cycle are normal. The build is usually the fastest part of the whole process.
Fees, testing requirements and review practices are set by Apple and Google, are quoted from their published pages on the date shown, and change without notice; read the current pages before relying on any of them. US-dollar amounts are not converted and your actual charge depends on the exchange rate and your card issuer. This article is general information about app distribution, not legal, tax or financial advice, and does not take account of your circumstances; you are responsible for your app’s compliance with each store’s guidelines and with the privacy and consumer law that applies to you. Apple, App Store and TestFlight are trade marks of Apple Inc.; Google Play is a trade mark of Google LLC; Oppermind is not affiliated with, endorsed by, or sponsored by either. Oppermind does not submit apps to any store on your behalf. Oppermind platform prices are current as at 12 September 2026, are in Australian dollars, and are subject to the plan terms at checkout.
Icons, screenshots, listing copy, privacy policy and release notes — from one brief, in one workspace.