Buyer guide
What should I collect when my developer leaves or hands over the app?
In short
Collect five things before the old developer is gone: the source code and its history, ownership of the store accounts, access to servers and the domain, every key and third-party login, and written notes on how to build and release. Then ask the new developer to build and release from scratch as a test.
Who is this guide for?
Owners who are changing developer, or whose developer is leaving, and want to be sure they can run and change their app afterwards without the previous person.
Why a handover goes wrong
Most handovers fail on small things that only one person knew: where the server is, which account holds the domain, how a release is made. The code alone does not tell you these.
The official guidance on legacy technology lists poor documentation among the risks that waste time and money when others try to work out how a system runs. A handover is the moment to write that down.
The source code and its history
Ask for the full repository, including its history, not a zipped copy of the latest files. The history shows why changes were made and lets a new developer go back if something breaks.
Put the repository in an account you own and add the developer as a member. Then the code stays with you whoever works on it.
Store accounts and app ownership
If the app is published on Apple's App Store or Google Play, find out which developer account holds it. Both stores can move an app between accounts, but each has conditions. Google Play says both accounts must be active and in good standing, and that some things, such as earnings reports and test groups, do not move across.
Apple's app transfer is started by the Account Holder and accepted by the receiving Account Holder, and Apple advises backing up the app information first because the app is removed from the original account. Features such as push notification certificates and Apple Pay merchant identifiers need extra steps.
Servers, domain, keys and third-party services
List every service the app depends on: hosting, the domain name, email sending, payments, analytics, push notifications, maps and any AI or other API. For each, note who holds the account, who pays the bill and how to get in.
Keys and passwords should be moved into a password manager you control. Once the new developer has access, rotate the secrets the old developer knew.
Documentation and a test run
Ask for short written notes: how to run the app locally, how to build it, how to release it, how backups work and what recurring jobs exist. Rough notes are better than none.
Then run the real test. Ask the new developer to build the app from the repository on a clean machine and publish a small change to a test environment. Anything that fails shows what the notes missed while the old developer can still answer.
How do the options compare?
| Item | Who should own it | How to check |
|---|---|---|
| Source repository | You, as the organisation owner | You can clone it with your own login |
| Apple and Google developer accounts | Your company | You can log in and see the app listed |
| Domain name | You | The registrar account is in your name and email |
| Hosting and cloud accounts | You | The bill comes to you and you can add users |
| Keys and third-party logins | You, in a password manager | Each service lists you as the owner |
What should I check before I sign?
- The full repository with history is in an account you own.
- You know which developer account holds each app in the stores.
- The domain registrar account is in your name.
- Hosting, email, payment and analytics accounts list you as owner.
- Keys and passwords are in a password manager you control.
- The old developer's access is removed and shared secrets are rotated.
- Written notes explain how to run, build, release and restore backups.
- A new developer has built and released the app from scratch as a test.
- The contract states who owns the code and the accounts.
How pricing works
I quote in writing after a short discovery call, against a written scope. Building an app from scratch? The app cost calculator gives a first range in two minutes.
What else do people ask?
What if the old developer will not cooperate?
Start with what you can reach: the store accounts, the domain and the hosting bill show who holds what. Read your contract for handover and ownership terms, and have a lawyer in your country advise if access is refused.
Can an app move to a new store account without losing its reviews?
Both Apple and Google describe transfers that keep the listing, ratings and reviews, subject to their conditions. Read the current steps before you start.
How long should a handover take?
It depends on the app. Plan for time for the new developer to ask questions, and do the build-from-scratch test before the old developer's access ends.
Should I pay for the handover?
Agree it in the contract in advance, so the final payment is tied to the items on your checklist.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
How can we work this way together?
- Mobile App Care PlanIn the app care plan I look after your live mobile app month by month: I watch crashes, fix what breaks, keep it working with new phone and store changes, and ship small updates in two-week sprints.
- Store Release ManagementIn store release management I handle your Google Play and App Store releases month by month: I build, sign, test and submit each update, deal with store review feedback and keep a way back if a release misbehaves.