Both stores ask the same question when you sign up, and neither explains it well: are you an individual or an organization? It looks like a formality. It decides whose name appears on your app, who else can work on it, whether you need a business identifier that takes weeks to obtain, and — for some app categories — whether you are allowed to publish at all.
The good news, and the part most guides get wrong: you can change your mind later on both stores. The bad news is that the two stores handle that change completely differently, and the advice you will find for Apple usually costs more than it needs to.
Start here, because it saves the rest of the decision. Google states that an organization account must be used for:
VpnService classIf your app is in one of those categories, you need an organization account on Google Play and the rest of this page is just background. Nobody leads with this, and it is the single fastest way to resolve the question.
Costs are identical. Everything else is about identity, access and eligibility.
Two of those points carry most of the real risk, and both surprise people.
An Apple individual membership publishes under the person's own legal name. Not a username, not a trading name — the name on your ID, visible on the App Store listing to anyone who looks. Plenty of solo developers are fine with that. Plenty of others assumed they could pick something else, and discovered otherwise after launch.
It is not something you can quietly undo either. Changing it means changing the account type, which brings us to the section below.
An individual Apple membership has no team. You cannot invite a developer, an agency or a colleague — access means handing over your Apple ID, which you should not do. So "I'll just use my personal account for now" quietly blocks bringing anyone else in later.
Google documents no equivalent restriction on personal accounts, which is worth knowing if you are setting up both stores at once and expecting them to behave the same way. They do not.
This is the most common edge case and the stores are quieter about it than they should be. Being registered as a business does not automatically make you an organization in Apple's sense.
Apple's enrolment guidance requires an organization to be recognised as a legal entity — a corporation, a limited partnership, a limited liability company. A sole proprietorship or a trading name usually is not a separate legal entity from the person, so it does not qualify, whatever your local business register says.
There is a hard confirmation of this in the fee-waiver rules: Apple's waiver excludes anyone who is an individual, sole proprietor or single-person business. Being registered as a sole trader gets you nothing extra here.
So if you are a freelancer or a one-person business without an incorporated entity, you are an individual on both stores — and if you want the organization treatment, the change you need is a company, not an account setting. Worth knowing before you spend a week chasing a D-U-N-S number for an entity that will not qualify.
This is where the internet's advice is expensive, and the two stores diverge completely.
Apple's own documentation is direct about it: to update a membership from an individual to an organization you submit a request. You need to be the founder or cofounder of the organization, and you provide details such as your organization's D-U-N-S number. Apple may also ask for business documents to verify the organization's identity.
What that means practically: you do not need to open a second membership and move your apps across. A great deal of advice online tells you to do exactly that — create a fresh organization account, then transfer each app individually. That path means paying for a second membership and doing the transfers by hand, for an outcome the conversion request gives you without either.
One correction worth making, since several guides state otherwise: Apple's documentation says founder or cofounder. It does not say "a senior employee" or "anyone with signing authority". If you are not a founder, expect to involve one.
Google's position is that you cannot update country, account type, or D-U-N-S number on an existing payments profile. To change any of them you create a new payments profile, provide the required information, verify your details, and then link the verified profile to your developer account.
So "can I switch?" and "is it just a setting?" have different answers: yes, and no. It is a replacement, not an edit, and it is worth budgeting verification time for.
One question to ask Apple before you convert, if you have a live app and run paid acquisition.
Apple documents that changing your organization name updates the vendor name across all your apps, resets the
identifierForVendor(IDFV) for existing users on their next update, may cause a mobile measurement partner to count existing users as new installs, and cannot be undone.Apple does not say whether an individual-to-organization conversion triggers the same reset. It plausibly might, since the vendor name changes either way — but that is an inference, not Apple's statement, and we are not going to present it as one. If your attribution matters, put that exact question to Apple Developer Support before you submit the request. It costs one email and it is not a question you want answered by your dashboard.
A fair amount of what circulates about this is not in Apple's documentation, so treat it as reported rather than official. In particular, you will read that your Apple ID, Team ID, certificates and existing apps all carry over untouched and only the seller name changes. That may well be what happens — but Apple does not document it, so we are not going to tell you it is guaranteed.
What Apple does document is the process: a request, founder or cofounder, a D-U-N-S number, and possibly business documents. Everything beyond that is worth confirming with Apple Developer Support for your specific account, particularly if you have paid apps, subscriptions or live users.
Apple waives the $99 Developer Program fee entirely for nonprofits, accredited educational institutions and government entities — and that waiver is organization-only. You cannot be an individual, sole proprietor or single-person business and qualify.
So for a nonprofit, choosing individual is not a neutral choice: it is $99 every year, forever, for no reason. The full fee arithmetic for both stores is in what it actually costs to publish an app.
You will see it claimed flatly that organization accounts are exempt from Google Play's requirement for 12 testers over 14 days. Here is the accurate version.
Google scopes that requirement to personal accounts created after 13 November 2023, and its documentation does not mention organization accounts. So organizations are widely understood to fall outside it — but that is an inference from Google's scoping, not an explicit statement, and it is worth holding loosely rather than planning a launch date around it.
It is also not a free shortcut. An organization account needs a D-U-N-S number, and obtaining one can take up to 30 days — often longer than simply running the closed test. We covered the whole thing in the Google Play 12-tester rule, explained.
Whichever you choose, the account setup itself is covered step by step in creating an Apple Developer account and creating a Google Play developer account.
If you build with Choicely, your apps are published to the App Store and Google Play under your own developer accounts — so this choice stays yours, and using us does not change it. What we do remove is the part that actually delays launches: the build toolchain, the certificates and the SDK deadlines. The D-U-N-S wait is still Dun & Bradstreet's, not something anyone can shortcut.
If you would rather hand the publishing over entirely, that is our app publishing service.