This guide walks through exactly what to transfer, in what order, so your new developer can pick up where the old one left off — without downtime, lost ratings, or a rebuild from scratch.

Quick Answer

To move your app to a new developer without losing progress, transfer four things in order: the source code repository, the App Store Connect and/or Google Play Console app listing (using Apple’s and Google’s official in-house transfer tools, not a rebuild), any backend/API keys and admin accounts, and the app’s domain or web assets. Do this while the original developer still has access, and confirm each transfer with a test build before cutting ties.

Step 1: Get the Source Code Under Your Control First

Before anything else, make sure you — not the developer — own the code repository. If it’s on GitHub, GitLab, or Bitbucket, ask to be added as an owner/admin on the organization or repo, then either transfer ownership to an account you control or have the developer transfer the repo directly to your organization. GitHub, for example, has a built-in ‘Transfer ownership’ option under repository settings that preserves commit history, issues, and stars.

If the code lives only on the developer’s personal machine or account, insist on a full export before the relationship ends — including the complete git history, not just a zip of the current files. You want history intact so a new developer can see how features were built and roll back if needed.

Also collect: the build configuration (Xcode project settings, Android Gradle files), any CI/CD pipeline configs, environment variable files (kept private, shared securely), and documentation like a README or setup guide. A codebase with no setup instructions can cost a new developer days just to get running locally.

Step 2: Transfer the App Store and Google Play Listings

This is the step most people get wrong — they think a new developer just resubmits the app under a new account, which loses the app’s existing reviews, ratings, download history, and store URL. Instead, use each platform’s official transfer feature.

On iOS: in App Store Connect, the Account Holder goes to My Apps, selects the app, opens App Information, and clicks Transfer App. You’ll need the receiving Apple Developer Program account’s Team ID. The receiving developer gets a notification and must accept it within 60 days under Agreements, Tax, and Banking in their own App Store Connect account. Once accepted, the app stays live on the App Store the whole time — same URL, same reviews, no downtime.

On Android: transferring an individual app between Google Play developer accounts is handled through Google Play Developer Support rather than a self-serve button. Both accounts need to be active and verified, and you’ll need each account’s registration transaction ID. Google typically reviews and approves these requests within a couple of business days. Ratings, reviews, and the store listing carry over automatically, but some reports (like historical payout and earnings data) do not transfer, so export those first if you’ll need them.

If you’re instead handing over control of your whole developer account (rather than one app), both Apple and Google support adding the new developer as an admin/owner and then removing yourself, which is simpler than an app-by-app transfer but gives them access to everything tied to that account.

Step 3: Hand Over Backend, Accounts, and Third-Party Services

Most apps depend on services outside the app store: a backend hosting provider, a database, push notification services, analytics, crash reporting, payment processors, and any third-party APIs (maps, auth, AI, etc.). Make a list of every service the app calls and confirm who owns the account for each one.

Where possible, put these accounts under your own company’s ownership (not the departing developer’s personal login) and add the new developer as a team member with the access level they need. For services that can’t easily change owners, rotate API keys and passwords once the handoff is complete, so the old developer no longer has live credentials.

Don’t forget app-specific credentials that live outside any dashboard: push notification certificates/keys, code signing certificates, provisioning profiles, and keystore files for Android. If your Android app is enrolled in Play App Signing (the default for any app that uploads an Android App Bundle, which Google has required for new apps since August 2021), losing your local upload key isn’t fatal — the primary owner of the Play Console account (admin and editor roles don’t have access to this option) can open the App Integrity page in Play Console and submit an upload key reset request, then keep publishing updates under the same listing once Google approves it, usually within a couple of business days. That said, you should still archive the original keystore securely: apps that predate Play App Signing and never enrolled don’t have this self-service recovery option, and losing the actual app signing key itself — as opposed to just the upload key, which Google securely holds a copy of — is not recoverable.

Tips / Common Mistakes

Keep the old developer’s access active until the new developer has confirmed they can build and deploy the app successfully — don’t revoke access first and troubleshoot second.

Do a test build immediately after each transfer step. A repo that ‘transferred fine’ but won’t compile, or a Play Console transfer that’s missing the signing key, is much easier to fix while the original developer can still answer questions.

Put everything in writing, including exactly what’s being transferred and by when, especially if the relationship with the previous developer ended on bad terms.

