At the end of an app development project you should receive the full source code, access to every account the app depends on, build and release instructions, documentation, and a written sign-off. Collect these before final payment, and check each item against your contract.
Handover is where many projects quietly go wrong. The app works, the launch is done, and only later does the owner discover they cannot rebuild it, cannot log in to a key service, or do not know how it was set up. This checklist helps you ask for the right things while the team is still engaged. It is general information, not legal advice; your written agreement decides what you are owed.
1. Source code and build files
- The complete source code for the app and for any backend or admin panel built for you.
- Build configuration, dependency lists and version numbers, so another developer can compile the app.
- Design source files and assets: icons, splash screens, fonts and images, with their licences.
- Written confirmation of what you own and what is third-party or open-source code. See who owns the source code when you hire an app developer.
2. Accounts and access
Every account that the app or store depends on should be registered to you, not to the developer.
| Item | What to confirm |
|---|---|
| Apple Developer and Google Play accounts | You are the account holder, and the app is published under your name |
| Hosting, domain and DNS | You control the logins and billing |
| Push notification and analytics services | Projects and keys belong to your accounts |
| Payment gateway and API keys | Keys are yours and stored securely |
| Code repository | The repository is in your organisation, or a full copy is delivered |
3. Signing keys and release instructions
- The app signing keys and keystore files, and where they are stored. Losing them can block future updates.
- Step-by-step instructions to build, sign and submit a new release.
- A list of environment settings and configuration values the app needs to run.
4. Documentation
- A short technical overview: how the app, backend and third-party services connect.
- Admin guides for the people who will run the store day to day.
- A list of integrations, plugins and custom features, including anything that needs periodic renewal.
5. Testing and acceptance
- The test checklist used, and the result of each item. See our buyer acceptance checklist for testing an app before launch.
- A list of known issues that were accepted or postponed, in writing.
- A signed acceptance note that states what was delivered.
6. Support and maintenance terms
- What support is included after handover, for how long and through which channel.
- How bugs are handled compared with new feature requests.
- Who will handle updates for new phone operating system versions. Our app maintenance checklist shows what ongoing care involves.
7. A simple handover process
- Agree the handover list in your contract or project brief, before work starts.
- Ask for a draft handover pack one to two weeks before launch, so gaps are found early.
- Check access yourself: log in to each account and confirm you are the owner.
- Ask a second developer, if possible, to confirm the code builds from the files supplied.
- Release final payment only after the pack is complete and accepted in writing.
Common handover problems
- Accounts registered under the developer's email.
- Signing keys held only on one person's computer.
- Code delivered without the build files needed to compile it.
- Documentation promised but never written.
Next steps
Put the handover list into your brief from day one; our guide to writing a project brief for a software quote shows where it fits. To see how we plan and deliver this kind of work, read about our Flutter ecommerce app development service, or request a quote.
Frequently asked questions
What should you receive at the end of an app development project?
You should receive the full source code and build files, ownership of every account (Apple, Google, hosting, domain, keys), signing keys, release instructions, documentation, and a written acceptance note. Check each item against your contract and confirm access yourself before releasing final payment.