How to Publish an App on Google Play and the App Store: 2026 Guide

Publishing an app is not "upload a file and you're done": it's a process with costs, legal requirements, and two reviewers who apply different criteria. To publish an app on Google Play and the App Store in 2026 you need a developer account in each store (a one-time USD 25 with Google, USD 99 per year with Apple), a published privacy policy, the completed data forms, and you have to pass a review that takes anywhere from 24 hours to 7 days. This guide is the checklist we use at Deepyze every time we launch a client's app, no fluff.

Developer accounts: 2026 costs and requirements

	Google Play Console	Apple Developer Program
Cost	USD 25 (one-time)	USD 99 per year
Recommended account type	Organization	Organization
Requires D-U-N-S (companies)	Yes	Yes
Verification	Legal identity + tax details	Legal identity + person with signing authority
Setup time	1-7 days	2-14 days (depends on the D-U-N-S)
What happens if you don't renew	Nothing (one-time payment)	Your apps drop out of the App Store

Three important notes for companies in Argentina and LATAM:

• Payment is in dollars with a credit/debit card. From Argentina, add the current tax withholdings on foreign-currency purchases to your budget. There's no way to pay in pesos.
• The D-U-N-S is free and issued by Dun & Bradstreet, but getting one from scratch can take up to two weeks. If you're launching as a company, request it before the app is ready — it's the most common bottleneck.
• Personal vs. organization account: publishing under your own name is faster, but the owner's name is exposed, migrating the app later is a hassle, and on Google, new personal accounts have an extra requirement: a closed test with at least 12 testers over 14 days before you can publish to production. For a company, the organization account is the only serious option.

What to prepare before submitting (the part everyone underestimates)

80% of rejections are avoided by preparing this before you touch "submit for review":

1. Privacy policy published at your own URL, in your audience's language, stating what data you collect and why. Mandatory in both stores even if your app "doesn't collect anything."
2. Data forms: Data Safety on Google Play and Privacy Nutrition Labels in App Store Connect. They have to match what the app actually does — reviewers cross-check network traffic against what you declared.
3. Screenshots in the required sizes: for iOS, 6.7"/6.9" iPhone captures (and 13" iPad ones if your app runs on tablet); for Android, at least 2 captures, a 512 px icon, and a 1024×500 feature graphic.
4. Demo account for the reviewer if your app requires login. A working username and password, added to the review notes. It's the number-one avoidable rejection reason at Apple.
5. Store listing: title (30 characters), short and long descriptions, category, and a content rating completed honestly.
6. Real testers before submitting: TestFlight on iOS, closed testing on Android. A crash during review is an automatic rejection.

If your app falls into a sensitive category —finance, health, apps for kids— there are additional documentation and compliance requirements; for fintech apps this includes proving licenses or the backing of a regulated entity.

Is your app ready but the stores are making your life miserable? Book a 30-minute call and we'll unblock it: we publish apps in both stores every month.

Apple vs. Google review: what to expect from each

Apple (App Store)

• Human review, strict and sometimes subjective. 90% of submissions are resolved in 24-48 hours; the first submission from a new account can take longer.
• If you're rejected, you get the number of the guideline you violated and you can respond, fix it, and resubmit (each resubmission goes back to the queue) or appeal.
• Apple rejects apps it considers "low quality": websites wrapped in an app with no native functionality, incomplete apps, or apps with placeholder content.

Google (Play Store)

• More automated up front: an app can be approved in hours. But a new account's first release and sensitive categories can take up to 7 days — don't launch a marketing campaign with a fixed date without a buffer.
• Google is more lenient on the way in and tougher afterward: it requires the app to target a recent version of Android (the target API level is updated every year), and if you don't update, the app stops being visible to new users.

The most common rejection reasons (and how to avoid them)

1. Crashes or bugs during review → test on real devices, not just the simulator.
2. Missing demo account or invalid credentials → verify the reviewer's login on the same day you submit.
3. Privacy policy missing, broken, or generic → a live URL with content specific to your app.
4. Data forms that don't match what the app does → declaring too little is worse than declaring too much.
5. Misleading metadata → screenshots showing features that don't exist, keywords with other brands' names.
6. Permissions with no justification → if you request location or camera, the app has to explain what for at the moment it asks.
7. (Apple only) "Minimum functionality" → if your app is basically your website, consider a PWA instead of fighting guideline 4.2.

When NOT to publish in the stores (yet)

There are scenarios where going through Google and Apple isn't the best first step:

• Internal app for your employees: Apple has enterprise distribution and Google allows private distribution; you don't need the public store.
• You're validating an idea: a closed test with TestFlight and invited testers gives you real feedback without exposing an immature version to one-star reviews that are costly to reverse later.
• Your product changes every day: every visible change goes through review. If you're iterating hard, a web app or PWA lets you deploy without asking permission, and you publish to the stores once the product stabilizes.

Final checklist and how we do it at Deepyze

The quotable summary: a Google Play account (one-time USD 25), an Apple Developer account (USD 99/year), a D-U-N-S if you're a company, an online privacy policy, completed data forms, screenshots in order, a demo account for the reviewer, and between 24 hours and 7 days of review. Anyone who tells you it gets published "same day" has never published an app for the first time in their life.

In all of our mobile app development projects, publishing is included: we create or manage the accounts, prepare the full listing for iOS and Android, and answer the rejections until the app is live. If you're just starting to weigh whether to build, begin with how an app is built step by step and the mistakes companies make when hiring app development. And if you already have the project in mind, tell us about your case: fixed price, a proposal in 24 hours, and a team in your time zone that has already fought —and won— against both stores' reviewers.