( Guide )
How to Publish an App to the App Store and Google Play: Costs, Steps and Timing
How to publish an app to the App Store and Google Play: Apple's $99 a year, Google's one-time $25, commissions, review times and what to prepare.

( The Short Answer )
Publishing an app costs $99 a year for the Apple Developer Program and a one-time US$25 for a Google Play developer account, as of November 2026. Apple says it reviews 90% of submissions in under 48 hours; Google publishes no typical figure and says review for certain accounts can take seven days or longer. A new personal Google account must first run a 14-day closed test with 12 testers. Build prices are in the app cost guide.
Getting an app into the App Store and Google Play is a separate job from building it: two developer accounts, two listings, two sets of privacy answers and two reviews. Every fact below comes from Apple's and Google's own pages, read on November 15, 2026, and links to the page that states it.
What does it cost to publish an app on the App Store and Google Play?
Publishing an app costs $99 a year for the Apple Developer Program and a one-time US$25 registration fee for a Google Play developer account, so $124 for both stores in the first year (arithmetic from the two fees). Apple's enrollment page states the fee as 99 USD per membership year and offers a waiver to nonprofits, accredited educational institutions and government entities that qualify. Both stores also keep a share of digital sales:
| Cost | Apple App Store | Google Play |
|---|---|---|
| Developer account | $99 a year (Apple) | US$25, once (Google) |
| Digital sales, reduced rate | 15% on paid apps and in-app purchases in the Small Business Program: up to 1 million USD in proceeds the prior year, and new developers | 10% plus a 5% billing fee on the first $1 million (USD) of yearly earnings (service fees) |
| Digital sales, standard rate | "The standard commission rate"; the program page prints no figure. On subscriptions you receive 70% of the price in a subscriber's first year and 85% after | Subscriptions 10% plus a 5% billing fee; other purchases 20% plus 5% for installs on or after June 30, 2026, 25% plus 5% for earlier installs |
| Physical goods and services | Paid for outside in-app purchase, such as Apple Pay or card entry (guideline 3.1.3(e)) | Google Play's billing system must not be used (Payments policy) |
The commissions apply to paid apps and digital purchases inside an app. An app that takes bookings or sells products collects those payments through a card processor instead, and Apple's guideline 3.1.1(a) lets apps on the United States storefront include buttons and links to other ways to buy. Google adds that 97% of developers distribute their apps at no charge. Build prices are in the Flutter app cost guide.
What do you need before you submit an app?
You need a developer account with each store in the business's own name, a store listing, screenshots, a privacy policy, each store's privacy answers and an age rating. Open the accounts first, because verifying a company takes the longest.
To enroll as an organization, Apple asks for a legal entity (it does not accept DBAs, fictitious business names, trade names or branches), a D-U-N-S Number, a work email on the company's domain, a public working website and an enrolling person with authority to sign for the company. The organization's name then shows as the seller on the App Store; an individual enrollment shows a personal legal name. A D-U-N-S Number is free from Dun & Bradstreet, and Apple says to allow up to 5 business days to receive one and up to 2 more for the details to reach Apple.
Google Play offers personal and organization accounts and tells a business to choose the organization type, which also requires a D-U-N-S number. Then prepare the listing:
- Name and description. A name of up to 30 characters and a description of up to 4,000 in the App Store; the same limits on Google Play, plus a short description of up to 80.
- Screenshots. Apple requires at least one and allows up to 10 per device size (screenshot specifications); Google requires at least two and allows up to 8 per device type (preview assets).
- Privacy policy. Apple requires a link to it in App Store Connect and inside the app (guideline 5.1.1); Google requires a link on the store listing and within the app (Prepare your app for review).
- Privacy answers. Apple's app privacy details are required to submit new apps and updates and must cover third-party code in the app. Google's Data safety form is required of every developer with a published app, including apps that collect no data.
- Age rating. Apple generates it from a questionnaire, and an unrated app cannot be published on the App Store. Google requires its content rating questionnaire for each new app and says apps without a rating will be removed.
- Access for reviewers. A working demo account if the app has a login, a support URL for Apple and, for Google, declarations on ads and the target age group.
How long does app review take?
Apple says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours; Google publishes no typical figure and says some reviews can take seven days or longer. Apple's figure is on its App Review page. Google's publishing page says only that certain developer accounts get a longer review, of up to seven days or longer in exceptional cases. Review is one of several waits:
| Step | Published time | Source |
|---|---|---|
| D-U-N-S Number for a company | Up to 5 business days from Dun & Bradstreet, then up to 2 business days to reach Apple | Apple |
| Apple App Review | At least 50% of submissions in less than 24 hours and 90% in less than 48 hours | Apple |
| Google Play app review | No typical figure; up to seven days or longer in exceptional cases for certain accounts | |
| Google closed test, new personal accounts | At least 14 days with 12 testers | |
| Google production-access review, new personal accounts | Usually seven days or less |
Apple will consider an expedited review for a critical bug fix or a release tied to an event. On Google Play, managed publishing holds an approved update until you choose to publish it. Set a launch date with a margin, because a rejection means fixing the issue and submitting again.
What does Google require of a new personal developer account before production?
Google requires personal developer accounts created after November 13, 2023 to run a closed test with a minimum of 12 testers who have been opted in continuously for at least 14 days before applying for production access. That is the wording of Google's testing requirements page. Until then, the Production and Pre-registration features in Play Console stay disabled.
- The 12 testers must still be opted in on the day you apply, and have been for the 14 days before it without a break.
- The application asks about the closed test, the app and its readiness for production, and you must summarize the feedback testers gave.
- Google says it usually reviews the application in seven days or less, and may ask for more testing if fewer than 12 testers stayed opted in or they barely used the app.
The page is written for personal accounts and does not mention organization accounts. Google's pages do not say in so many words that organization accounts skip the test, so check the Production page in Play Console as soon as the account opens.
Why do apps get rejected, and how do you avoid it?
The best-documented cause is an unfinished app: Apple says over 40% of unresolved review issues relate to guideline 2.1, App Completeness, which covers crashes, placeholder content and incomplete information. Apple's App Review page lists the other common issues, and Google's publishing tips name much the same ones:
- Crashes, bugs and broken links. Google's Broken Functionality policy rejects apps that do not work as expected; Apple's guidelines want final versions with working URLs and the backend switched on.
- No way in for the reviewer. Both stores ask for a working demo account when the app has a login. Without one, Google says it cannot review the app.
- A listing that does not match the app. Apple wants screenshots that show the app in use, not a title or login screen (guideline 2.3.3). Google rejects misleading, irrelevant or excessive listing text under its Metadata policy, and apps missing a feature the listing promises.
- Privacy gaps. A missing or vague privacy policy, data requests that do not explain themselves and, on Apple, no way to delete an account inside an app that lets people create one (guideline 5.1.1).
- Too little app. Apple's guideline 4.2 turns away apps that are little more than a repackaged website, and guideline 4.3 turns away copies of what is already widely available.
- The wrong payment method. Digital features unlocked inside an app must use Apple's in-app purchase (guideline 3.1.1) and, on Google Play, Play billing.
To avoid them, test the release build on real phones, fill in every field, write reviewer notes for anything that is not obvious and supply a login that works. If Apple still says no, you can fix and resubmit or appeal to its App Review Board. Google says to fix the issue and resubmit, and warns that repeated rejections may lead to a suspended app.
What happens after an app is live?
Every update is reviewed again, both stores let you release an update to a share of users first, and each year's new iOS and Android versions bring build requirements the app has to meet.
- Apple phased release. An update can go out over 7 days to 1%, 2%, 5%, 10%, 20%, 50% and then 100% of users with automatic updates on. You can pause it for up to 30 days in total, and anyone can still download the update by hand (Apple).
- Google staged rollout. You pick the percentage of users who get the update and raise it yourself. It does not increase automatically, can be halted, and works for updates only, not a first release (Google).
- Yearly requirements. Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK (Apple). From August 31, 2026, new apps and updates on Google Play must target Android 16 (API level 36), with an extension to November 1, 2026 on request (Google).
An app left alone falls behind those requirements and cannot ship even a small fix until it is brought up to date, so upkeep belongs in the budget. The Flutter vs native guide compares upkeep on one codebase and on two, and a product that works in a browser needs no store review at all (web app cost guide).
How does American Web Guild handle an app release?
American Web Guild submits each app from the client's own Apple Developer and Google Play Console accounts, prepares both listings and answers the reviewers' questions. Release is part of our mobile app development work: the listing text, screenshots, age rating and privacy answers are prepared with you, and we reply when App Review or Google Play asks for a change. Whether an app is approved is decided by Apple and Google.
Every app is quoted from its written scope: fill in the form and a fixed price comes back in writing within 24 hours. The account fees and any commission are paid by you to Apple and Google directly. A focused first version is usually three to six weeks of build, and review by Apple and Google comes after that.
The code, the designs and the store listings are yours once the final invoice is paid, and the developer accounts are in your name from the start. We build in Flutter first, so one codebase covers iPhone and Android, with native Swift and Kotlin or React Native where the product calls for it. A care plan after launch covers the yearly iOS and Android updates, and an NDA can be signed before you describe the product.
Frequently asked questions
- How much does it cost to publish an app on the App Store?
- The Apple Developer Program costs $99 a year, which Apple's enrollment page states as 99 USD per membership year. On digital sales, Apple's Small Business Program charges a 15% commission on paid apps and in-app purchases for developers with up to 1 million USD in proceeds the prior year and for new developers. Figures checked November 15, 2026.
- How much does a Google Play developer account cost?
- A Google Play developer account costs a one-time US$25 registration fee. On purchases by users in the United States, Google's service fee is 10% plus a 5% billing fee on a developer's first $1 million (USD) of yearly earnings, and Google says 97% of developers distribute their apps at no charge. Figures checked November 15, 2026.
- How long does Apple take to review an app?
- Apple's App Review page says it typically reviews at least 50% of submissions in less than 24 hours and 90% in less than 48 hours. Apple reviews every update as well as every new app, and you can ask for an expedited review for a critical bug fix or a release tied to an event.
- How long does Google Play take to review an app?
- Google publishes no typical review time. Its publishing page says that for certain developer accounts review can take up to seven days or longer in exceptional cases. A new personal account also has to finish a closed test and a production-access review first, which Google says usually takes seven days or less.
- Do I need a D-U-N-S Number to publish an app?
- Yes, if the account is in a company's name. Apple requires a D-U-N-S Number to enroll an organization, and Google Play requires one to create an organization account. The number is free from Dun & Bradstreet, and Apple says to allow up to 5 business days to receive it. Neither page asks individuals for one.
- What is Google Play's 12-tester rule?
- Google requires personal developer accounts created after November 13, 2023 to run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access (Google's testing page). Google says it usually reviews that application in seven days or less. The page does not mention organization accounts.
















