Shipping an App to the App Store and Google Play: What to Know First

By PB ·

A finished app is not a published app. Before anyone can download it on an iPhone or an Android phone, you need a developer account with each store, an identity check, a choice between enrolling as a person or as a business, and a pass through testing and review. Some of those steps take days or weeks of calendar time, no matter how fast you work.

I ship my own apps through both stores. This guide covers what each store asks for, what it costs, what becomes public when you enroll under your own name, and the checks that hold up a first submission. Start enrollment while the app is still being built, so the waiting happens in parallel. If you are also setting up hosting, domains, and databases, pair this guide with a one-page record for organizing your app's infrastructure.

Four steps before shipping an app: 1. Choose Account Type: Pick individual or organization on both stores. 2. Gather Documents: Prepare ID, legal details, or D-U-N-S number. 3. Listing and Policies: Prepare listing, support link, and privacy policy. 4. Test and Submit: Run required closed tests and send for review. Figure 1: Four steps before shipping an app: choose account type, gather documents, prepare listing and policies, and test and submit.

What It Costs

To publish on both platforms, you pay an enrollment fee to each store. You join the Apple Developer Program to publish on the Apple App Store through App Store Connect (Apple's web portal for uploading packaged versions of your app and managing listings), and you register on Google Play Console (Google's web and mobile portal for managing Android releases) to publish on Google Play.

Apple offers fee waivers for eligible nonprofits, accredited educational institutions, and government entities. Google does not refund its fee if your identity verification information turns out to be invalid.

Terms You Will See

Signup forms on both stores use a few legal and administrative terms:

Individual vs Organization Accounts

Before paying an enrollment fee, choose between an individual (or personal) account and an organization account. Each option requires different verification records and displays a different public seller identity.

Apple individual

Apple organization

Google Play personal

Google Play organization

If You Are Not a Business

You do not need a registered company to ship most everyday apps. Both stores let individuals enroll under their own legal names, provided you accept what becomes public and complete each store's verification steps.

One distinction matters on Google Play. Google says to choose a personal account "if your account is for personal use" or "if you're a student, hobbyist, or amateur developer," and an organization account if you are "engaged in commercial, industrial, professional, or governmental activities." So if the app is part of how you earn a living, plan for an organization account, which means a D-U-N-S number and up to 30 days of lead time. Apple's individual account has no such wording on its enrollment page; the main trade-off there is that your own name becomes the seller name.

Apps That Need an Organization

Certain regulated or sensitive categories cannot be published under an individual or personal account:

Submission Checklist

Apple notes that over 40% of unresolved App Review issues relate to Guideline 2.1 (App Completeness). Check these items before submitting:

  1. Complete build without crashes: Test every screen on real hardware so your submitted build runs without crashes.
  2. No placeholder content: Remove temporary text, unfinished screens, and "coming soon" sections before uploading.
  3. Working support link and privacy policy link: Confirm that your public support link and privacy policy link open cleanly in a standard browser. Both Apple (Guideline 5.1.1(i)) and Google Play require every app to link to its privacy policy both in the store listing metadata and inside the app in an easily accessible place, even when the app collects no user data.
  4. A privacy policy that says what you do with data: Apple expects it to list what data the app collects, how, and every use of it; confirm that any third party you share data with protects it equally; and explain how long you keep data, how you delete it, and how people can withdraw consent or ask for deletion.
  5. Demo account and review access when sign-in is required: Whenever sign-in or another restriction limits access to any part of your app, provide active login credentials in Apple's App Review Information (in App Store Connect) and all required access instructions and resources (such as test credentials) in Google Play's App access / Sign-in details declaration (under App content in Play Console).
  6. Account deletion if users can create accounts: Under Apple Guideline 5.1.1(v), apps that let users create an account must let them start account deletion inside the app; deactivation alone is not enough. On Google Play, apps that allow account creation must also provide an in-app deletion path and a web link resource where users can request account and data deletion, and link that web resource in Play Console (under Data safety in App content).
  7. Purpose text for sensitive access: When your app asks for something sensitive, such as the camera, the permission prompt must carry a short purpose string (one sentence that tells the user why the app needs it).
  8. Accurate screenshots: Upload store screenshots that reflect your app's actual interface and working features.
  9. Google Play Data safety form: Complete the Data safety form in Play Console and provide a privacy policy link, even if your app collects no user data. This applies to closed testing, open testing, and production releases. Apps exclusively on internal testing tracks, system services, and private apps are exempt.
  10. Apple App Privacy details: Answer the App Privacy questions in App Store Connect before submitting a new app or update. If your app and any integrated third-party code collect no data, select "No, we do not collect data from this app."
  11. Google Play Health apps declaration: Complete the Health apps declaration form in Play Console (under App content) for closed testing, open testing, and production tracks, even when your app offers no health features (you certify that it offers none). System services and private apps are exempt.

Realistic Timeline

Verification and testing gates follow calendar time:

Store Fees in Brief

When you sell paid downloads or digital in-app purchases, each store charges a service commission:

Worked Example (Hypothetical): A Hobbyist's Meditation Timer

Consider a hypothetical example: Maya, a hobbyist building a free meditation timer to share with friends and anyone who finds it useful. Her app is a timer-only app with a bell and no meditation guidance, mindfulness coaching, or health claims. She has no company and no paid features.

Want Help With Your First Submission?

If you want to review your developer account choice, public seller details, or submission checklist before you launch, email hello@tilorah.co for a consultation about your accounts and submission.