Agree rights and operational access separately

The project agreement should state the rights granted or transferred in code, designs and other assets, including any third-party licences or reusable components. Repository access alone does not decide those rights. This guide is an operational checklist; legal ownership terms need to be agreed in your contract.

Also identify the people and accounts that can operate the product. Your business may have rights to the work but still need access to the store, cloud account, database or signing arrangement to release an update. Resolve both questions before treating handover as complete.

Inventory the assets behind the app

AssetEvidence to request
Android source and designsRepository, agreed release tag, design files, dependency details and relevant licence information.
Build and releaseInstructions an authorised maintainer can follow, environment requirements and the agreed signing/release process.
Google PlayApp record, account roles, current release status and responsibility for future submissions.
Backend and databaseSource or service configuration, environments, data model, migrations and deployment instructions.
Operational servicesCloud, domain, email, notifications, payments and integration accounts, with ownership and billing recorded.
ContinuityMonitoring contacts, known issues, support terms and backup/restore procedures where included in scope.

Decide who controls the Google Play account early

Agree the intended publisher and the access each person needs before launch. Google Play has account setup and role requirements; use its current documentation rather than assuming that handing over an APK transfers a store listing or a developer account.

In the operating model you agree, the business should know who can submit releases, manage permissions, recover access and pay applicable bills. Use named access where the platform supports it rather than passing around one shared password. An account change may involve platform procedures as well as your agreement with the supplier.

Demonstrate that the handover works

Have an authorised maintainer follow the build instructions in the agreed environment and identify the release it produces. Check how the app connects to the correct test or production backend, and confirm who is allowed to release it. This is stronger evidence than a folder that has only been opened on the original developer's computer.

Where backups are part of scope, ask for evidence of a restore procedure rather than the presence of a backup file alone. Where external services are involved, check that their billing and alert contacts will still be reachable after the project team changes.

Why an integrated app needs more than mobile source

Pulse works with WhatsApp API conversations, contacts and tags. That published product behaviour illustrates why an integration-dependent app has operational responsibilities beyond its Android interface. For your own project, identify the service accounts, access rules and documentation needed to keep the agreed integration functioning.

Keep the inventory specific to your own project and match it to the system in your backend and admin-panel scope.

A handover check you can observe

Illustrative acceptance check for an inspection app

Ask the incoming maintainer to build the agreed release, connect it to a test environment and install it on a test phone. A technician signs in, records an inspection and submits it. A coordinator then finds that record in the staff panel. The maintainer explains where a failed submission would be investigated and who has access to the relevant service.

Record the release tested, the environment used, the person who demonstrated it and any missing access. If the build works but the staff panel cannot be deployed, assign that outstanding step and agree when it will be demonstrated. Test with suitable sample records and keep production access subject to the agreed release process.

Record what remains open

Keep known bugs, deferred features and incomplete documentation in an agreed list with an owner and next action. Separate acceptance of the current release from approval of future work. Confirm the maintenance start, responsibilities and exclusions in writing.

Transfer secrets through an agreed secure channel. Review a departing supplier's access after the incoming owner has verified continuity. Plan this process during proposal comparison, when both parties can still agree what good delivery means.

Free to use and share

Your copyable worksheet

Download the plain-text version or select and copy it below. No account or email address is required. Keep passwords, API keys and real customer records out of a project brief.

Download the worksheet (.txt)

Read and copy the full worksheet
ANDROID APP HANDOVER CHECKLIST
Prepared with bbigcheese · https://bbigcheese.com
Agree the deliverables and rights in the project contract. This is an operational
checklist, not a transfer of rights or a substitute for legal advice.

For each item, record owner / access held / evidence checked / unresolved work.
[ ] Source repositories, release tag and agreed reuse/licensing rights
[ ] Design source files and licensed fonts, images and other assets
[ ] Build instructions, tool versions and dependency details
[ ] An authorised maintainer can build the agreed release from the instructions
[ ] Google Play account roles, app record and release responsibilities
[ ] Signing arrangement, upload access and recovery responsibility documented
[ ] Backend source/configuration, environments and deployment instructions
[ ] Cloud/database/storage accounts and billing ownership documented
[ ] Data model, migrations, retention and deletion procedures documented
[ ] Backup and restore procedure tested where backups are part of scope
[ ] Domains, email, notification, payment and other external accounts inventoried
[ ] Secrets transferred through an agreed secure channel, not a public document
[ ] Monitoring, alerts and support contacts assigned
[ ] Acceptance tests completed and known issues recorded
[ ] Support/maintenance terms, exclusions and change process agreed
[ ] Departing supplier's access reviewed after continuity is confirmed

Questions and answers

Does paying for development automatically settle source-code ownership?

Do not assume so. The written agreement should state rights in the deliverables, reusable components and third-party materials. Access to a repository is an operational matter and does not replace those terms.

Is an APK enough for an app handover?

An installable app is useful for testing but does not by itself give a maintainer the source, build instructions, release access or backend information needed to make and operate future updates.

When should handover be discussed?

During scoping and proposal comparison. Agree the expected assets, account responsibilities, demonstrations and outstanding-work process before delivery.

Our own published apps

The product examples refer to apps we build and run ourselves. Their pages link to the published listings and explain the relevant scope.

Primary sources

Check the platform’s current requirements before planning a release or account change.