Store your Android keystore, Apple certificates, and any master credentials somewhere your company controls (a password manager or secrets vault your business owns), not solely in an individual developer’s personal accounts.

If the app uses a custom domain for its website, marketing pages, or API, confirm you (not the developer) are listed as the registrant on the domain registrar account, and that DNS access isn’t locked to the old developer’s login.

Explore more: more app development guides.

App developer transfer FAQs

Will my app lose its reviews and ratings when I switch developers?

Not if you use the official App Store Connect or Google Play transfer process instead of resubmitting as a new app. Reviews, ratings, download history, and the store URL all stay intact through an official transfer.

What’s the single most important thing to secure before switching developers?

Your code repository and your signing credentials (Apple certificates and the Android upload keystore). Most Android apps enrolled in Play App Signing can recover from a lost upload key through Google’s reset process, but it’s still far simpler to hand over the original files than to go through recovery — and apps that never enrolled in Play App Signing don’t have that safety net.

How long does an app transfer take?

An App Store Connect transfer can complete once the receiving account accepts it, though the recipient has up to 60 days to do so. A Google Play app transfer through Developer Support typically takes a couple of business days for approval once both accounts are verified and the request is submitted.

Can I switch developers without the app going offline?

Yes. Official app store transfers are designed to happen without taking the app down. Backend and hosting migrations require more care — plan those during low-traffic periods and test thoroughly before pointing users at new infrastructure.

Build It With GTStudios

Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.

Want dev news in your inbox? Subscribe to the free newsletter.

Photo by Nubelson Fernandes on Unsplash.

The post How to Move Your App to a New Developer Without Losing Progress appeared first on GTStudios.

This guide walks through what each account actually requires, how long each one takes to get approved, and how to decide which to start first based on your budget, business structure, and launch timeline.

Quick Answer

Start whichever account has the longer approval wait — usually the Apple Developer Program if you’re enrolling as an organization, since it requires a D-U-N-S number and manual review that can take anywhere from a few days to a few weeks. Google Play Console approval is typically faster (often within a couple of business days) once identity verification clears, but its $25 fee and the new personal-account testing rule mean solo developers should also start early rather than at the last minute.

What Each Account Actually Requires

Apple Developer Program costs $99 per year (Enterprise Program is $299/year for internal-only distribution) and requires an Apple ID with two-factor authentication. If you’re enrolling as an individual/sole proprietor, you just need your legal name and a matching payment method. If you’re enrolling as an organization, Apple requires a legal entity, a website, a D-U-N-S number that matches your business’s legal name in the D&B database, and someone with legal authority to accept Apple’s agreements. Getting a D-U-N-S number is free and usually takes a few business days, but can stretch closer to 30 days without expedited processing — and Apple’s own review after that can take anywhere from a few days to a few weeks, especially for organizations.

Google Play Console has a one-time $25 registration fee (no annual renewal) but now requires identity verification for every new developer — a government-issued ID (and sometimes a selfie) for individuals, or a D-U-N-S number for organization accounts. Verification typically completes within a few hours to about two business days. The bigger catch: any personal (non-organization) developer account created after November 13, 2023 must run a closed test with at least 12 opted-in testers for 14 consecutive days before Google will grant production access — so even though registration is quick, reaching a live listing isn’t instant either.

How to Decide Which to Set Up First

Base the decision on which process has more unknowns for your situation, not which store you personally prefer. If you’re enrolling Apple as an organization, start there first — the D-U-N-S lookup and Apple’s manual review are the least predictable steps in either process, and starting early gives you buffer room while you build the app itself.

If you’re a solo developer without a registered business, Apple’s individual enrollment is usually the faster of the two to get approved, but Google’s 12-tester, 14-day closed testing requirement means you should open your Play Console account and start recruiting testers as early as possible, since that clock only starts once your app is in testing — not once you register.

If cost timing matters (say, you want to delay spending until you’re closer to launch), Google’s one-time $25 fee is easier to front early since it doesn’t recur, while Apple’s $99 is an annual cost you may not want to start until you’re closer to submission.

If you’re only launching on one platform initially, this whole question is moot — just start that platform’s account as soon as you’re seriously working on the app, since both processes can run in parallel with development.

Tips / Common Mistakes

