App monetization: subscriptions, fees, ads or freemium
Compare app monetization models, subscriptions, transaction fees, ads and freemium, and learn how to choose based on the way your app delivers value to users.
A step-by-step guide to publish an app on the App Store and Google Play: developer accounts, store listings, privacy forms, testing and common rejections.

To publish an app you need three things: developer accounts with Apple and Google, an app build with a complete store listing, and approval from each platform's review. The technical part is usually the fastest. What delays launches is company verification, the privacy policy and rejections for details you could have seen coming.
Apple charges an annual fee for the Apple Developer Program and Google charges a one-time registration fee for the Google Play Console. Amounts and conditions change, so check the official pages before you set your budget.
The most important decision here is whose name the account goes under. If the app belongs to a company, the account should be an organization account registered to that company, not to an individual developer or to the agency you hired. The seller name shown in the store comes from that account, and moving an app to another account later is possible but bureaucratic.
Organization accounts go through verification. Both stores usually ask for the company's D-U-N-S number, a free international business identifier that can take several days to be issued. Request it at the start of the project, in parallel with development, so it does not become the bottleneck at the end.
Once the account is open, give your technical team access through each platform's user roles. That way nobody needs the owner's password, and access can be revoked when the contract ends.
Many rejections come from incomplete or inconsistent materials. Put this list together ahead of time:
Your privacy disclosures must match what the app really does. If you use an analytics or advertising SDK that collects data, it belongs in the disclosure, even if your own code stores nothing.
Apple's flow runs through Xcode and App Store Connect:
Building and uploading iOS apps requires Xcode, which runs on macOS. If you do not have a Mac, cloud build services can fill the gap, but the account and App Store Connect remain yours.
On Google's side, everything happens in the Play Console:
Google also requires apps to target a recent Android API level and raises that requirement on a regular schedule. An app left without updates for too long stops being shown to users on newer devices.
The most common rejections are predictable. Use this table as a pre-submission review:
| Rejection reason | How to avoid it |
|---|---|
| The app crashes or shows an obvious bug during review | Test the release build on real devices, not only on emulators |
| The reviewer cannot log in | Provide test credentials with populated sample data |
| Minimum functionality, such as a website in an app shell | Offer real app features and useful content |
| Declared privacy does not match actual behavior | Include data collected by third-party SDKs |
| Selling digital content outside the store's payment system | Check the in-app purchase rules for your case and country |
| Permissions without a clear reason | Explain in the prompt why the app needs camera, location or contacts |
| Description or screenshots promising features that do not exist | Show real screens and describe only what is there |
When a rejection arrives, read it carefully and reply through the store's own channel. Often a clarification or a text change is enough, with no new build.
Going live is the start of your work in the store, and a few routines matter from week one:
When Bridgemoon builds an app, publishing is part of the job: setting up accounts, store materials, testing and updates, with the accounts registered to the company that owns the product. That keeps the effort to publish an app from becoming an improvised step at the end of the project.
It varies a lot, from a few hours to a few days, and a first submission usually takes longer than updates. Apps that handle payments, sensitive data or content for children tend to get extra scrutiny. Leave a buffer of several days before any launch date you announce publicly.
To compile and upload the iOS build you need Xcode, which only runs on macOS. Cloud build services solve this if you do not own a Mac, and the rest of the process happens in the browser through App Store Connect. For proper testing, it still helps to have at least one real iPhone available.
Technically yes, but it is not a good idea. The app, its reviews and its history stay tied to another company's account, and moving it later requires a formal transfer in both stores. Open the account under your own company from the start and add the vendor as a user.