Start an app handover by confirming that your business controls the store listings, source code, and systems that keep the app running. Then have the incoming team reproduce a build and check its ability to release an update. Those checks tell you whether the team can maintain the app before you agree to feature work.
Confirm who controls the store accounts
Your business should control its Apple Developer and Google Play Console accounts. Add developers as individual team members with the permissions they need. Check who receives renewal notices, policy messages, and release approvals. If the app is listed under a contractor's account, establish whether it can be transferred through the store and who needs to initiate the transfer.
Record each listing, the last published version, and any pending warnings. An incoming iOS development team or Android development team should be able to match that information to the code it receives.
Collect the code and prove it builds
- Get access to the repositories, all branches and tags, and any related backend projects.
- Ask which commit matches the current store release and which changes are still in progress.
- Collect setup and build instructions, required tool versions, and a list of environment settings for test and production. Share secret values through a controlled channel.
- Include the automated build and release setup, test accounts, and a short list of workflows the incoming team should verify.
For a React Native app, collect both platform projects alongside the shared code. Platform-specific dependencies or settings can affect whether the iOS and Android versions build.
Check app signing and release access
For iOS, identify the Apple team responsible for the app and confirm access to manage signing certificates and provisioning profiles. Ask the new team to check the signing setup before revoking certificates that may still be in use.
If Android uses Play App Signing, Google manages the signing key used for distribution, while your team uses an upload key to sign the file sent to Google Play. Find out who controls that upload key and use Google Play's reset process if needed. For an older app, have the team verify its signing arrangement first.
Map hosting and third-party services
List the servers, databases, scheduled jobs, backups, and admin panels. Identify who pays each bill, where the domain and DNS are managed, and who handles SSL renewal. Give the incoming team enough access to review the setup and agree on how to verify that a backup can be restored. A backend development team can review these dependencies alongside the mobile apps.
Make a separate list for push notifications, analytics, payments, maps, email or SMS, and crash reporting. For each service, record the account owner and the app feature it supports. After the handover, rotate credentials held by the outgoing team in a planned order. Test the features that depend on each replacement before retiring the old credential and removing former access.
Document open issues and agree on the first milestone
Collect known bugs, pending store warnings, and unfinished work with enough detail to reproduce or locate each issue. Check your agreement for ownership of the code and other intellectual property, including designs and licensed assets. This is general handover guidance. Ask a qualified adviser about disputed or unclear rights.
Have the new team confirm the app builds, check which accounts it can access, and identify release or operational risks. Agree on what to fix first and who approves the work. Use a maintenance plan to assign the tasks that continue after the takeover.
Worked example: a booking app after a freelancer leaves
- Collect access
- The owner confirms control of both store listings, then gathers the mobile repository, booking server account, DNS access, and the account that sends confirmations.
- Verify the handover
- The incoming developer matches the last release to a commit, builds both apps, and uses a test account to book and cancel an appointment. The team checks whether staff can still manage availability.
- Agree on the first milestone
- A store warning has a deadline and a cosmetic issue can wait. The team prioritises the update and tests booking confirmations before replacing the old service credentials.