Don’t wait until your app is finished to start either account — identity verification and D-U-N-S lookups can stall on mismatched business names, expired IDs, or unverifiable addresses, and you don’t want that discovered the week you planned to launch.

Make sure your legal business name matches exactly across your D-U-N-S registration, your Apple enrollment, and your Google organization account — small mismatches (abbreviations, punctuation, “LLC” vs “L.L.C.”) are a common cause of rejected or delayed verification.

If you’re a solo developer on Google Play, start lining up your 12 testers before you’re ready to submit — friends, beta communities, or testing services can fill this, but the 14-day clock doesn’t start until testers are actually opted in.

Keep your payment method valid for both — Apple can suspend renewal if the annual charge fails, and Google’s registration fee won’t be refunded if identity verification later fails, so double-check your ID documents match your account details before paying.

Explore more: More App Development guides.

Apple Developer Account vs Google Play Console FAQs

Can I set up both accounts at the same time?

Yes, there’s no rule against running both enrollments in parallel. Many developers do this specifically because Apple’s organization review can take longer, so starting both at once minimizes total wait time before you can submit to either store.

Is Google Play Console really cheaper than Apple Developer Program?

Yes — Google Play Console is a one-time $25 fee with no renewal, while Apple Developer Program is $99 every year you want your app to stay live. Over multiple years, Apple is the more expensive of the two.

Do I need a D-U-N-S number for both platforms?

Only if you’re enrolling as an organization on either platform. Individual/personal accounts on both Apple and Google skip the D-U-N-S requirement, though Google still requires personal ID verification either way.

How long should I budget before my planned launch date?

For an organization account on either platform, budget at least 3-4 weeks to account for D-U-N-S processing and manual review delays. For individual accounts, a week or two is usually enough, but add 14+ days if you’re a solo Android developer who needs to clear Google’s closed testing requirement.

Build It With GTStudios

Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.

Want dev news in your inbox? Subscribe to the free newsletter.

Photo by Fotis Fotopoulos on Unsplash.

The post Apple Developer Account vs Google Play Console: Set Up First? appeared first on GTStudios.

This guide walks through a simple framework for writing a reply that actually helps, ready-to-adapt templates for the most common complaint types, and the specific rules Apple and Google enforce on App Store Connect and Google Play Console — character limits, editing, and notifications — so you don’t find out the hard way that your reply got cut off or never reached the reviewer.

Quick Answer

Reply promptly, address the specific problem the reviewer mentioned (not a generic apology), take responsibility without being defensive, and give a concrete next step — a fix that’s already shipped, a workaround, or an invitation to email support with more detail. Keep it short: Google Play caps replies at 350 characters, and even on the App Store, where there’s no official cap, brevity reads better than a corporate script.

A 5-Step Framework for the Reply Itself

Read it twice before responding. A one-star review written in frustration is rarely about your product being worthless — it’s usually one specific bug, a confusing screen, or a bad support experience. Reacting within minutes, while you’re still annoyed, is how replies turn defensive.

Name the actual issue. ‘Sorry you had a bad experience’ could be copy-pasted onto any review. ‘Sorry the export button crashed the app on your device’ shows you actually read it — and shows everyone else reading the thread that you pay attention.

Apologize for the experience, not necessarily the facts. You can acknowledge frustration without conceding a factual point you know is wrong (a review blaming your app for a known OS-level bug, for example). State what’s true, briefly, and move on.

Give a concrete next step. ‘Fixed in version 4.2, out now’ or ‘Please email support@yourapp.com with your order number and we’ll sort it same day’ does more work than any amount of apologizing. If it’s already fixed, say so — that’s often what turns a rating around.

Stop there. Don’t argue, don’t over-explain, and per Google’s own guidance, don’t explicitly ask the reviewer to raise their rating — focus the reply on solving their problem, not on the star count.

Example Replies You Can Adapt

A bug that’s already fixed: ‘Hi [name], you’re right that the export button was crashing on some Android 14 devices — that’s fixed in version 4.3, which is live now. Update and it should work; if it doesn’t, email support@yourapp.com and we’ll dig in.’ Naming the exact bug and version number is what separates this from a template.

A missing feature or design complaint: ‘Thanks for the honest feedback — dark mode isn’t in the app yet, but it’s on our roadmap based on requests like this one. In the meantime, lowering your device brightness in low-light use helps a bit. Appreciate you flagging it.’ This doesn’t pretend the gap doesn’t exist, which reads as more credible than a deflection.

