Building for clients: whose Apple and Google accounts should publish

Whose Apple and Google accounts should publish a client’s app?

Apple wants the client to enroll, be the seller and submit the app. Here is how agencies should set up Apple and Google accounts for client apps.

Tomas·5 min read
0.0.6the App Review rule most agencies miss
$0a year for the Apple Developer Program
0testers for 14 days on a personal Play account

Publish a client's app under the client's own developer accounts, not yours. Apple says so directly: the client organization enrolls, appears as the seller, and submits the app, while you help as a team member. Google Play's registration pages don't state an equivalent rule, but the same setup saves you a transfer, a support problem and an ownership argument later.

The question usually comes up after the app is already built. It is cheaper to settle it before the first build.

What Apple actually requires

As of November 2026, Apple's enrollment guidance is clear about apps built for someone else. The client organization should enroll in the Apple Developer Program and add the developer to its team. The client's name shows as the seller on the App Store, and "the organization must be the one to submit the app."

Enrolling as an organization has requirements that take time, so start early:

The client must be a legal entity. Apple doesn't accept trade names, DBAs or branches.
The client needs a D-U-N-S Number, which is free in most places.
The person enrolling must have legal authority to bind the company.

The fee is $99 a year (Apple Developer Program), and it belongs on the client's card, so the client owns the renewal.

For apps that are only for the client's staff, Apple points to Custom App Distribution through Apple Business Manager rather than a public listing.

The rule most agencies miss: 4.2.6

App Review Guideline 4.2.6 is the reason this isn't just an etiquette question. Apps created from a commercial template or an "app generation service" are rejected unless the content provider submits them, and such services shouldn't submit on behalf of clients (App Review Guidelines, last updated October 16, 2026).

If you build client apps with any AI builder, including ours, assume a reviewer may read your app as generated. The defence is the setup Apple already asks for: the business that owns the content submits from its own account.

The same page also has 4.2, Minimum Functionality: an app needs features and content beyond a repackaged website. A thin wrapper around a menu page can fail on 4.2 before 4.2.6 even comes up.

Google Play: one fee, one test period

Google is simpler on ownership and stricter on process. As of November 2026:

Registration is a one-time $25 fee. Prepaid cards aren't accepted, and identity checks can ask for a government ID.
Personal accounts created after November 13, 2023 must run a closed test with at least 12 testers for 14 consecutive days before they get production access.

That second rule matters for small clients. A sole trader who registers a personal account can't launch the week the app is ready. Either plan two weeks of testing with real customers or staff, or register the client as an organization where that's possible.

If you already published under your own account

It happens. A café asked for a loyalty app, you used the agency account to move fast, and now the client wants it back.

Apple supports app transfer: your Account Holder starts it, the client's Account Holder accepts. The app keeps its reviews, ratings and Bundle ID, and users keep receiving updates. Before you start, turn off TestFlight. Apple Pay merchant IDs and push notification certificates don't move with the app, so anything that depends on them needs to be set up again on the client's side.

A transfer works, but it is a migration with a checklist. Doing it right the first time is one enrollment.

How this works with Leanfinit today

During the beta, Leanfinit does not submit apps to the App Store or Google Play. The Publish button puts an app live on the web, which is often enough to show a client a working version and collect feedback. More on that in What happens when you press Publish.

When a client needs a store listing, the path is the one Apple describes:

1Export the code. Generated apps are built on Flutter, so one codebase covers iOS and Android.
2The client enrolls with Apple and registers with Google Play, and adds you to both teams.
3You build, sign and prepare the release under the client's accounts.
4The client's account submits.

This keeps the client as owner of the listing, the reviews and the customer relationship. It also keeps you clear of 4.2.6, because the content owner is the one submitting.

A setup checklist for the first client meeting

Put these on the kickoff agenda, before design or prompts:

Legal entity and D-U-N-S Number for the client, or a decision to publish on the web only.
Who pays the $99 renewal every year, and who gets the reminder.
Who is Account Holder on the Apple side (the client) and which role you get.
Organization or personal Play account, and if personal, who the 12 testers are.
Who owns the code export and where it is stored after handover.
Who answers store reviews and support emails once the app is live.

The last two are where agency relationships usually go wrong, and they have little to do with stores. We cover the delivery side in Delivering client apps with an AI builder.

What I'd tell a freelancer starting out

Don't treat the store account as a favour you do for the client. It is the client's asset, like their domain name or their bank account. You can manage it, but they should own it.

If you are unsure whether a client even needs a developer account, our insight on whether you need an Apple developer account to use your own app covers the cases where a web app is enough.

You can build the first version for a client in the studio: studio.leanfinit.com.