Publishing on the App Store and Google Play in 2026: Timelines, Costs, and 7 Hidden Requirements That Could Derail Your Launch

In Short

Publishing an app on the App Store costs $99/year for an Apple Developer Program membership, plus around 2–5 days for the review of a new app (updates are typically reviewed within 24–48 hours). However, this doesn’t include the time needed to register the account itself. For companies, Apple requires a D-U-N-S Number and business verification, and the entire enrollment process can take anywhere from 1 to 4 weeks.

Google Play has a lower upfront cost — a one-time $25 fee. Mandatory closed testing (at least 12 testers for 14 consecutive days) applies only to personal developer accounts created after November 13, 2023. Organization accounts are exempt from this requirement, but they have their own verification process involving a D-U-N-S Number and business documents, which can take 2–4 weeks.

Starting in 2026, Google is introducing another requirement — Android Developer Verification. From September 30, 2026, in four countries (Brazil, Indonesia, Singapore, and Thailand), apps from developers who haven’t verified their identity using a government-issued ID won’t be installable on certified Android devices. The requirement is expected to expand globally starting in 2027. The bottom line: in 2026, the actual time from finished code to a live store listing depends heavily on the type and age of the developer account — anywhere from a few days for an update on an already verified account to 4–6 weeks for a new organization account and its first release.

7 Things You Need to Know Before Publishing

1. Developer account costs differ not just in price, but also in how you pay

The Apple Developer Program costs $99 per year. It’s an ongoing subscription, and if you don’t renew it, your app can be removed from the App Store even if it has already been approved.

Google Play Console charges a one-time $25 registration fee, after which the account remains active indefinitely. Over five years, publishing through Apple costs roughly 20 times more than Google’s initial registration fee alone. That’s worth including in the overall project budget rather than treating it as a one-off launch expense.

2. Apple’s official review times aren’t always what you’ll see in practice

Apple says that around 90% of submissions are reviewed within 24 hours, with a typical review time of 24–48 hours. According to the same official figures, the first release of a new app generally takes 2–5 days.

These timelines also cover updates to previously approved apps and should be treated as targets rather than guarantees. In practice, developers in 2026 have been widely reporting delays ranging from 7 to 30+ days, with some cases reaching 45 days.

One reason is the sharp increase in app submissions. Releases in Q1 2026 grew by 60% year over year, while iOS releases alone increased by 80%. Much of that growth has been linked to the wave of AI-generated and “vibe-coded” apps, which has put additional pressure on review queues. So when planning a launch, it’s safer to build in extra time rather than relying solely on Apple’s official estimates.

Google Play is somewhat more predictable. For accounts with an established publishing history, reviews usually take 1–3 days. New accounts may face review times of 7–14 days, not including the mandatory testing stage that applies to certain personal accounts (see point 3).

3. Google Play may require closed testing before you can publish

This requirement applies only to personal developer accounts created after November 13, 2023. Before Google allows an app to move into production, it must complete a closed test with at least 12 opted-in testers for 14 consecutive days.

Organization accounts are exempt from this requirement. Instead, they go through business verification using a D-U-N-S Number and supporting company documents, which typically takes 2–4 weeks. In other words, the delay doesn’t necessarily disappear — it simply takes a different form.

This stage should be factored into your launch schedule, especially when there’s a hard deadline such as a public announcement, funding round, or seasonal launch. It’s also important to determine in advance which type of developer account will be used.

4. Android is introducing developer identity verification in 2026

Google is rolling out Android Developer Verification, a system that links an app to a verified developer identity using a government-issued ID and a one-time $25 fee. Importantly, this applies not only to apps distributed through Google Play, but also to apps installed through third-party stores or downloaded directly as APK files.

The first phase begins on September 30, 2026, in four countries: Brazil, Indonesia, Singapore, and Thailand. Certified Android devices in these markets will block the installation of apps from unverified developers. A broader global rollout is planned starting in 2027.

For hobbyist developers and educational projects, Google is offering a simplified option without ID verification or a fee, but it will be limited to a maximum of 20 devices.

5. Apple’s most common reason for rejection isn’t bugs — it’s privacy compliance

According to Apple, failure to comply with Guideline 5.1.1 (Privacy) is the most common reason for app rejection, more frequent than any other individual guideline violation.

Typical issues include a missing Privacy Policy link in App Store Connect or inside the app, App Privacy Labels that don’t match the data the app actually collects, and missing App Tracking Transparency prompts where they’re required.

The practical takeaway: prepare your privacy documentation and declarations for every third-party SDK before submitting the app for review — not after receiving your first rejection.

6. Guideline 4.3 targets “copycat” apps and overcrowded categories

Guideline 4.3(a) applies to developers who publish nearly identical apps under different Bundle IDs — for example, creating a separate version of essentially the same app for every city.

Guideline 4.3(b) became stricter in 2026. In already saturated categories — such as flashlight apps, wallpapers, and basic timers — Apple may reject new submissions if they don’t provide a “meaningfully different or improved experience” compared with existing apps.

For niche B2B and enterprise applications — such as software for managing EV charging stations or parking facilities — this usually isn’t a major concern. For consumer utilities, however, it’s a risk worth evaluating during the concept stage rather than after development is complete.

7. Banking and tax forms are a bottleneck many teams overlook until the last minute

Both Apple and Google require developers to complete their payment and tax profiles before an app can generate revenue — even if monetization is as simple as charging users to download the app.

In App Store Connect, this means accepting the Paid Applications Agreement and completing the relevant tax forms, such as W-8/W-9 forms and their equivalents for developers outside the U.S. On Google Play, you’ll need to configure a Payments profile through your Google account.

Banking and tax information can take several business days to verify on either platform, and this process is separate from the app review itself. If you leave it until the last minute, a monetized launch can be delayed even when the app itself has already been approved.

iLab.md develops and publishes React Native mobile apps — from the initial idea to launch on the App Store and Google Play, including developer account setup, privacy documentation, and navigating the review process.

Sources:
App Review Guidelines — Apple Developer
App testing requirements for new personal developer accounts — Google Play Console Help
Understanding Android developer verification — Android Developer Console Help