Apple rejected roughly 1.93 million app submissions in 2024 alone. Google now blocks first-time developers from going live at all until they run a 14-day test with real users. The upload button is the easy part. Everything around it is where launches stall.
If you are working from a guide written in 2023, most of it is wrong now. “iTunes Connect” became App Store Connect years ago. Single APK uploads are dead for new Android apps. And the Play Store review that once took “about two hours” can now stretch to a week or more for a fresh account.
This walkthrough is built for how the stores actually work in 2026. You get the real costs, the current review timelines, a side-by-side comparison, and the exact steps to ship on both platforms. More useful still, you learn why apps get bounced and how to clear review on the first attempt.
Let’s get your app live.
What Changed in 2026 (and Why Old Guides Get You Rejected)
Submission has tightened hard on both stores. A handful of shifts trip up nearly every first-timer following outdated instructions:
- Google’s 12-tester rule. New personal developer accounts must run a closed test with at least 12 real testers for 14 straight days before they can even request production access.
- App Bundles replaced APKs. New Android apps ship as an Android App Bundle (.aab), not a standalone APK. Google generates the device-specific install files for you.
- Apple’s privacy manifest. Since May 2024, every iOS build needs a PrivacyInfo.xcprivacy file. Miss it and Apple auto-rejects before a human even opens your app.
- Data disclosure is mandatory. Google’s Data Safety form and Apple’s Privacy “nutrition” labels both have to match what your code actually collects.
- Target SDK floors keep rising. New Play uploads must target Android 15 (API level 35), moving to Android 16 (API level 36) on August 31, 2026. iOS builds must use the current Xcode and SDK.
Skip any of these and you are not slow. You are rejected.
Play Store vs App Store: The Money and Time, Side by Side
Before you pick a lane or commit to both, here is the honest comparison. The two stores charge differently, review differently, and gate new developers differently.
| Factor | Google Play Store | Apple App Store |
| Developer fee | $25, one time | $99, per year |
| Commission | 15% under $1M/year, then 30% | 15% under $1M/year, then 30% |
| Publishing format | Android App Bundle (.aab) | Build and upload via Xcode |
| First-time gate | 12 testers for 14 days (personal accounts) | Standard review, no tester minimum |
| Typical review time | Hours to a few days; up to 7 days for new-account production access | About 90% within 24 hours, 98% within 48 hours |
| Minimum target | Android 15 (API 35) | Current iOS SDK via latest Xcode |
| Account types | Personal or Organization | Individual or Organization |
One number is worth flagging: that $99 Apple fee renews every single year, while Google’s $25 is once and done. Plan your budget accordingly if you are shipping on both.
Before You Upload: The Pre-Submission Checklist
Most rejections trace back to something missing before submission, not a flaw in the app itself. Run this list first. It applies to both stores.
- Privacy policy URL, live and reachable. Both stores require one. A dead link is an instant hold.
- App icon at full resolution. Apple needs 1024×1024 px. Play needs a 512×512 px hi-res icon plus a feature graphic.
- Screenshots from the real build. Not mockups. Reviewers compare them against the app, and promising a feature you don’t ship gets flagged.
- A working demo account. If your app has a login, provide test credentials. No reviewer will create their own.
- Accurate data disclosures. List every data type you collect, why you collect it, and whether it is tied to a user’s identity.
- No placeholder content. Strip debug overlays, “lorem ipsum,” and test endpoints out of the build you submit.
- Two-factor authentication on your developer account. Both Apple and Google require it before you can publish.
Ten minutes here saves you a rejection cycle that costs days.
How to Publish Your Android App to the Google Play Store
Assuming your app is built and signed, here is the path from zero to live on Google Play.
1. Create Your Google Play Developer Account
Go to the Play Console and pay the one-time $25 registration fee. Choose your account type carefully. A Personal account is faster to set up, but an Organization account (which needs a D-U-N-S number) skips the 12-tester requirement entirely. If you are a registered business, register as an organization. Either way, Google verifies your identity before the account goes fully active, so expect to confirm a phone number, an email address, and (for personal accounts) a government ID.
2. Set Up Your App and Store Listing
Inside the Play Console, select Create app. Set the default language, the app name (up to 30 characters), and whether it is an app or a game, free or paid. Then build out the store listing: a short description, a full description, your screenshots, the hi-res icon, and the feature graphic. This is your storefront, so write the description for humans first and keywords second. Put your main search term in the app title and the first two lines of the description, since that is what Play search weighs most heavily and what users read before they tap “see more.”
3. Upload Your App Bundle
Head to Test and release and pick a track. New apps upload an Android App Bundle (.aab), not an APK. Google’s Play App Signing manages your signing key and generates optimized APKs per device through Dynamic Delivery. Upload the .aab, name the release, and add your release notes.
4. Complete the Content and Data Forms
Three forms gate your release, and all three are required:
- Content rating questionnaire. Answer honestly. A wrong rating can get your app pulled later.
- Data safety form. Declare what you collect and share. This maps to the “Data safety” section shoppers see on your listing.
- App content declarations. Ads, target audience, and any special content categories.
5. Run Your Closed Test (New Personal Accounts)
Here is the step the old guides never mention. If your personal account was created after November 13, 2023, you must run a closed test with at least 12 testers, opted in for 14 consecutive days, before you can apply for production access.
Opted in is not enough on its own. Google now measures real engagement, so testers who install but never open the app get flagged as inactive, which can void the whole test. Recruit people who will actually use it. Friends, colleagues, and classmates are the usual starting point, and you invite them by email address or through a Google Group with the official opt-in link. When the 14 days are up, apply for production access and answer the questionnaire about your testing process and the feedback you acted on. That review usually takes 7 days or less. Organization accounts skip this step.
6. Set Pricing and Countries, Then Roll Out
Choose free or paid (note: a free app can never switch to paid later), pick your countries, and confirm distribution. Then go to Production, create your release, and start the rollout. You can push to 100% or use a staged rollout to release to a small percentage of users first and watch for crashes. Your app goes live the moment review clears.
How to Publish Your iOS App to the Apple App Store
Apple’s process runs through App Store Connect, the platform once called iTunes Connect, plus Xcode on a Mac.
1. Enroll in the Apple Developer Program
Sign up and pay the $99 annual fee. Pick Individual or Organization at enrollment. Apple does not let you switch afterward, so choose the one that matches how you plan to publish. New developers automatically qualify for the Small Business Program, which cuts commission to 15%. Enroll in it. Set a calendar reminder for the renewal as well, because if the $99 membership lapses, your apps drop off the store until you pay again.
2. Create Your App ID and Certificates
In your developer account, register a Bundle ID in reverse-domain format (com.yourcompany.yourapp). Then generate a Distribution Certificate and a Provisioning Profile so your build can be signed for the App Store. You will create a Certificate Signing Request from the Keychain Access app on your Mac to get that certificate.
3. Add Your Privacy Manifest
Do not skip this one. Your own code and every third-party SDK must declare data collection and any “required reason” API usage inside a PrivacyInfo.xcprivacy file. Bundled libraries need their own manifests too, and Apple checks at the SDK level. A missing manifest is the single most common auto-rejection in 2026.
4. Archive and Upload the Build in Xcode
Build with the latest stable Xcode and current SDK. Older versions get bounced at upload. In Xcode, select Product > Archive, then use the Organizer window to upload the build to App Store Connect. It usually appears in your account within 10 to 30 minutes.
5. Create the App Store Listing
In App Store Connect, open My Apps, add a new app, and select your Bundle ID. Fill in the name, subtitle (both capped at 30 characters), description, keywords, screenshots, and the 1024×1024 icon. Complete the App Privacy labels so they match your manifest and your actual behavior. If you collect tracking data, your App Tracking Transparency prompt and tracking domains must be declared.
6. Test with TestFlight, Then Submit
Before going live, push a build to TestFlight for beta feedback, up to 10,000 external testers. When you are confident, attach the build to your listing, set pricing, and click Submit for Review. Apple runs automated checks first, then human review. Roughly 90% of submissions get a decision inside 24 hours.
7. Release to the App Store
Once approved, you control the launch. Choose manual release to go live on your own schedule, or automatic release to publish the moment review clears. You can also use phased release to roll out gradually over seven days. Wait for the “Ready for Sale” status, and your app is live.
The Real Timeline: From Finished Build to Live
Assume your app is finished and your accounts are set up. Here is what the wait actually looks like in 2026, so you can set a launch date you can hit.
Apple App Store: For most apps, plan on 1 to 3 days from submission to live. Automated checks run first, then human review, and about 90% of decisions land inside 24 hours. First submissions, apps with in-app purchases, and complex privacy setups tend to sit longer.
Google Play, organization account: Roughly 1 to 3 days. There is no tester gate, so once your listing and forms are done, it moves close to Apple’s pace.
Google Play, new personal account: This is the long road. Budget 14 days for the closed test, plus up to 7 days for the production-access review, which is about three weeks minimum before you can even push to production. Start recruiting testers the day your build is ready, not the day you want to launch.
Build these numbers into your plan. A marketing date set for “next Friday” collides badly with a three-week Play testing requirement nobody accounted for.
Why Apps Get Rejected (and How to Pass the First Time)
Rejection is common and almost always preventable. Here are the patterns that stall the most launches, with the fix for each.
On the App Store:
- Missing or wrong privacy manifest. The top technical rejection today. Audit every third-party SDK, not just your own code.
- Broken functionality or crashes. Apple tests on real devices. A crash on launch or in a fresh-account flow ends review fast, so test airplane mode, a clean install, and the first-run experience on an actual iPhone before you submit.
- Metadata that oversells. Screenshots or copy promising features the build does not have. Match every claim to the live app.
- No demo account. A login wall with no test credentials gets bounced immediately.
On Google Play:
- Insufficient testing engagement. The 2026 headline rejection for new accounts. Testers have to genuinely use the app across the 14 days.
- Data safety mismatch. Declared data practices that do not match observed behavior. Align the form with what the app truly does.
- Policy violations. Permissions you do not need, deceptive behavior, or restricted content. Request only the permissions you actually use.
- Stale target SDK. A build targeting an old API level will not publish. Target Android 15 (API 35) or higher.
The common thread runs through both stores: submit a complete, honest, working build with disclosures that match reality. Reviewers reward that with a fast yes.
Ship Your App Without the Guesswork
Getting an app through review cleanly takes the same discipline you put into building it. Missed manifests, mismatched data forms, and failed test cycles turn a one-week launch into a one-month slog. If you would rather hand that off, XCEEDBD builds and ships mobile apps end to end, from development through store submission, privacy compliance, and a clean first-review pass on both platforms. We handle the manifest files, data forms, and testing tracks before they turn into a rejection email.
Ready to launch without the rejection cycle? Talk to our mobile team and get your app to market faster.
Frequently Asked Questions
How much does it cost to publish an app on the Play Store and App Store?
Google Play charges a one-time $25 registration fee. Apple charges $99 per year for the Apple Developer Program. Both take a commission on sales: 15% for developers under $1 million a year in revenue, and 30% above that.
How long does app store review take in 2026?
Apple decides on roughly 90% of submissions within 24 hours and 98% within 48 hours. Google Play updates often clear in hours to a couple of days, but a new personal account’s first production release can take up to 7 days, and that is on top of the required 14-day closed test.
Why does Google Play require 12 testers for 14 days?
The rule applies to personal developer accounts created after November 13, 2023, and exists to cut spam and low-quality apps. You need at least 12 testers actively using your app for 14 straight days before you can apply for production access. Organization accounts are exempt.
Can I upload an APK to the Play Store instead of an App Bundle?
Not for new apps. Google requires the Android App Bundle (.aab) format for new submissions. Google’s servers then generate the optimized, device-specific APKs automatically through Dynamic Delivery.
What is a privacy manifest and do I need one?
Yes, every iOS app has needed one since May 2024. A PrivacyInfo.xcprivacy file declares what data your app collects and which “required reason” APIs it uses. Third-party SDKs need their own. Apple automatically rejects builds without it.
Do I need a Mac to publish an iOS app?
Yes. Apple’s build, archive, and upload workflow runs through Xcode, which only runs on macOS. There is no supported path to submit an app to the App Store without access to a Mac.
What is the difference between a personal and organization developer account?
A personal (Google) or individual (Apple) account is faster to set up and lists you as the developer. An organization account publishes under a business name, needs a D-U-N-S number, and on Google Play it skips the 12-tester requirement. Apple will not let you change the type after you enroll.
How do I avoid getting my app rejected?
Submit a complete, working build with a live privacy policy, accurate data disclosures, real screenshots, and a demo account if you have a login. On iOS, include your privacy manifest. On Android, run a genuine closed test and target a current API level. Honest, fully functional submissions clear review the fastest.
