Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I want a new developer to take over my existing app

Short answer

A takeover needs four things from the old developer: the code with its history, access to the accounts the app depends on, the steps to build and release it, and the keys. A new developer should first audit what they receive and prove they can ship a small update before taking on any large work.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I am leaving my current developer or agency and the app must keep running.
  • I inherited an app from a previous owner with no documentation.
  • The new developer says they need the project and I do not know what to give them.
  • The app is in the store but nobody on my side can release an update.
  • I worry the new developer will want to rewrite everything.

Why does this happen?

  1. Handovers are not part of the original deal

    Most contracts end when the product is live. The code, the build steps and the account list are rarely part of what was delivered.

  2. The code can move without losing its history

    A repository can be transferred between owners with its issues, pull requests, wiki, stars and watchers, and links to the old address are redirected. The person with administrator access to the repository has to do it.

  3. Store access is managed by roles

    In Google Play Console the account owner and administrators can invite and remove users and manage their permissions, so a new developer can be given access without sharing a login.

  4. The app can be out of date for the stores

    An app nobody has touched for a while may no longer meet a store's current requirements, and a first update then needs more than a small edit.

What can I do about it today?

  1. Ask the current developer for a handover packageThe repository with history, the build and release steps, a list of the services and keys, and the staging and production addresses.
  2. Give the new developer their own accessInvite them by their own account in the store consoles and the code host. Do not share your login with anyone.
  3. Keep the old developer until the first release worksDo not close the old arrangement until the new person has built and released from your accounts.
  4. Ask for an audit before a planA short written review of what the new developer received, what is outdated and what is risky, before any estimate for big work.
  5. Do not agree to a full rewrite on the first callRewrites are sometimes needed, but a rewrite proposed before the code has been read is a guess.

When should I bring someone in?

  • The app earns money or serves customers and cannot afford a failed release.
  • The old developer is slow or unwilling to hand over.
  • You do not know whether the code you were given is complete.

How do I handle it?

  1. Audit what was handed overI build it on a clean machine, read its structure and list what is missing, outdated or fragile, in plain language.
  2. Ship a small update firstA takeover is proven when a small, safe change is built and released from your own accounts. That is my check before larger work.
  3. Write the runbookHow to build, test, release and roll back, where each key lives and what the app depends on, so you never depend on one person again.
  4. Then plan the next steps with youFix what is dangerous, update what the stores require and only then talk about new features. Decisions about rewriting come with evidence.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I have to tell the old developer?

It is best to handle it openly and in writing. If it is a dispute, ask a lawyer before you act.

Will the new developer need my passwords?

No. They should be invited with their own accounts and the permission levels you choose.

What if there is no documentation at all?

That is common. The audit produces the first documentation, written from the running system and the code.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.