Knowledge

Who controls your app's source code and store account?

Owning an app can mean several different things in conversation. Rights to use and modify code, access to a repository, the ability to build an update and control of a store account need separate answers. This guide is general information, not legal advice. Have qualified counsel review the contract and rights for your particular arrangement.

Project handover documents, laptop and phone.

Separate rights from technical access

Describe the business situations you need the agreement to support: operating the product, modifying it, appointing another developer or transferring it to another organisation. Ask counsel to translate those needs into suitable terms. Do not rely on a broad statement that the app will be yours without identifying deliverables, permitted uses and restrictions.

Repository access provides access to files; it does not by itself establish the full legal position. Conversely, a contractual right does not automatically provide a working build or access to a release account. Keep separate lists for rights, materials and operational capabilities. Identify custom code, pre-existing components and third party libraries because their conditions may differ.

Define deliverables and handover conditions

Name the mobile client, backend, administration interface, editable design sources and documentation where they are included. Identify external services that remain dependencies rather than deliverables. The technical schedule should identify the delivered state and how acceptance works. A demonstration and a maintainable system can involve different handover materials.

Clarify when agreed rights take effect, what conditions apply and how supplier change assistance works. Those answers depend on the actual agreement and legal context. Also define how discrepancies found at acceptance are resolved and what later assistance covers. Review the contract alongside the technical checklist so a promise of a build includes an understood environment and usable instructions.

Connect the repository to the released product

Identify the source revision corresponding to the published app. Agree which history, branches, release tags and issue records are included. A copied folder alone does not explain what produced the live product. Ask for dependency information and known limitations so the next developer can distinguish an expected constraint from a new defect.

An organisation controlled repository with named developer invitations may make access management clearer. Decide who can administer it and what happens when a contact leaves. Keep secrets in a suitable dedicated system rather than placing them in source or handover notes. Documentation should name required configuration items and access routes without exposing credential values.

Distinguish account control from app transfer

Before launch, agree which organisation's developer account publishes the app and who manages billing and official notices. Developers can be invited through suitable roles rather than sharing one personal login. Ownership administration and release work may be handled by different people. Record the permissions needed for each responsibility.

For an existing app in another account, check the official transfer processes and eligibility rules. Apple and Google publish procedures for moving apps between accounts. Do not assume changing a password is a substitute. Google's guidance specifically notes that integrated service permissions and linkage settings do not transfer automatically. Inventory connected services and verify the applicable Apple considerations too.

Plan checks for backend access, notifications, identity services and analytics alongside the store process. Confirm that the next release can update existing installations. Record what was tested and which account now controls each service. The purpose is continuity of the product as a whole, not simply moving the visible listing.

Prove that an authorised team can make an update

Build instructions should cover tooling, dependencies, configuration and verification. Another authorised developer should be able to follow them in an agreed environment. A process that only works on a departing developer's laptop leaves continuity unproven. Identify signing responsibilities, secure storage and recovery arrangements using the platform's actual capabilities.

Use an isolated environment and test records for the handover exercise. Check upgrading an existing installation as well as installing afresh. Record the source revision, produced package and unresolved prerequisites. Do not indiscriminately copy or rotate signing material: assess the applicable arrangements and dependencies before making changes that could affect future updates.

Include the backend and editable assets

Mobile code is insufficient if the main journey depends on an undocumented server. Include backend sources where agreed, the data model, deployment instructions, backup procedures and external integrations. Review account and data handling arrangements, particularly when control moves between organisations. Keep production data out of ordinary source archives.

Ask for editable design files and an inventory of licensed fonts, icons, photographs and other assets. Screenshots do not provide the same ability to maintain a design. Document business rules and known exceptions too. A joint walkthrough can capture why the system behaves as it does, then the receiving team should compare those notes with actual behaviour.

Close with evidence and an access review

Use a signed off checklist of received materials, a tested build, verified permissions and named open items. Coordinate removal of old access with proof that the new operating path works. Decide who watches the next release, handles incident reports and approves recovery actions. Review the final access list after transition.

Counsel should assess contractual rights; technical exercises establish operational capabilities. These complement each other. tealtap takes over native Swift and Kotlin apps, Flutter, React Native and PWA applications. We assess source access, licences and supplier arrangements before planning changes.

Frequently asked questions

Does payment automatically resolve all rights?

Do not assume that. Have the actual agreement, component origins and permitted uses reviewed by qualified counsel.

Is receiving the source code enough?

Continued development may also need build instructions, configuration, permissions and connected system documentation. Verify these through a handover exercise.

Should a store handover be a password change?

Do not build the plan around that assumption. Check suitable roles and whether an official app transfer is required under current platform guidance.

What records should remain?

Keep the identified source state, acceptance record, rights documentation, access inventory and operating instructions. Do not place secret values in those records.

Discuss your project

Describe the product, which materials and accounts you can access, and the purpose of the planned transition. Share redacted excerpts of relevant contract questions initially. Technical assessment and legal review can then be scoped separately.

Project enquiry form
Request a quote

Tell us what you need

A few details and a short description are all we need. We’ll get back to you with the details.

What happens next

  1. Describe the task, with a redacted sample if useful.
  2. An optional AI assistant asks clarifying questions.
  3. A person reviews your request, then we get back to you with the details.
  • Built around your workflow
  • With human review
  • Design, app, maintenance
[email protected]
0 / 4000