Publishing a club app: your developer account or ours?

This decision gets made in a sentence during onboarding and then matters for years. It determines who owns your install base.

The two routes

Published under your own accounts

The club holds an Apple Developer account and a Google Play account. The app is listed under the club's name, the reviews are yours, the installs are yours, and if you change vendor the listing survives.

Costs are trivial — Apple charges annually, Google once. The work is a few hours of setup and identity verification.

Published under the vendor's account

Faster to launch and no admin for the club. But the listing, reviews and install base belong to the vendor. Leave, and you start from zero somewhere else, asking every supporter to download a new app.

The container app option

Some platforms offer a single app with a club picker inside it — one download, choose your club. Legitimate, and genuinely sensible for smaller clubs where a standalone listing would never gain traction.

The trade-off is that the app is not branded as yours in the store, and discovery works differently.

The rule that catches vendors out

Apple's guidelines prohibit submitting multiple near-identical apps from one account. A vendor who publishes forty club apps from their own developer account, each differing only by colours and a crest, is operating against those rules and risks removal — taking every client's app with it.

This has happened to sports app vendors before. If a platform tells you they will publish under their own account and they have dozens of clients, ask how they handle it, because Apple has been enforcing this more tightly.

What we do

Flagship clubs publish under their own accounts, so the listing is genuinely theirs and survives us. Smaller clubs go into a container app with club switching. Both are compliant, and we will not batch-submit near-identical apps from one account.

The full app picture is on matchday and team apps.

What each route actually requires from the club

The row that matters is the install base. Rebuilding one from zero means asking every supporter to download a new app, and realistically you recover perhaps half.

Setting up your own developer accounts

Less work than clubs expect. What you need:

• Apple — an organisation account, which requires a legal entity name, a D-U-N-S number and identity verification. Allow two weeks for the D-U-N-S if you do not have one.
• Google Play — a developer account with identity verification, considerably faster.
• Both should be registered to the club's entity and email, never to an individual's personal account.

That last point causes real problems. A club whose app is registered to a former committee member's Apple ID cannot update it, and recovering access is slow and sometimes impossible.

The Apple rule and why it matters to you

Apple's guidelines prohibit submitting multiple near-identical apps from a single account, which is exactly what a vendor publishing forty club apps from their own account is doing.

Enforcement has tightened, and when it happens it takes every client's app down at once, not just the newest. If a vendor tells you they publish under their own account and they have dozens of clients, ask directly how they handle this. A vendor who has thought about it will have an answer involving separate accounts or a container app. One who has not will be vague.

When the container app is the right answer

For smaller clubs it genuinely is. A standalone listing for a club with 400 supporters will never rank in store search, will accumulate few reviews, and carries the same maintenance burden as one with 40,000.

A container app with club switching gives those clubs a working product without the overhead, and supporters of multiple clubs only download once. The honest trade is store branding, which for a club that size is worth very little.

Read next