How to Publish an App on the App Store & Google Play (2026)

How to publish an app in 2026: register a Google Play developer account ($25 one-time) and an Apple Developer Program membership ($99/year), prepare a compliant build and store listing, then pass review. Apple resolves most submissions within 24 hours; Google Play takes a few hours to several days — and new personal accounts must first complete a 12-tester, 14-day closed test.

Finishing the code is only half the job. Getting your app into the stores means account verification, certificates, privacy declarations, age ratings and testing queues — a chain of dependent steps where one missing piece can push your launch back by weeks. Most teams discover this only when their first submission bounces.

This guide walks through how to publish an app on both stores, with 2026's updated rules and realistic timelines. If you're still earlier in the journey, our mobile app development process guide covers everything from idea to launch; this article focuses on the final stretch.

Table of Contents

• Costs and Timeline at a Glance
• What Changed in 2026
• Step 1: Set Up Your Developer Accounts
• Step 2: Prepare a Release-Ready Build
• Step 3: Build Your Store Listings
• Step 4: Privacy Declarations and Age Ratings
• Step 5: Complete the Testing Phase
• Step 6: Submit and Manage the Review
• Step 7: Updates, Fees and Payouts
• Why Apps Get Rejected
• Frequently Asked Questions

Costs and Timeline at a Glance

Before we get into how to publish an app step by step, set expectations on cost and timing. The most common planning mistake is assuming "the app is done, we ship tomorrow" — an assumption that fails hardest on Google Play. Here is how the two stores compare:

The fees are the official rates from the Apple Developer Program and Google Play Console registration pages. For commissions, see the Apple Small Business Program and Google Play's service fee table — in mid-2026 Google introduced a new split fee structure for the US, UK and EEA markets, while most other markets keep the 15% rate on the first $1 million.

These are store-side costs only. For the development budget itself, see our mobile app development cost guide or try the app cost calculator.

What Changed in 2026

Publishing got harder in 2026 for two reasons: the queues grew, and the technical bars moved up.

The queue numbers are striking. According to a TechCrunch analysis of Appfigures data, worldwide app releases in Q1 2026 were up 60% year-over-year across both stores — and 80% on the iOS App Store alone. In April 2026 the combined increase reached 104%. AI-assisted development made building faster, but review capacity did not scale with it, so reviews that used to clear in a day now stretch into several more often.

On the technical side, 2026 has three dates that matter:

• Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 and the iOS 26 SDK (Apple's upcoming requirements).
• From August 31, 2026, new apps and updates submitted to Google Play must target Android 16 (API level 36); extensions to November 1, 2026 are available on request (Play target API policy).
• Since January 31, 2026, apps that have not answered App Store Connect's updated age rating questionnaire cannot submit updates (Apple announcement).

Google is also rolling out developer verification beyond the Play Store: apps installed on certified Android devices — including sideloaded ones — must come from verified developers, starting with the first countries in 2026 and expanding globally from 2027 (Google's explanation). Identity verification is no longer a detail you handle at the end; it belongs at the start of your project plan.

Step 1: Set Up Your Developer Accounts

This step hides the longest waits in the whole process, so start it well before the code is finished.

Apple Developer Program. Individual enrollment needs an Apple ID and identity verification, and usually activates within a few days. Enrolling as an organization requires a D-U-N-S number registered to your legal entity. The number itself is free, but obtaining one can take weeks — plan for that if you want your company name, not a personal name, shown in the store.

If you will sell the app or offer in-app purchases, accept the Paid Apps agreement in App Store Connect and enter your banking and tax details. Developers outside the US complete a W-8BEN (individual) or W-8BEN-E (entity) form (Apple's tax information guide). The account name, tax form and bank account holder must match exactly; mismatches freeze payouts.

Google Play Console. Registration costs a one-time $25. Organization accounts also require a D-U-N-S number here, and Google notes that obtaining one can take up to 30 days. Personal accounts verify identity with a government ID plus proof of address, and two-step verification on the Google account is mandatory.

One recommendation from our agency work: developer accounts should be created in your name (or your company's), never the agency's. If you outsource development, put account ownership in the contract and give the agency admin access instead. Account ownership is app ownership — transfers after the fact are painful.

Step 2: Prepare a Release-Ready Build

A store build is not the same as the debug build you tested with.

On iOS, the app is compiled with Xcode 26 against the iOS 26 SDK, signed with a distribution certificate and provisioning profile (Xcode's automatic signing handles both), and uploaded via Xcode or Transporter. Note one side effect of the SDK requirement: apps built with the iOS 26 SDK inherit the new system look in standard UI components unless you opt out, so review every screen after upgrading.

On Android, the release format is the Android App Bundle (AAB); APKs are for test distribution only. Enable Play App Signing so Google stores your signing key — it eliminates the risk of losing the key and with it the ability to ever update your app. Make sure the build targets the current required API level.

Before uploading, run through these checks on both platforms:

• Version and build numbers incremented?
• Test server URLs, debug logging and staging accounts stripped from the package?
• Does the app launch without crashing on older, low-memory devices?
• Do screens fail gracefully when the network drops?
• Are third-party SDKs on current versions?

Boring checks — but "the app doesn't work properly" is the single biggest rejection cause, as the numbers below show. Our free interactive app launch checklist covers every pre-submission item in one place.

Step 3: Build Your Store Listings

The listing is both a review artifact and your sales page. You need: app name, short and long descriptions, category, keywords (App Store only), support and privacy policy URLs, and contact details.

Visual requirements differ between the stores:

Apple scales the 6.9-inch iPhone and 13-inch iPad sets down for smaller devices automatically, and rejects images containing alpha channels (screenshot specifications). Google recommends at least four screenshots at 1080 px or higher to qualify for featured placements (Play graphic assets).

A practical rule: your first two screenshots should explain what the app does without any reading. Most users never see the rest.

Step 4: Privacy Declarations and Age Ratings

Both stores require you to declare what data your app collects: the App Privacy section on the App Store, the Data safety form on Google Play.

The declarations must be consistent in three places: the store form, your privacy policy page, and what the app actually does. An app that declares "no location collection" while an embedded SDK sends location data may pass review — and get removed from the store later, when automated scanning catches the mismatch.

Age ratings changed materially in 2025-2026. Apple replaced the old 12+ and 17+ tiers with 13+, 16+ and 18+, added new questions about in-app controls, health topics and violence, and made answering them mandatory — since January 31, 2026, apps without updated answers cannot ship updates. Budget an hour for the questionnaire and answer honestly; misdeclared ratings are grounds for removal.

If you operate in regulated markets, layer local privacy law on top: GDPR in Europe, KVKK in Turkey. A principle worth adopting everywhere, drawn from the Turkish DPA's mobile app privacy guidance: users who refuse optional permissions must still be able to use the app's core features. Blocking the app until a location permission is granted is a red flag for both regulators and store reviewers.

Step 5: Complete the Testing Phase

Testing works completely differently in the two stores, and it is the item that actually sets your launch date.

TestFlight (iOS) is optional. You get 100 internal testers with instant access and up to 10,000 external testers; the first build shared with an external group goes through a short Beta App Review (TestFlight). Even though it's optional, skip it at your peril — real-device feedback is far cheaper than a store rejection.

Google Play's closed test is mandatory for personal accounts created after November 13, 2023. The rule: before you can apply for production access, at least 12 testers must be opted in to your closed test continuously for the last 14 days, and they must actually install and use the app (closed testing requirement). Organization accounts are exempt.

Three traps to avoid:

1. Inviting testers is not enough. Each tester must accept the invitation and install the app with the enrolled Google account.
2. The 14-day clock has conditions. It runs only after the release is approved and 12 testers are opted in; if someone drops out mid-way, you can lose time.
3. An organization account saves two weeks. If you have a registered company, use it — the closed test requirement disappears entirely.

Plan the Android launch around this from day one. If a marketing date is fixed, start the Google Play process at least a month ahead.

Step 6: Submit and Manage the Review

With everything prepared, submission itself takes minutes; managing the review well is what saves days.

On the App Store, select the build, write release notes and submit. Apple states that most submissions are reviewed within 24 hours. In practice, first submissions, apps using sensitive permissions and brand-new accounts take longer.

On Google Play, promote the release to production and the review starts. Categories with extra declarations — health, finance, apps for children — take longer.

Three things reliably speed up review:

• Provide a demo account. If your app requires login, reviewers must be able to get in. A reviewer who cannot log in rejects the app.
• Use the review notes. Special hardware, payment flows or region-specific features? Explain exactly how to test them.
• Make the listing match the app. Every feature your description promises must exist in the build; "coming soon" screens are a rejection trigger.

If you do get rejected, read the notice carefully — it names the violated guideline. Fix, resubmit, and you keep your place in the process. Apple's own 2024 data shows 295,109 initially rejected submissions were approved after the developers fixed the issues.

Step 7: Updates, Fees and Payouts

Publication is a starting line. Keeping the app in the stores takes ongoing work.

Update rhythm. Every release goes through review again, though updates usually clear faster than first submissions. Both operating systems ship major versions yearly, so plan at least one compatibility update per year — a realistic maintenance budget is 15-20% of the original development cost annually.

Commissions. If you sell digital content or subscriptions, the store commission is part of your revenue model. Apple charges 15% under the Small Business Program (for developers under $1 million in the prior year) and 30% above it. On Google Play, most markets outside the US/UK/EEA keep 15% on the first $1 million per year and 30% beyond, with subscriptions at 15% regardless of volume. Apps selling physical goods or services — e-commerce, bookings — can use external payment providers commission-free.

Payouts and tax. Stores pay out after thresholds and fiscal periods close. Keep the tax form, payment profile and bank account holder consistent — a company account paying out to a personal bank account will be blocked.

Visibility. With release volume doubling in 2026, being in the store no longer means being found. Your app name, subtitle and first two screenshots drive conversion; the first month after launch is the best window to iterate on them using real search and uninstall data.

Why Apps Get Rejected

Apple's own 2024 App Store Transparency Report puts numbers on rejection. Apple processed 7.77 million submissions during the year and rejected 1.93 million of them:

The table tells one story: the dominant cause of rejection is not obscure policy — it is apps that simply don't work properly. A crashing screen, an empty tab or a dead link produces more rejections than every other category combined.

The four practical mistakes we see most often: a privacy policy URL that doesn't load, no working demo account for the reviewer, permission prompts that don't explain why the permission is needed, and screenshots that don't match the real interface. All four are checkable in half an hour before you submit.

Platform-specific costs and store processes are covered in more depth in our Android and iOS development guides.

Frequently Asked Questions

How long does it take to publish an app?

On the App Store, a realistic total is 3-7 days: Apple reviews most submissions within 24 hours, and account and asset preparation add the rest. On Google Play, new personal accounts need the 12-tester, 14-day closed test, which stretches the total to 3-4 weeks.

How much does it cost to publish an app?

The mandatory store costs are $99/year for the Apple Developer Program and a one-time $25 for Google Play Console. A privacy policy page, domain and backend hosting come on top. Development itself is a separate budget — typically the largest one.

Can I publish an app without a company?

Yes. Both stores accept individual developer accounts with identity verification. The trade-offs: personal Google Play accounts must pass the 14-day closed test, and on the App Store your personal name appears as the developer instead of a brand.

Do I need a D-U-N-S number?

Only for organization accounts — both stores require it for companies, neither for individuals. It is issued free by Dun & Bradstreet but can take up to 30 days, so apply early if you want to publish under your company name.

What happens if my app gets rejected?

The rejection notice names the violated guideline, usually with screenshots. You fix the issue and resubmit at no cost, with no penalty or cooldown. Both stores also have an appeal process if you believe the decision was wrong.

Which store should I publish on first?

If you are on a deadline, start the Google Play process first — the closed test creates a fixed two-week wait. Prepare your App Store submission while the Android test runs, and you can launch on both stores in the same week.

Can a development agency handle publishing for me?

Yes, and it is standard practice — store listings, declarations, builds and rejection fixes are part of a full-service engagement. Just make sure the developer accounts are registered in your name and the agency works with admin access; account ownership should always stay with you.

Is publishing cheaper if I build with a team in Turkey?

Store fees are identical worldwide, but the development behind the app is where budgets differ: Turkish agency rates typically run well below Western European and US rates for the same stack. Our cost guide breaks down the numbers.

---

Publishing is less a technical challenge than an organizational one. Account verification, D-U-N-S applications and closed tests can all run in parallel — or cost you a month if handled one by one. Open the accounts, gather the documents and recruit your testers before the final build is ready.

At Master Web, store submission is part of every app we build — accounts, listings, declarations and review management included in our mobile app development service. If your app is approaching launch or your submission is stuck, get in touch and we'll map the fastest route to approval together.