APP Development Handover: Code, Accounts, and Docs

The project demo passes and the installation package downloads successfully. Yet at handover, the company discovers that the code repository is under a personal account, the iOS certificate is about to expire, SMS and map services use vendor accounts, and only one person knows the server password. The product may appear to have launched, but the company has not gained the ability to operate it continuously.

APP handover should be organized around five goals: ownership, buildability, publishability, maintainability, and portability. The deliverable is not a compressed file, but a set of product assets that a new team can take over.

01 Code Repository: The Client Needs More Than the Final Source Code

The client organization should ideally create the Git repository and invite the vendor to collaborate. If a vendor repository was used earlier, the complete history, branches, tags, and release records should be migrated at handover. Sending only a final compressed file loses the reasons for changes, rollback points, and collaboration history.

The repository should contain a clear directory structure, dependency lockfiles, sample environment variables, and a README. Real secrets must not be committed to the code, but the required configuration and application process for each environment should be documented.

02 The Company Must Control Signing Certificates and App-Store Accounts

iOS certificates, provisioning profiles, App Store Connect, Android signing keys, Google Play Console, and domestic app-market accounts directly determine whether the same application can be updated later. They should not remain exclusively under an individual developer’s or outsourcing company’s control over the long term.

At handover, confirm the account owner, highest-level administrators, two-factor authentication, recovery email, key backups, and expiration dates. Signing materials should be kept in a secure password manager or controlled storage, not retained indefinitely in WeChat groups.

□ Organization owner and administrators for Apple Developer and App Store Connect;

□ Android signing key, alias, password, and secure backup location;

□ Legal entity, package name, Bundle ID, and listing history for each app marketplace;

□ Push certificates, associated domains, universal links, and deep-link configuration;

□ Expiration reminders and renewal responsibilities for certificates, keys, and services.

03 Map Back-End, Database, and Cloud Assets

An APP often depends on APIs, databases, object storage, a CDN, message queues, scheduled jobs, and log monitoring. Delivering only the client source code still leaves the product unable to operate independently. Use an architecture diagram to identify every resource, its account, environment, owner, and backup method.

Production database handover requires particular care. Do not casually download all user data to a personal computer. Complete the transfer through controlled permission changes, backup verification, and auditing. Separate test and production accounts, keys, and data.

04 Third-Party Services Are Hidden Handover Dependencies

SMS, email, maps, payments, identity verification, customer support, analytics, push notifications, OCR, and content moderation may all rely on third-party platforms. Confirm the entity under which each is registered, how it is billed, whether its balance is sufficient, and where callback URLs and keys are stored.

If a shared vendor account is used, the contract should define a migration plan and transition period after the engagement ends. Services that cannot be migrated should be replaced in advance, or the product may suddenly lose critical capabilities after handover.

05 Deliver Design Files and Product Rules as Well

Development source code does not replace Figma files, icons, exported graphics, the design system, or interaction documentation. Future releases often begin with design. Without complete source files, the new team can only reconstruct the interface from screenshots of the installed APP.

Product rules are equally important. If discount calculations, order states, permissions, reviews, notifications, and exception handling exist only in a product manager’s chat history, the code may run but the team will struggle to modify it safely. Deliver the PRD, state diagrams, API documentation, and records of key decisions.

06 Have the New Team Complete an Independent Build and Release Drill

The most effective handover acceptance method is for the client or a third party to clone the code into a clean environment, configure a test environment, build an installation package, change a minor version number, and publish it to a testing track. Any step that requires temporary “manual handling” by the original developer should be added to the documentation.

The drill should also cover rollback, database backup and recovery, certificate-expiration checks, and alert delivery. Completing it demonstrates that handover has progressed from files to operational capability.

1. Freeze the handover release and generate a changelog;

2. Transfer highest-level permissions for accounts, repositories, and cloud resources;

3. Replace temporary passwords and keys controlled by the vendor;

4. Have the new team independently build a test release from the documentation;

5. Verify monitoring, backups, and incident contacts;

6. Have both parties sign the handover checklist and document unresolved issues.

07 Do Not Put Every Password in One Word Document

Handover documents may state each credential’s name, purpose, and storage location. Actual passwords, private keys, and recovery codes should be stored in a company-controlled password manager or key service and assigned under least-privilege principles. Revoke vendor accounts that are no longer needed after handover.

Also retain an emergency recovery process explaining how the company can recover app-store, cloud-platform, and domain access if the only administrator leaves, loses a phone, or cannot complete two-factor authentication.

Frequently Asked Questions

Does copyright automatically transfer to the client when APP source code is delivered?

No. Delivery of source-code files and copyright ownership are separate matters. They must follow the contract and distinguish custom code, open-source components, and third-party SDKs.

What happens if a signing key is lost?

It may affect future updates and releases of the Android application. The company should maintain a secure backup and document the key, alias, password, and recovery method.

Can a vendor manage app-store accounts on the company’s behalf?

The vendor can assist with operations, but the company should own the legal entity and highest-level permissions so it does not lose publishing capability when the engagement ends.

How long does handover take?

It depends on system scale and how widely assets are distributed. A simple project may take several days, while a complex product should be inventoried several weeks in advance with build, release, and recovery drills scheduled.

Can development continue with only the installation package?

Usually not. An installation package is not maintainable source code and does not include the back end, configuration, signing materials, or documentation.