You can finish a great app and still be weeks away from your first user, because publishing has its own setup that nobody warns you about. The accounts, the identity checks, the review processes, and a few surprise requirements all take real, unavoidable time. Here is exactly what you need to get an app onto the App Store and Google Play, what it costs, and the traps that catch first-timers, so the publishing phase is a planned step instead of a panicked scramble the week you wanted to launch.

The two accounts and what they cost

  • Apple Developer Program: $99 per year, recurring.
  • Google Play Console: $25, one time.

So budget about $124 for your first year to publish on both stores, and $99 a year after that. That is entirely separate from anything you spend building the app. These fees are cheap. The real cost, as you will see, is time, not money.

Apple Developer Program (iOS)

  1. Create an Apple ID with two-factor authentication enabled. You need to be 18 or older to enroll.
  2. Enroll in the Apple Developer Program at developer.apple.com.
  3. Choose Individual or Organization:
    • Individual is the fastest path, and your legal name appears as the seller on the store.
    • Organization shows a company name as the seller, but you first need a D-U-N-S number for the business. It is free to request, but verification can take several days to a couple of weeks, so start it early if you want to publish under a company.
  4. Pay the $99 and wait for approval, usually quick but occasionally a day or two.

You will also need a Mac with Xcode to build, sign, and submit your app, or a cloud build service such as Expo EAS or Codemagic if you use a cross-platform framework and want to avoid buying a Mac. Apple’s signing system (certificates and provisioning profiles) is genuinely confusing the first time, so budget an afternoon just to get a build onto a real device. Your listings, builds, and submissions are all managed in App Store Connect, and TestFlight, built into App Store Connect, is how you distribute beta builds to testers before going live.

App review: Apple reviews every app and every update, typically within a day or two, and it is the stricter of the two stores. Read the App Review Guidelines before submitting. The usual rejections are broken features, missing or inaccurate privacy details, misleading screenshots, and the dreaded “this app does not provide enough lasting value.” Expect a rejection or two on your first app, respond politely in the Resolution Center, fix what they flag, and resubmit. It is a normal part of the process, not a catastrophe.

Google Play Console (Android)

  1. Use or create a Google account.
  2. Go to play.google.com/console and register as a developer. Pay the one-time $25.
  3. Choose a personal or organization account. Organizations need a D-U-N-S number here too.
  4. Complete identity verification. Google now requires this for all developers: legal name, address, phone, and sometimes a government ID. Start it early, because it can take a few days and you cannot publish until it clears.

The gotcha that surprises everyone: for new personal developer accounts, Google requires you to run a closed test with at least 20 testers for 14 continuous days before you can promote the app to production. That clock is unavoidable and it does not start until you actually have testers opted in, so line them up early, friends, a community, a dedicated testing group, and start the closed test the moment you have a working build. Treat those 20 testers as a real task on your launch checklist, not an afterthought. Organization accounts are currently exempt from the 20-tester rule, which is one reason some people choose that route despite the extra D-U-N-S step.

You will also fill out a Data safety form and a content rating questionnaire. Google’s review is generally faster and more lenient than Apple’s, but it still reviews apps, and updates can take anywhere from a few hours to a few days.

What both stores require from you

Before you can publish on either, have these ready, ideally prepared during development rather than scrambled together at the end:

  • A clear app icon and screenshots for each required device size.
  • A title plus short and full descriptions. This is also where App Store Optimization begins, so the words are worth real thought.
  • A privacy policy URL. Both stores require one, even for a simple app. This is one practical reason a small website is handy: somewhere stable to host the policy where it will not disappear.
  • A content and age rating questionnaire.
  • Data disclosures: Apple’s “App Privacy” labels and Google’s “Data safety” form. Answer honestly about exactly what you collect. If your app runs on-device and collects nothing, say so loudly, because “we collect no data” is a genuine selling point that the store will display to users.

A sane order to do this in

  1. Register both developer accounts on day one of the project, not the week you want to launch. Verification and D-U-N-S delays are the silent killers of launch dates.
  2. If you are taking the organization route on either store, start the D-U-N-S request immediately, since it is the longest pole in the tent.
  3. For Google, start the 20-tester closed test as early as you have a build, so the 14-day clock runs in the background while you finish the app instead of after.
  4. Prepare your store assets, icon, screenshots, descriptions, privacy policy, in parallel with development, not after.
  5. Submit to Apple expecting a possible rejection, and to Google expecting the testing requirement, so neither one surprises you.

The takeaway

Building is the fun part, but the publishing setup is where first-timers lose weeks they never budgeted for. The accounts themselves are cheap, about $124 for year one across both stores. The real cost is time: identity verification, D-U-N-S numbers, Apple’s review, the signing setup, and Google’s 20-tester rule. None of it is hard, but all of it has a clock, and the clocks run in serial if you start late and in parallel if you start early. Kick off the slow, bureaucratic pieces at the very beginning of the project, and a multi-week surprise turns into a quiet background task that is already done by the time your app is ready.

Once you are live, the next problem is getting found, which is where App Store Optimization and getting your first 100 users with no budget take over.