Read from Apple’s and Google’s own pages
How to publish an app on the App Store and Google Play: the steps, the cost, and how long review takes
To publish an app on the App Store, you join the Apple Developer Program, set the app up in App Store Connect, answer Apple’s questions about it and submit it for review. Google Play works the same way, with its own account and its own review. Apple says it reviews most apps within two days. Both stores also say what slows an app down, and much of it is something you can have ready before you press submit. Here are the steps for each store, what it costs, how long review takes, and a checklist, from Apple’s and Google’s own pages.
The short version
- You need a developer account with each store. Apple: “The Apple Developer Program is 99 USD per membership year.” Google: “There is a US$25 one-time registration fee.”
- A company should enrol as a company. Apple shows the organisation’s name as the seller, and checks it with a D-U-N-S number.
- Have these ready before you submit: a support link and a privacy policy, a demo login if the app has a sign-in, no placeholder content, and Apple’s age rating, privacy and accessibility answers.
- Apple’s review is usually quick. It typically reviews “at least 50% of submissions in less than 24 hours and 90% in less than 48 hours”.
- Google’s can take longer. Google says “a few hours or up to seven days (or longer in exceptional cases)”, and new developer accounts can get a longer review.
- New personal Google Play accounts test first. At least 12 testers, for at least 14 days, before the app can go public.
- From 16 November 2026, Apple’s age rating questionnaire has two new questions.
How to publish an app on the App Store, step by step
- Join the Apple Developer Program. Apple’s enrolment page says: “The Apple Developer Program is 99 USD per membership year. Prices may vary by region and are listed in local currency during the enrollment process.” We set out what that comes to in pounds in how much an Apple developer account costs in the UK.
- Enrol as your business, if you are one. A limited company enrols as an organisation. Apple says: “Your organization’s name will be displayed as the seller name of your apps on the App Store.” The organisation must be “a legal entity that can enter into contracts with Apple”, and “We do not accept DBAs, fictitious business names, trade names, or branches.” It also needs a D-U-N-S number “so that we can verify your organization’s identity, legal entity status, and address”; we explain what a D-U-N-S number is and how to get one free. A sole trader enrols as an individual: Apple’s page groups an “individual or sole proprietor/single person business” together.
- Build it with Apple’s current tools. Apple’s Upcoming Requirements page says that since 28 April 2026, apps uploaded to App Store Connect “must be built with Xcode 26 or later”, and since 9 September 2026, iPhone and iPad apps “must target iOS 13 or later”. Apple’s submitting page lists higher minimums from April 2027, which we covered in iPhone Duo apps. Whoever builds your app handles this, but it’s worth asking them.
- Set the app up in App Store Connect. Your app’s details, and the answers Apple asks for, all go in there. Before you submit, Apple’s submitting page says to: “Complete the age rating questionnaire.” “Provide your app’s privacy details.” “Indicate your accessibility support.” The privacy details cover what any outside code in your app does with data too, and they are “required in order to submit new apps and app updates to the App Store”.
- Test it on real phones. Apple’s TestFlight puts the app on testers’ iPhones before it’s public. We covered it in what is an MVP.
- Fill in the review information, and submit. Apple’s App Review page says: “If some features require signing in, provide a valid demo account username and password.” Of settings, accounts and special instructions, it adds: “If you don’t include this information, the app review process may be delayed and your app may not pass review.”
- Wait for review, then release. “You’ll be notified by email of status changes.” For an app tied to an event, Apple recommends you “plan and schedule the release of your app in App Store Connect”.
How to publish an app on Google Play
Google’s “Get started with Play Console” guide sets out the account side in six steps:
- Sign up with a Google Account. “You must be at least 18 years of age to sign up for a Play Console account.”
- Accept the Developer Distribution Agreement.
- Pay the registration fee. “There is a US$25 one-time registration fee.” Google adds: “Google Play does not accept prepaid cards.”
- Choose a personal or organisation account. Google offers “two developer account types, personal and organisation”. For a business publishing its own app, we’d choose organisation. The choice decides what you’re asked to verify in step 5, and whether step 6 applies at all.
- Verify who you are. Google warns that “you may be asked for a valid government ID and a credit card, both under your legal name. If this information is determined to be invalid, your registration fee will not be refunded.”
- On a personal account, test first. Google’s guide marks this step “(personal accounts only)”. Its testing requirements say: “Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days.” Personal account owners also “must verify access to an Android device using the Play Console mobile app before publishing apps”.
Then the app itself. Google’s “Prepare your app for review” page covers the App content page, where you make the “mandatory safety, policy, and legal declarations before publishing”: your privacy policy, whether the app shows ads, instructions for reaching anything behind a login, the target audience, content ratings, and the app’s privacy and security practices. Then you prepare a release and send it for review. Google’s publishing page notes: “Your changes are not automatically sent for review.”
How much does it cost to put an app on the App Store?
The stores’ own fees are small. Building the app is the bigger cost, and that depends on the app.
| App Store | Google Play | |
|---|---|---|
| Account fee | 99 US dollars a year, charged in local currency | US$25, once |
| Account for a business | Organisation, checked with a D-U-N-S number | Organisation (the other type is personal) |
| Testing before the app can go public | No tester minimum on the pages we read | Personal accounts created after 13 November 2023: 12 testers for 14 days |
| How long review takes | Typically under 24 hours for at least half, under 48 hours for 90% | A few hours to seven days, longer in exceptional cases |
From Apple’s enrolment and App Review pages, and Google’s “Get started with Play Console”, testing requirements and review pages.
One exception on Apple’s side: “If you’re a nonprofit organization, accredited educational institution, or government entity and meet certain requirements, you can request a fee waiver”.
How long does App Store review take?
Usually a day or two. Apple: “App Review works around the clock, typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours.” The same page warns: “If your submission is incomplete, review times may be delayed or your submission may not pass.”
If you’re in a hurry for a good reason, Apple lets you ask for an expedited review “if you face extenuating circumstances, such as fixing a critical bug in your app or releasing your app to coincide with an event you’re directly associated with.”
And on Google Play?
Google gives a range rather than an average. Its page on reviews says: “Processing can take a few hours or up to seven days (or longer in exceptional cases), as it depends on the review time that your app is subject to.” Its publishing page adds: “For certain developer accounts, we’ll take more time to thoroughly review your app to help better protect users.” Google gives one example of apps “subject to extended review times, such as apps submitted by new developer accounts.”
One Google detail worth knowing before launch week: “if you submit a change while there are changes in review, your app may be pushed to the back of the app review queue.” So send your changes together, and leave them alone while they’re in review.
Why apps get rejected, and how to avoid it
Apple puts a number on one cause, the unfinished app: “On average, over 40% of unresolved issues are related to guideline 2.1: App Completeness, which covers crashes, placeholder content, incomplete information, and more.” Guideline 2.1 in the App Review Guidelines says submissions “should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission.” If the app has a login, include demo account details “(and turn on your back-end service!)”.
The other common problems on Apple’s list:
- Missing links. “A link to user support with up-to-date contact information and a link to your privacy policy is required for all apps.”
- Placeholder content. “Items that are still in progress and contain placeholder content are not ready to be distributed and cannot be approved.”
- Promising what it doesn’t do. “Your app must perform as advertised and should not give users the impression the app is something it is not.”
- A website in an app. “Websites served in an iOS app, web content that is not formatted for iOS, and limited web interactions do not make a quality app.” We covered this in turning your website into an app.
- The wrong name on it. “Certain types of apps must be submitted by the legal entity that provides the services rather than an individual developer.” Apple’s examples include “banking and financial services, cryptocurrency, healthcare, gambling, and air travel”.
Google’s tips for getting published cover the same ground. If parts of the app need a login, provide “an active demo account, valid login information, and any other resources needed for Google Play to review your app”. And the listing has to match the app: “if we notice a discrepancy between what is promised in your store listing and what your app actually delivers (for example, if a feature described in your store listing is not present in your app), it may be rejected.” Google also warns that “multiple rejections may lead to your app getting suspended”, so it’s worth testing properly before you send it.
The privacy policy, in particular
Both stores want it. Google says: “You must link to a privacy policy on your store listing and within your app, even if your app doesn't access personal or sensitive user data or target children.” To avoid delays, Google’s review page says it must be on a public web address with a valid SSL certificate, reachable from anywhere without a login, “displayed on a standard, non-editable webpage (not a PDF or downloadable file)”, and written for that app specifically.
Added 13 November 2026: what Apple, Google and UK law say goes in the policy, and the two lines UK law added this year, are in privacy policy for an app.
New from 16 November: two more age rating questions
Apple announced on 2 November: “Starting November 16, 2026, App Store Connect will include new content descriptors”. When you fill in the age rating questionnaire, you’ll be asked whether your app includes “Shared Location” (“Sharing of real-world location with another person or group.”) and “Dating and Relationships”.
Apple says: “You must provide these declarations when submitting an app update or making changes to your age rating questionnaire. All apps must have these declarations completed by January 12, 2027.” So anyone submitting from 16 November meets the two new questions. Answer them from what the app actually does.
A checklist before you press submit
Putting Apple’s and Google’s pages together, this is our checklist:
- Developer accounts in your business’s name, with each store you’re publishing to.
- A working support page with up-to-date contact details.
- A privacy policy on a public web page, not a PDF, written for this app, and linked both in the listing and inside the app.
- A demo account for the reviewers if the app has a sign-in, with the systems behind it switched on.
- No placeholder text or images, and every link working.
- Screenshots and a description that match what the app actually does.
- Apple’s answers done: age rating (including the two new questions), privacy details and accessibility. Google’s App content declarations done.
- On a new personal Google Play account, 12 testers for 14 days before you can apply to publish.
- Time in the plan: usually a day or two for Apple, and up to seven days for Google, longer for some new accounts.
Whose name the app goes out under
Publish under your own business’s developer accounts. On the App Store, your organisation’s name is shown as the seller. If someone else builds the app for you, ask them to publish it under your accounts, not theirs. We covered what else to agree in what to check before you hire an app developer.
What argues the other way
- Apple’s review figures are typical, not promised. The page says “typically”, and doesn’t say how long the slowest 10% take.
- Google doesn’t say which accounts get a longer review. It says “certain developer accounts”, and gives new ones as an example.
- The rules change often. Apple’s submitting page already lists the April 2027 minimums, but its Upcoming Requirements page doesn’t yet. Everything here is as we read it on 9 November 2026.
- Our interest. We build apps for UK businesses, so a post saying preparation matters suits us. Everything quoted here is from Apple’s and Google’s public pages, and any developer can read them.
Sources, and what we checked
- Apple: the App Review page; “Submitting”; “Enroll” in the Apple Developer Program; Upcoming Requirements; the App Review Guidelines (the page says “Last Updated: October 16, 2026”), guideline 2.1; and Apple’s 2 November 2026 news item on the new age rating descriptors.
- Google Play Console Help: “Get started with Play Console”; “App testing requirements for new personal developer accounts”; “Prepare your app for review”; “Publish your app”; “Control when app changes are reviewed and published”; and “Helpful tips to get your app published on Google Play”.
- Apple’s pages and some of Google’s are in American English, so quotes keep “organization”, “enrollment” and “November 13, 2023”. We keep each source’s own punctuation inside quotes, including Google’s straight apostrophe in “doesn't”.
- All of the pages above were read in full on 9 November 2026, and again on 11 November 2026, the morning we published. Every quotation was checked word for word against the page it comes from.