What an app handover actually transfers

An app handover at Fluids is not a zip of the repo on the last Friday. Ship, on the homepage, is launch, handover documentation, and credentials that belong to you. Nothing is held hostage. That line is an inventory, not a slogan.

Frame, build, ship is the same engagement as the rest of the studio. Weekly builds already arrive on your TestFlight, your Play internal track, or your URL. Ship confirms the product is live — and that the accounts were yours the whole time.

Ship is not a zip of the repo

Software handover is control, not files. A zip without history is not a repo. A listing on someone else’s Apple ID is not your listing. A Supabase project on the studio’s card is not yours. Delivered is not handed over.

• You can invite us. You can revoke us. You do not ask us for a password.
• The store seller name is your legal name, not ours.
• Billing for Apple, Play, Supabase, and the domain sits on your accounts.
• A competent engineer who did not build it can clone, run, and ship an update from the docs.

What actually transfers

• Apple Developer Program and App Store Connect — your organization. Account Holder is yours. We are invited to upload. We do not own the listing.
• Play Console — your Organization account. We upload the AAB.
• Store listings — metadata, screenshots, privacy labels on your consoles.
• Supabase project — your org, you are Owner, billing on your card. The secret key is not in the IPA, the AAB, or the React bundle.
• Domains and DNS — you are the registrant. We use them. We do not keep the registrar login.
• Repo — your GitHub or GitLab org, full history, a tag that matches the store build. Not a zip.
• Keys — upload key and signing materials in a store you control. Play App Signing: you hold the upload key; Play holds the app-signing key.
• Docs — enough to run Flutter or Swift, the React admin, and Supabase without us.

You know it is yours when you can invite or revoke Fluids without asking us for a password.

Apple and Play sit on the client’s account

The plan is not an app transfer at the end. The plan is enroll your organization before week twelve. We upload. The two store checklists already say this. An organization listing needs a legal entity and a D-U-N-S number. The seller name is the legal name. Healthcare-class products should not sit on a personal name. Apple says as much.

App transfer between Apple accounts exists for when the app was sold, or opened on the wrong account. Play can transfer ownership, or transfer the app to a new account. Those are the cost of doing it on the wrong account. They are not the process.

One Supabase project, their org

You are Owner. Fluids is not the billing entity. Only Owner updates org settings and transfers a project out. That is why Owner has to be you. The backend note is the schema. This note is who holds the project.

The repo is your org, history intact. GitHub can transfer a repository. The point is not to need it. Domain registrant is you from day one.

Handover documentation

Software documentation handover is the package that lets someone else run it. A README: what the repos are, exact tool versions, how to run locally, how to build the IPA or AAB and the admin. An env inventory: names of variables, which environment, where they live — not the values in git. A service inventory: each third party, owner email, billing, what it does. How to submit the next store build. How the two clients share one Supabase project. Known limits of the accepted build. Honest. No fake zero debt.

What we do not keep

• Account Holder on Apple. Play owner.
• Supabase Owner. Domain registrant. Repo org.
• Production secrets and upload keys.
• The seller name on the listing.

We may stay an invited collaborator if you still want build work. That is access you grant. It is not a hostage. We do not invent a retainer. We do not invent a support window. Reviews stay Apple’s and Google’s.

This work is not the last Friday. Accounts before week twelve. Weekly increments already on your devices. Ship confirms launch, docs, and that the credentials were yours. The 20-day offer already puts handover in the in-list, and holding the repo in the out-list. Write to us with the product. Not with a fear of lock-in we then have to disprove.