App Release on the App Store and Google Play in 2026: From Account Setup to First Rankings

An app release on the App Store and Google Play lands in a crowded stream: 4,161 new apps hit the App Store every day, and 1,956 hit Google Play (42matters, October 5, 2026). Together, the stores hold 2.69M and 2.6M apps. That is why metadata, localizations, and visuals should be ready before you submit for review, not after.

Apple reviews every version by hand, even if you only changed keywords. Google lets updates through faster, but a new personal account must first test the app with real people for two weeks.

App Store vs. Google Play: key differences

Releasing on the App Store

Account and technical requirements

Publishing on the App Store starts with the Apple Developer Program at $99 per year. Companies enroll as an organization with a D-U-N-S number, so the store shows the brand name instead of a private person's name.

Since April 28, 2026, App Store Connect only accepts builds made with Xcode 26 and the iOS 26 SDK or later. The next threshold is already announced: from April 2027, you'll need the iOS 27 SDK (Apple's requirements). Before submitting for review, prepare:

• a privacy policy link and a completed App Privacy section;
• a demo account and notes for the reviewer if some features sit behind a login;
• answers to the age rating questionnaire;
• metadata and visuals for every localization you launch in.

Apple has reworked the age rating questionnaire. Instead of 12+ and 17+, there are now 13+, 16+ and 18+, and the new questions had to be answered by January 31, 2026, or updates would fail to submit. With iOS 27, the questionnaire added a question about social media features: parents can limit time in such apps, as well as in games and entertainment apps.

App Store Connect through an ASO lens

App Store Connect is a developer tool, but many of its fields affect search and conversion.

The name, subtitle, and categories live in App Information, while keywords, description, promotional text, and visuals sit on the version page. Only the name, subtitle, and keyword field count for search. The description and promotional text drive conversions.

Each localization gives you its own set of name, subtitle, and keywords. One country indexes several localizations, so extra languages expand your keyword coverage without translating the app itself. We covered which localizations work in which country in our article on App Store localization.

The name, subtitle and keywords only change with a new version, so every ASO iteration goes through review. Promotional text can be edited at any time, and since October 2026 visuals can also be submitted separately from a build through the Asset Library.

The product page still holds up to 10 screenshots and up to 3 app previews per localization. Since October 5, 2026, they've been joined by a product page header (21:9) and a search results asset (3:2), shown to iOS 27 users. These assets are optional, but users see the search asset before they ever open your page. From April 2027, apps built with the iOS 27.1 SDK or later will also need iPhone Duo screenshots (Apple's specifications).

You can now keep up to 70 custom product pages live at once and assign keywords to them. For those queries, organic search shows the custom page instead of the default one (Apple). If your app covers several use cases, you can show the right screenshots for each intent.

Since March 26, 2026, you can no longer create promo codes for in-app purchases: Offer Codes replaced them for all purchase types. Promo codes for free downloads of paid apps are still available.

Review and rejection reasons

Apple aims to review 50% of submissions within 24 hours and 90% within 48 hours, but that's a goal, not a guarantee (App Review). In 2026, developers on Apple's forums report waiting a week or more, so we build in extra days before an important date. You can request an expedited review for a critical bug or an event-driven release, but it isn't always granted.

Typical rejection reasons under Apple's guidelines:

• crashes, broken links, and placeholder content (guideline 2.1);
• metadata that promises what the app doesn't have, or screenshots that don't show the real interface (2.3). In October 2026, Apple added a separate guideline, 2.3.14, for the new creative assets;
• collecting data without consent or a mismatch with App Privacy (5.1);
• minimum functionality: a website wrapper or a template app (4.2, 4.3);
• paying for digital goods outside in-app purchase where that isn't allowed (3.1.1).

If the app is rejected, we reply to the reviewer in App Store Connect: an explanation or demo access is often enough. If we disagree with the decision, we file an appeal with the App Review Board. The full rule set is in the App Review Guidelines.

Apple only removes abandoned apps: no updates for three years and almost no downloads over the last 12 months. After a notice, the developer has 90 days to submit an update. Apps that crash on launch are removed right away (App Store Improvements).

Release

After approval, there are three options: release the version manually, automatically, or no earlier than a set date. For a launch on a specific day, manual release works best: the app doesn't appear in every country instantly but within up to 24 hours.

Updates can go out in phases. Over 7 days, automatic updates reach 1, 2, 5, 10, 20, 50 and 100% of users, and you can pause the rollout for up to 30 days. Anyone can still download the new version manually, so this is insurance against a widespread bug, not a closed test.

Releasing on Google Play

Account and verification

Registering in Play Console costs a one-time $25 (Google Help). An account can be personal or organizational, and in both cases Google verifies identity: the ID and the card must be in the same name. If the details fail verification, the fee isn't refunded.