A pricing or subscription complaint: ‘I hear you on the price — we priced the annual plan to work out cheaper per month than the monthly option if that helps. If you were charged after canceling, email support@yourapp.com with your receipt and we’ll sort it directly.’ Billing disputes belong in a private channel, not a public back-and-forth, so the reply should route there fast.

A review that’s a misunderstanding or user error: ‘Sorry for the confusion — the sync happens automatically every time you open the app, so there’s no manual button to press. If it’s still not syncing on your end, email us and we’ll take a look at your account.’ State the correct behavior plainly, once, without sounding like you’re correcting the reviewer’s intelligence.

An abusive, spam, or policy-violating review: don’t reply at all. Use Apple’s ‘Report a Concern’ option in App Store Connect or Google Play’s reporting flow instead — reporting doesn’t notify the reviewer, whereas replying does, and a public reply to an abusive review just gives it more visibility.

The Platform Rules You Need to Know

On Google Play Console, developer replies are capped at 350 characters of plain text (HTML tags get stripped and don’t count toward the limit), so write tight. The user gets a push and email notification the first time you reply to a given review — replying again to the same thread doesn’t re-notify them, so make the first reply count. Google’s own guidance is explicit that 1- and 2-star reviews deserve a hand-written reply rather than a canned template.

On the App Store, accounts with the Account Holder, Admin, or Customer Support role in App Store Connect can respond to reviews. Apple doesn’t publish an exact character limit, but replies can run considerably longer than Google Play’s 350-character cap. The reviewer is notified when you first respond, and you can edit or delete your response at any time — you don’t even need to be the person who originally wrote it. Only the latest version is shown publicly, with a notation marking it as edited.

App Store Connect also lets you turn on email alerts for when a customer edits a review you’ve already replied to, so you’re not relying on manually re-checking old threads to catch an updated rating.

If a review is abusive, spam, or violates the store’s terms, don’t reply to it at all — use Apple’s ‘Report a Concern’ option or Google Play’s reporting flow instead. Reporting doesn’t notify the reviewer, whereas replying does.

Tips and Common Mistakes

Don’t copy-paste the same reply across multiple one-star reviews — it’s easy for readers to spot a template, and it undercuts the sincerity of the apology.

Don’t argue in public. Even if the reviewer is factually wrong, a back-and-forth in a public reply thread makes your app look worse to everyone browsing, not just the reviewer.

Don’t let ‘we’re looking into it’ be the last word. When the fix ships, go back and reply again or edit your existing reply referencing the update — this is exactly the kind of follow-through both Apple and Google’s guidance points toward.

Don’t offer refunds, discount codes, or account-specific fixes in the public reply. Route anything involving personal or billing details to email or in-app support, and keep the public-facing reply generic enough to post without exposing the reviewer’s account info.

Don’t skip one-star reviews because ‘that user is already gone.’ The reply is really aimed at the hundreds of undecided people who read reviews before installing — a calm, specific response to criticism often reassures them more than a wall of five-star reviews does.

Photos

Frequently Asked Questions

Can I edit an App Store or Google Play review response after posting it?

Yes on both. In App Store Connect you can edit or delete your response at any time, and only the latest version displays publicly, marked as edited — you don’t even need to be the original author to edit it. Google Play Console also lets you revise your reply at any time; the updated text simply replaces the old one.

Is there a character limit for review replies?

Google Play Console enforces a hard 350-character limit on developer replies, with HTML tags stripped and excluded from the count. Apple doesn’t publish an exact cap for App Store Connect replies, but shorter is still better — reviewers and future readers skim, they don’t read corporate statements.

Will replying to a one-star review get the user to change their rating?

It can, but it’s not guaranteed and you shouldn’t explicitly ask for it. A specific, helpful reply — especially one pointing to a fix that’s already shipped — is what sometimes prompts reviewers to go back and raise their rating on their own. Google’s guidance specifically advises against asking directly.

Should I reply to or just report an abusive or clearly fake review?

Report it instead of replying. Both Apple’s ‘Report a Concern’ flow in App Store Connect and Google Play’s review-reporting option exist precisely for spam, abuse, and policy-violating reviews, and reporting doesn’t notify the reviewer the way a reply does.

