Building an app and launching an app are two very different jobs. Development is coding and designing the experience. All that happens after publishing – developer accounts, signed builds, store listings, review processes, and ever tighter compliance requirements – before a single real user can actually download your software. Apple’s own transparency reporting says its App Review team reviews millions of entries every year, and rejects around one in four for not meeting quality, safety or design standards. Most of those rejections are completely preventable with proper preparation.
In this tutorial, I’ll take you thru exactly how to get your app live on Google Play and the App Store in 2026 – accounts, costs, technical requirements, review deadlines, and the issues that most typically delay a debut.
Before you send it in: Pre-Launch Checklist
Both platforms have become much more strict over the last two years, with new SDK requirements, more rigorous identity verification and tougher privacy review standards. Before you begin the submission process, please confirm that you have:
- A working, crash-free build tested on real devices, not just a simulator
- Clear and detailed privacy policies that clearly state what data your app collects and how it is used
- Polished visual assets – icons, images, promotional visuals – sized precisely to fit each platform
- A current privacy policy URL and a help URL (both of which are common rejection reasons when lacking)
How to Publish to Google Play
Step 1: Register for a Google Play Developer Account
Sign up for Google Play Console for a one-time registration fee of $25. There is no annual renewal price and no per app or per listing expense. New accounts will need to verify their identification with a government issued ID and can take up to 48 hours to process.
Step 2 Build and Sign Your App
Google Play mandates that a new app be published as an Android App Bundle (AAB), not as a raw APK. Google automatically builds optimized APKs for each device from your AAB, so end consumers download reduced sizes. Enrolll Play App Signing: Google will securely store your signing key for you. If you lose your signing key you cannot publish future updates of the same app.
Step 3: Write Your Store Listing
In Play Console, navigate to Create Application and complete:
- App name – 30-50 characters depending on current requirements, in your default language
- Short Description (80 characters) – short and snappy, as it appears in search result
- Full description (up to 4,000 characters) – advantages, features and why you should download the app
- icon 512×512 px and feature graphic 1,024×500 px
- Screenshots – 2-8 high quality photos showing both phone and tablet layouts if possible
Step 4: Perform Closed Testing (if needed)
This step catches many first time developers off guard. If you started your Google Play developer account after November 13, 2023, you must execute a closed test of your app with at least 12 opted-in testers for 14 consecutive days before you may request a production release. no workaround, it is enforced at the account level Don’t be blindsided halfway thru your launch timeframe – schedule for this.
Step 5: Target the current API level
Google has a stringent criteria for the yearly goal API level . Starting in 2026, all new apps and app updates submitted to Google Play must target Android 16 (API level 36) or higher as of the enforcement deadline – non-compliant submissions will be rejected outright, so please ensure your build target before submitting.
Step 6: Send for review
Typical evaluation times for new developer accounts are 3-7 days and old accounts usually are live in less than 24 hours. Sensitive areas including fintech, health and apps for children can take up to 14 days due to further inspection.
Stage 7: Deploy to Production
Instead of deploying to all users at once, deploy in stages. Start at a small percentage (typically 1-5%) and increase gradually. This can help you detect any difficulties before they affect your complete user base.
Publishing to the Apple App Store
Step 1: Register for Apple Developer Program
It costs $99 per year and it renews every year (whereas Google Play is a one time fee). Organization accounts require a D-U-N-S number to verify your firm if you’re publishing thru a company account rather than an individual account, and this process might take anywhere from several days to a few weeks. Start this well before your target launch date.
Step 2: Build and Sign Your App
Apple demands you to sign with certificates and provisioning profiles, handled by Xcode or the Apple Developer portal. And creating really does require a Mac. As of April 2026, any apps submitted to App Store Connect must be built with the iOS 26 SDK or later. Any app built with an earlier SDK will be automatically rejected, no matter how good the app is.
Step 3: Create Your App in App Store Connect
App Store Connect is Apple’s web interface for managing your apps, builds and metadata. Before uploading a build, set up your app’s key details, pricing and regional availability here.
Step 4: Create Your Store Listing
Apple’s listing standards are as follows:
- App name and subtitle for rapid branding and context
- Keywords box (100 characters) – only used for search optimization, not for your visible title and subtitle
- Screenshots and preview video fit Apple’s exact size standards per device
- Support URL Required Privacy policy URL Required
Step 5: TestFlight Before Full Submission
TestFlight enables you release builds to internal and external testers before submitting them for formal App Store review. It helps you find bugs and usability issues while you may still address them without having to go thru a whole re-review cycle.
Step 6: Send for Review
As a rule, reviews in the App Store take from 24 to 72 hours, although during peak times for submitting apps this can be longer. Reviewers analyze functionality, performance, quality of design, legal content and conformity with Apple’s Human Interface Guidelines – a far broader and more subjective evaluation than Google’s mostly automated procedure.
Comparison of Costs and Time
| Comparison of Costs and Time | Google Play | Apple App Store |
|---|---|---|
| Account charge | $25 one time | $99/year |
| Average review time | 24-72 hours | 2-7 days (up to 14 days for sensitive categories) |
| Build format required | Android App Bundle (AAB) | IPA, produced using the current year’s SDK |
| Identity verification | Government ID, up to 48 hours | Individual or D-U-N-S for organizations, several weeks or more |
| Special first-time requirement | 12 testers, 14 day closed test (accounts created after Nov 2023) | None, but more rigorous design/quality review |
| In-app purchase commission | 15% under $1M per year 30% above Likewise, tiered structure | 15% under $1M per year 30% above Likewise, tiered structure |
Common Reasons for Denial – And How to Avoid Them
- Crashes and bugs – by far the most prevalent, and most preventable, reason for rejection. Test extensively on real devices, not just simulators, before submitting.
- Incomplete information (i.e. missing privacy policy URL, support URL or poor app description) is a simple and totally avoidable rejection.
- Both platforms are scrutinizing discrepancies in privacy statements, e.g. saying you collect data you don’t, or collecting data that isn’t declared in your privacy declarations.
- Closed testing requirement for Google Play – You can’t skip the 12-tester/14-day requirement for new developer accounts. Plan your calendar around it, don’t discover it mid-submission.
- Building with an older SDK (Apple) – apps developed using an SDK older than the current mandated version are automatically rejected irrespective of app quality.
- Broken links or features that don’t work – if a reviewer clicks on something that doesn’t work as intended, that’s a fast track to rejection.
What’s Next After Launch
Publishing is not the end line. Once your app has gone live:
- Invest in App Store Optimization (ASO) – your title, keywords, screenshots and description all have a direct impact on discoverability and download conversion in the search results of both stores.
- Pay particular attention to crash reports and reviews in the first days after launch, as early user feedback reveals flaws that testing may have overlooked.
- Set a regular update schedule-Both platforms prefer apps that are updated on a regular basis, and being on top of each year’s SDK and API level requirements will save you future issues with rejections.
- Put a buffer in for each subsequent submittal. Even experienced developers build in a 2-3 day buffer to a launch date so that unforeseen reviewer questions or fixes can be absorbed.
Last Thoughts
Getting your app on Google Play and the Apple App Store is a learnable process that is well-documented – the platforms have tightened their rules over the past two years, but the prerequisites are clearly publicized, and the great majority of rejections are easily preventable with good preparation. Get your developer accounts set up early, especially if you need Apple’s organization verification, block out real time for Google Play’s mandatory closed testing if your account is newer, and build in a buffer before any launch date for the inevitable back-and-forth with reviewers. Getting the checklist correct makes the submission itself a formality rather than the hurdle it can seem like the first time around.
Frequently Asked Questions (FAQs)
2. How much does it cost to launch an app on Google Play and App Store?
Google Play charges a one-time registration fee of $25. No recurring payments. Developer Program costs $99 a year and will renew annually. Both platforms also charge a cut on in-app sales and subscriptions, typically around 15% on the first $1 million in yearly revenue and 30% above that barrier.
2. Duration of app review time on Google Play and App Store?
Google Play evaluations usually take 2-7 days (up to 14 days for sensitive categories like Fintech, Health or Children’s apps). Apple generally takes less time to assess apps, usually 24-72 hours, but can take longer during busy periods. Regardless of the platform, it’s a smart move to put in a 2-3 day cushion into your launch timeline.
3. Why do I have to wait 14 days with 12 testers on Google Play before publishing?
This closed testing restriction is applied at the account level and cannot be bypassed. It applies to all Google Play developer accounts created after November 13, 2023. This is to make sure that new developers have tested their app with real users before they go live in full production, if you skip this your app won’t go live.
4. The most typical reason for rejection of apps?
Crashes and problems during review are typical and avoidable grounds for rejection on both platforms, with inadequate metadata (e.g., no privacy policy or help URL) and discrepancies in privacy declarations not far behind. The bulk of rejections can be avoided with thorough testing on real devices and complete and correct information in the app store listing.
5. Do I need a Mac for publishing an iOS app on the App Store?
Yes. To build and sign an iOS app you need Xcode (which only runs on macOS) plus certificates and provisioning profiles that you manage via the Apple Developer portal. Google Play doesn’t have such a need and can be handled from any regular computer.
