App takeover checklist: ask for evidence, not just files
Taking over a mobile app means establishing that an authorised team can understand it, produce an update and operate the connected system. A project archive alone cannot prove that. Use this checklist to connect each requested item with a practical verification step, an owner and a clear record of anything still missing.
Updated: · tealtap

Define the purpose and capture the current state
Routine maintenance, urgent repair and planned modernisation require different assessments. Identify the business objective, current production version, supported platforms and next necessary release. Walk through the core journey with test data, including error recovery. Mark known defects, accepted limitations and uncertain behaviour separately so the receiving team does not inherit assumptions as facts.
For each handover item, record the provider, verification method, status and next action. Received and tested are different states. Agree the assessment scope and access arrangements before touching live services. Keep proposed redesign work separate from the steps required to establish a dependable starting point.
Connect source code to the live release
Request the agreed client, backend and administration sources with dependency information. Identify the revision used for production and any files or changes held outside the repository. If the published package cannot be traced to a source state, record that uncertainty explicitly. Do not silently substitute a plausible looking folder for evidence.
Ask for a short code walkthrough covering configuration, API access, authentication and generated material. Review known issues and run the relevant existing checks. Have rights and licence questions reviewed separately: technical access does not establish the legal position. This article is general information, not legal advice; qualified counsel should assess contractual questions.
Build a package from the documented process
Instructions should identify tools, versions, dependency installation, commands and required configuration names. Keep secret values in an appropriate access controlled system. Make test and production settings distinguishable. Another authorised developer should be able to use the instructions without reconstructing the process from old chat messages.
Produce and install a test package in an agreed environment. Record its source revision, environment and verification result. The objective is an understood and repeatable process, not necessarily a byte identical copy of an old package. Also test updating an existing installation: retained data, login state and the main journey can behave differently from a clean installation.
Verify accounts and the operations each role can perform
Inventory store accounts, source hosting, infrastructure, domains, identity services, push services and external APIs. Record organisational control, billing contacts and required roles. Opening a dashboard is not sufficient proof of the ability to carry out an assigned release or recovery task. Use named invitations where appropriate and confirm the required permissions.
A developer change does not always require moving an app between store accounts. If a transfer is needed, follow current Apple and Google procedures and check eligibility. Google's guidance notes that integrated service permissions and linkage settings do not transfer automatically. Inventory those connections and test them after the change while preserving an understood continuity plan.
Handle signing and secrets deliberately
Record each credential's purpose, owner, secure storage location and recovery route without copying its value into the checklist. Cover build automation, signing and service access. Grant access through suitable roles or a dedicated secret management process rather than attaching a password list to an ordinary message.
Do not rotate or copy signing material indiscriminately. First understand its dependencies, platform arrangements and effect on future releases. Plan verification and recovery before making a change. After transition, review old access and remove what is no longer justified, coordinating this with evidence that the new operating route works. Avoid leaving continuity dependent on one person's private mailbox.
Include backend operation and recovery
Request a system map, deployment instructions, API documentation, data model and configuration inventory. Identify which services enforce permissions and business rules and which run scheduled jobs. A server address alone is not an operating manual. Confirm test environments and keep production records out of ordinary development archives.
Verify backup recovery in an isolated environment and inspect monitoring, alert recipients and incident handling. Record supplier limits, billing and support contacts. Consider compatibility with older installed clients during a transition. Separate necessary takeover repairs from optional modernisation so the initial assessment does not quietly become a complete rewrite.
Close each item with usable evidence
Collect business rules, release instructions, known issues, operating procedures and editable assets where included. Compare privacy documents and store declarations with actual behaviour. Identify who maintains content, supports users and approves releases after the supplier change. Walk through documentation with the receiving team and correct instructions that do not match the system.
At closure, list accepted gaps with their consequences, owners and next decisions. Assign responsibility for watching the first release and handling reports. tealtap takes over native Swift and Kotlin apps, Flutter, React Native and PWA applications. The checklist prepares the code assessment that informs the repair plan.
| Item | Practical evidence |
|---|---|
| Source | Revision linked to the production release |
| Build | Documented test package produced and installed |
| Accounts | Named permissions for the required operation |
| Backend | Deployment instructions and isolated recovery exercise |
| Documentation | Instructions followed and corrected by the receiver |
Frequently asked questions
Can assessment start with incomplete documentation?
Yes, but record the gaps and their consequences. Scope release and support commitments around what the assessment actually establishes.
What is a useful first technical exercise?
Produce a test package from identified source in a documented environment, then check the main journey and an existing installation's update path.
Should we request every production password?
No. Identify necessary tasks and roles first, then arrange named access and secure credential handling.
Does a takeover mean rewriting the app?
No. Establish current behaviour and risk first. Decide separately on necessary repairs and optional modernisation.
Discuss your project
Describe the product, available materials, known issues and next required change. Identify an outgoing contact if possible. Redacted notes and test data are enough for an initial discussion; access can then be arranged for the agreed assessment tasks.