Who is allowed to reply to reviews on each platform?

On App Store Connect, only accounts with the Account Holder, Admin, or Customer Support role can post or edit review responses. Google Play Console reply permissions are controlled through the account’s user-management settings, so check that a team member has the right access level before assuming they can respond.

Build It With GTStudios

Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.

Want dev news in your inbox? Subscribe to the free newsletter.

The post How to Respond to a One-Star App Store Review (+ Templates) appeared first on GTStudios.

This checklist walks through what to line up before submission, how to handle the review and rollout process on both App Store Connect and Google Play Console, and what to monitor daily once real users start opening your app.

Quick Answer

In launch week, submit early in your platform’s review queue, roll out gradually on Android instead of releasing to 100% of users at once, monitor crash reports and reviews daily, and have a rollback or hotfix plan ready before you hit publish.

Before You Submit: Final Pre-Launch Checks

Test the actual build you’re about to submit, not an older debug version. Install the release build (or a TestFlight/internal testing track build) on a couple of real physical devices, not just simulators, and walk through signup, core actions, purchases, and logout end to end.

Lock down your store listing assets: screenshots for each required device size, an app icon that matches your submitted binary, a clear short description, and accurate age rating and privacy answers. Mismatches between what your app actually does and what your privacy labels or data-safety form say are a common cause of rejections and delays on both platforms.

Set up crash and analytics monitoring (Firebase Crashlytics, Sentry, or similar) before launch, not after. You want data flowing from the first install, since the first 48-72 hours after real users arrive is when you’ll catch device- or OS-specific bugs your testing missed.

Prepare a support channel — an email address, in-app feedback form, or help page — and put it somewhere users will actually find it. Early reviewers often mention unresolved bugs publicly if they can’t find a way to report them privately first.

Submission, Review, and Rollout: What to Expect

On iOS, submit through App Store Connect and expect App Review to take anywhere from about 24 hours to a few days for a first-time submission; updates to an already-approved app tend to move faster since reviewers only need to check what changed. Submitting early in the week gives you buffer if Apple asks follow-up questions through the Resolution Center, since a same-day reply usually gets you back in the queue faster than leaving it overnight.

On Android, Google Play’s review for a brand-new app listing typically runs from a few hours up to a couple of days, though first-time developer accounts and apps in sensitive categories can take longer. Once approved, use a staged rollout rather than releasing to everyone immediately — Google Play Console lets you start at a small percentage of users (commonly 5-10%) and increase it manually as you confirm crash rates and ratings look healthy. Note that staged rollouts apply to updates, so for a brand-new app’s very first release you won’t have this option, which is exactly why pre-launch device testing matters so much.

Once live, don’t just wait for downloads. Check App Store Connect’s App Analytics and Play Console’s Android vitals daily for crash rate, ANR (app not responding) rate, and uninstall spikes. A rising crash rate on a specific OS version or device model is your earliest warning that something testing missed is now affecting real users.

Tips and Common Mistakes

Don’t submit late on a Friday if you can help it — if a reviewer flags an issue, you may lose the whole weekend waiting for a response window, and support requests from early users pile up faster than a small team can answer them.

Reply to every early review, especially critical ones. A quick, human response to a 2-star review about a fixable bug often gets it updated once the fix ships, and it signals to future readers that the app is actively maintained.

Have a hotfix path ready before launch: know how fast you can ship a patched build if a critical bug appears, and keep your previous stable build handy in case you need to pause a staged rollout on Android.

Avoid changing your app’s name, icon, or main category right after launch. Early keyword rankings and app-store search visibility take time to build, and resetting them in the first week can cost you the visibility you just earned.

Don’t ignore your data-safety/privacy forms after submission — if a later update adds a new SDK or data collection, update those disclosures too, since mismatches are a recurring cause of rejections and account-level review escalations.

Explore more: More app development guides.

Mobile app launch checklist FAQs

How long does it take for an app to go live after submission?

For iOS, first-time App Store review commonly takes anywhere from about a day to several days; updates usually go faster. For Android, Google Play review for a new app is typically a few hours to a couple of days, though it can run longer for new developer accounts or sensitive categories.

Should I release to 100% of users right away on Google Play?

