# Client App Store Onboarding

ClientOS Studio's default for production mobile apps is simple:

**The client owns the Apple Developer and Google Play Console accounts. ClientOS Studio operates inside those accounts by invitation.**

## Why This Is The Default

- The app launches under the client's business name and legal identity.
- Store payments, tax profiles, legal agreements, app reviews, ratings, and long-term account control stay with the client.
- ClientOS Studio can still handle the technical release work without becoming the publisher of record.
- Future transfers, ownership disputes, and launch delays are easier to avoid when the app starts in the correct account.

## Client Responsibilities

- Create or maintain an Apple Developer Program account for the business.
- Create or maintain a Google Play Console developer account for the business.
- Keep the owner, account holder, payment, tax, and legal agreement roles internal to the client.
- Invite ClientOS Studio with the minimum access needed for development, submission, testing, and release management.
- Approve any store-facing legal, pricing, subscription, privacy, or policy decisions.

## ClientOS Studio Responsibilities

- Configure bundle IDs, app identifiers, signing, builds, and release tracks.
- Prepare store metadata, screenshots, review notes, privacy answers, and testing instructions.
- Submit builds for review and coordinate fixes if Apple or Google asks for changes.
- Maintain release notes, update cadence, and post-launch store improvements.
- Document the app's store setup so the client is never dependent on a single person.

## Exceptions

ClientOS Studio may publish under a studio-owned account only for prototypes, demos, temporary review builds, or a written managed-publishing arrangement.

Any exception should include:

- Why client-owned publishing is not practical yet.
- Who owns the app, data, brand, and store listing.
- When and how the app will be transferred or migrated.
- Who handles fees, support requests, policy notices, and account risk.

## Launch Checklist

- Apple Developer account active.
- Google Play Console account active.
- Business legal name and address confirmed.
- D-U-N-S or organization verification handled if Apple requires it.
- Store payment and tax profiles completed if the app charges users.
- Privacy policy URL ready.
- Support URL ready.
- App icon, screenshots, descriptions, keywords, and category approved.
- ClientOS Studio invited to the right teams.
- Production domains, backend APIs, and support email verified.
- Final submission approval received from the client.