Personal accounts have two extra steps. First, you confirm access to an Android device through the Play Console mobile app. Then, if the account was created after November 13, 2023, you go through mandatory testing (Google Help):

1. Run a closed test with at least 12 testers.
2. Keep them opted in for 14 days in a row. If a tester opts out and back in, their count starts over.
3. Click Apply for production on the dashboard and answer questions about the test, the app and its production readiness.
4. Wait for the decision: usually up to 7 days, sometimes longer.

All in all, about three weeks pass between the first build and production. We keep the answers in the application specific: what testers found and what we fixed. Google may send an application with generic answers and low tester engagement back for more testing. Organization accounts are exempt from this requirement.

Play Console and the App content section

Before the first release, Play Console asks you to fill in App content. It's a set of declarations the reviewer checks the app against:

• privacy policy and the Data safety section on data collection and sharing;
• app access: a login and password for the reviewer if the app requires sign-in;
• ads;
• content rating through the IARC questionnaire;
• target audience and content;
• industry declarations for finance, health, news and government apps.

Since November 2026, Play Console also requires you to declare trader status. Data safety must match what the SDKs in the app actually collect, so we check the list of third-party libraries before filling it in.

Since August 31, 2026, new apps and updates must target Android 16 (API 36). An extension could be requested until November 1 (Android Developers).

Tracks: from internal testing to production

Staged rollout and managed publishing

Staged rollout on Google Play is more flexible than on the App Store. We choose the share of the audience ourselves and raise it manually; it doesn't grow on its own. A rollout can be halted: new users stop getting the version, while those who already updated stay on it. Staged rollout only works for updates; the first version goes out to everyone at once (Google Help).

For ASO, Google's own advice matters: we update the store listing once the version reaches 100% of users. Otherwise, screenshots show a feature most users don't have yet.

Managed publishing solves a different problem. Changes go through review in advance and go live when we say so. That way, a new build, store listing and event launch at the same time.

Review

Google combines automated and manual review and doesn't publish target timelines. A first release, new permissions, and apps for children take longer to review, so we plan for a week.

Review doesn't end at release: Google can unpublish an app later, and repeated violations can get the account suspended. Policy notices arrive in the Play Console Inbox and in the account owner's email, so don't ignore them.

Pre-launch ASO checklist

The same semantic core is packaged differently for each store. The App Store rewards fitting keywords into short fields; Google Play rewards a natural description that uses the right words.

And four checks that often get skipped:

• Screenshots show the real interface of the current version. An idealized mockup gives both stores a reason to reject.
• Metadata contains no competitor brands, prices or words like best or #1 without proof.
• Every localization has localized visuals or at least translated captions on screenshots.
• Keywords are added to tracking before release, so there's a baseline for the first rankings.

What changed in 2026

Over the year, both stores changed their fees, technical requirements and developer rules. The table covers what matters for a release; the details are in our monthly digests.

A few more dates are coming. On January 27, 2027, new Google Play rules on location and contacts access take effect. In April 2027, the App Store will require builds with the iOS 27 SDK, and builds with the iOS 27.1 SDK or later will need iPhone Duo screenshots. If you're planning a spring release, factor these in now.

After release: the first two weeks

The first days after launch show whether the metadata works. In the first week, we check three things.

First, indexing. The app should appear in search for words from the name, subtitle, keyword field or description. Keyword Monitor updates rankings every 6 hours for the App Store and every 12 hours for Google Play. Keyword Report compares two dates and shows which queries the app gained its first rankings for and which ones it lost. If an important keyword stays unindexed for several days, we check the localization and spelling.

Next, reviews. Early ratings have the biggest impact on the average while there are few of them. We reply to every negative review within the first day and collect recurring complaints in the backlog.

And finally, stability. On Google Play, it's measured by Android Vitals. If the user-perceived crash rate exceeds 1.09% or the ANR rate exceeds 0.47%, the app becomes less visible in the store and may get a warning on its listing. From February 2027, memory usage requirements are added to these metrics. On the App Store, crashes are tracked in Xcode Organizer and the analytics section of App Store Connect.

Reviews from both stores are easier to read and handle in one place. To do this, we connect the ASOMobile integrations:

• In App Store Connect, we create a separate user with the Customer Support role, add it to ASOMobile, and confirm with a two-factor authentication code.
• Google Play Console connects through OAuth from Google Cloud. The account owner has to do it, and the app must be in production.

After that, review replies, templates and keyword rankings live in one place. This shows how a metadata change or a bug fix affected the rating and visibility.

Conclusion

Releasing in two stores means two different timelines. On Google Play, a new personal account loses about three weeks to testing and the application, but updates ship fast after that. On the App Store, the start is quicker, but every change to the name or keywords goes back to review. We count both timelines back from the launch date, prepare keywords and visuals in advance and start tracking rankings from day one.

Release is just the start. Optimize with ease and grow from day one in the store!