No — use a staged rollout for updates, starting around 5-10% of users and increasing gradually while you watch crash and uninstall data. This only applies to updates; a brand-new app’s first release goes out to everyone once approved, which is why thorough pre-launch testing matters most for version 1.0.

What should I monitor in the first week after launch?

Watch crash and ANR rates in Crashlytics or your monitoring tool, check new reviews daily so you can respond quickly, and keep an eye on install-to-uninstall trends and any support emails coming in — these tell you faster than store rankings whether something is broken.

What’s the most common reason apps get rejected during launch week?

Mismatches between what the app does and what’s declared in privacy/data-safety forms, broken core flows found on a device or OS version that wasn’t tested, and incomplete or misleading metadata (screenshots, descriptions) are among the most common review issues on both platforms.

Build It With GTStudios

Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.

Photo: ICent Powered by Neel-Tech / CC BY-SA 4.0, via Wikimedia Commons.

The post Mobile App Launch Checklist: Your App’s First Week Live appeared first on GTStudios.

This guide gives you the official fee for each platform side by side, what a full launch actually costs on Android versus iOS, and the extra costs — accounts, testers, compliance — that trip up first-time publishers.

Quick Answer

The Apple Developer Program — the official membership required to publish on the App Store — costs $99 per year (a separate Apple Developer Enterprise Program for internal-only company apps is $299/year). The Google Play Console — the official account required to publish on Google Play — costs $25, paid once, with no annual renewal.

Those two fees are the entire mandatory cost of publishing. Beyond them, both stores take a commission when you sell a paid app, in-app purchase, or subscription, and Google requires new individual accounts to complete a 12-tester testing period before they can go live.

Apple Developer Program Fee (Official): $99/Year

To publish on the App Store you need an Apple Developer Program membership, officially priced at $99/year on Apple’s own developer.apple.com/programs page. It’s a flat fee regardless of how many apps you publish or how much revenue they generate, and it renews automatically as an annual subscription until you cancel — so it’s easy to let it lapse right before a launch if you’re not watching for the renewal charge.

Nonprofits, accredited educational institutions, and government entities can apply for an official fee waiver through Apple. Setting up an organization account (instead of an individual one) also requires a D-U-N-S number, which is free to obtain but can take a few days to a few weeks to process — worth budgeting for if you’re publishing under a company name.

Google Play Console Fee (Official): $25 One-Time

Google Play’s official developer registration fee is $25, charged once when you create your Play Console account — confirmed on Google’s own Play Console Help pages. There’s no annual renewal, no per-app charge, and no monthly cost. Once verified, that single account lets you publish as many apps as you want for the life of those apps.

The catch for new developers: personal accounts created after November 2023 can’t jump straight to production. Google requires a closed test with at least 12 opted-in testers who stay active for 14 continuous days before you can apply for production access — testers have to actually open and use the app, and dropping below 12 active testers can reset the clock. Organization accounts and personal accounts created before November 2023 are exempt.

Apple Developer Program Fee vs. Google Play Console Fee, Side by Side

Put next to each other, the two official fees aren’t structured the same way at all: Apple’s $99 is a recurring annual charge tied to your membership staying active, while Google’s $25 is a single upfront charge that never comes due again. Miss Apple’s renewal and your apps come off the App Store; Google’s fee has no renewal to miss.

Both fees are per developer account, not per app — publishing five apps under one Apple account still costs $99/year total, and five apps under one Google account still costs $25 total, ever.

How Much Does It Cost to Publish an App on Android (Google Play)?

For a free app, the total mandatory cost to publish on Google Play is the one-time $25 Play Console registration fee — nothing else is required by Google. If you’re a new individual developer, factor in the time (not money) to line up 12 testers for a 14-day closed test before you can request production access.

If your app sells anything, Google also takes a commission (covered below), and after production access is granted, Google’s review of your submission typically takes about a week.

How Much Does It Cost to Publish an App on the Apple App Store?

For a free app, the total mandatory cost to publish on the App Store is the $99/year Apple Developer Program fee — that’s your entire ongoing platform cost if there are no in-app purchases. The $299/year Enterprise Program is a separate product for private, internal-only distribution to employees and isn’t required for (or usable for) public App Store listing.

If your app sells anything, Apple takes a commission on top of the membership fee, and app review can add review-queue time to your launch timeline.

Commission: What Apple and Google Take From Sales

Apple runs a simple split: 30% standard, dropping to 15% for developers enrolled in the App Store Small Business Program (available if you earned $1 million or less in App Store proceeds the prior calendar year). Subscriptions also auto-drop to 15% starting in their second year, regardless of program enrollment.

Google’s commission is not a copy of Apple’s. In most of the world it’s still tiered: 15% on a developer’s first $1 million in annual Play revenue and 30% above that, with subscriptions at a flat 15%. As of June 30, 2026, Google began rolling out a different model in the US, UK, and European Economic Area that unbundles the old single rate into a 10% service fee plus a separate 5% billing fee on a developer’s first $1 million in earnings for developers who use Google Play’s own billing system, with lower combined rates if you use alternative billing or link out to the web; subscriptions are billed at that same 10%+5% rate. Starting September 30, 2026, developers enrolled in Google’s Apps Experience or Games Level Up programs qualify for reduced rates on top of that structure — 15% (down from the standard 20%) on transactions from new installs and 20% (down from 25%) on transactions from existing installs, with subscriptions unaffected at 10%. Google has said it plans to extend this overall structure to more markets, including Australia, Japan, and Korea, through 2027. Because the exact rate now depends on your region, revenue, program enrollment, and payment method, check Google Play Console’s Service Fees page for your specific situation rather than assuming one percentage.

Does Google Play Have an Annual Fee?

No. Unlike Apple’s $99/year membership, Google Play’s $25 developer fee is charged exactly once — there’s no yearly renewal, no subscription, and no recurring charge tied to keeping your account or apps live. Your Play Console account stays active indefinitely once the one-time fee is paid, even if you never publish another update.

Tips / Common Mistakes

Budget for both fees before you start, not after your build is finished — the $99/year and $25 one-time charges are trivial next to development cost, but they block you from submitting anything until paid, and Apple’s yearly renewal is easy to forget and let lapse right before launch.

If you’re a new individual Google Play developer, line up your 12 testers early. Recruiting people willing to install a test build and actually use it for two straight weeks takes longer than most teams expect, and it directly delays your launch date.

Don’t assume Apple and Google charge the same commission, and don’t assume you automatically qualify for a reduced rate on either platform — check the current thresholds and, on Google Play, your region, program enrollment, and billing method, since the rate isn’t applied by default just because you’re a small developer. Factor in review time on both sides when you set a launch date.

app store and google play publishing costs FAQs

What is the official Apple Developer Program fee?

$99 per year, per developer.apple.com/programs. It’s an auto-renewing annual membership required to publish on the App Store, plus a separate $299/year Enterprise Program for internal-only company distribution.

What is the official Google Play Console registration fee?

$25, paid once when you create your Play Console account. There’s no renewal and no per-app charge — one account covers unlimited apps for life.

Is there a Google Play annual fee?

No. Google Play’s only account charge is the one-time $25 registration fee. Apple, by contrast, does charge an annual $99 membership fee.

How much does it cost to publish an app on Android?

For a free app, just the $25 one-time Google Play Console fee. New individual developers also need to complete a 12-tester, 14-day closed test before production access, and any paid sales incur Google’s commission.

How much does it cost to publish an app on the Apple App Store?

For a free app, just the $99/year Apple Developer Program fee. Any paid downloads, in-app purchases, or subscriptions also incur Apple’s commission on top of the membership.

Do I have to pay Apple or Google every time I update my app?

No. Updates are free once your account is active — Apple’s $99/year and Google’s one-time $25 cover unlimited app updates, not per-release charges.

What percentage does Apple or Google take from app sales?

Apple takes 30%, or 15% if you qualify for the Small Business Program or after a subscription’s first year. Google takes 15% on the first $1 million in annual revenue and 30% above that in most markets, with a 10%+5% service/billing split now rolling out in the US, UK, and EU, and further reduced 15%/20% tiers for qualifying Apps Experience or Games Level Up program developers starting September 30, 2026.

Can I skip Google Play’s 12-tester testing requirement?

Only if your account is an organization account or a personal account created before November 2023 — those are exempt. New individual accounts must complete the 12-tester, 14-day closed test before requesting production access.

Build It With GTStudios

Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.

The post Apple & Google Play Fees: Official Costs to Publish an App appeared first on GTStudios.