App rescue checklist

Developer disappeared? A checklist to get your app back

Last reviewed 3 November 2026

Your developer has stopped replying and the app depends on accounts you may not control. Work through these steps in order. Most of them need no technical knowledge, and they’ll show you exactly where you stand.

Short answer

Don’t rush to replace anyone yet. First list what the app depends on and find out who controls each item, then make one clear written request for the code and accounts, and keep everything paid and running. Once you know what you have, you can decide whether to finish the app or rebuild it.

1. Keep the app alive

Before anything else, look for payments that could stop the app working if they lapse.

Hosting and cloud bills. If they’re on the developer’s card, the service may stop when that card does.
Apple Developer and Google Play accounts. Find out who holds them. An Apple membership needs renewing every year for apps to stay available.
Domain name. Look up when it expires and who controls it. Your website, emails and app may all depend on it.
Paid services: payments, email, maps, push notifications or AI providers.

2. Find out what you already have

You may hold more than you think. Search your email, contracts and invoices for:

Your contract, especially who owns the code and what happens when the work ends.
Invitations from GitHub, GitLab, Bitbucket, Apple, Google, AWS, Firebase or Supabase. You may already have access.
Logins, documents and links the developer shared in chats.
The seller name on your App Store and Google Play listings. It shows whose account published the app.
Payment records for any accounts or services, since these can help prove the account is yours.

3. Make a list of who controls what

Note each item below, and mark it as yours, theirs or unknown.

Source code and its repository, including every branch and any backend code.
App Store Connect and Google Play Console.
Servers, cloud and database, including backups.
Domain and DNS.
Payments and subscriptions, such as Stripe or RevenueCat.
Third-party services and API keys.
Design files and documentation.
Signing keys. Android apps in particular depend on them to publish updates.

4. Make one clear written request

Keep it calm, since you may still need their cooperation. Try every channel you have, and keep a copy. A message you can adapt:

Hi, I haven’t been able to reach you about the app. I’m not looking to dispute anything, I just need to make sure the project can continue.

Please could you, by [date]: 1. add me as owner of the code repository, 2. start the transfer of the app to our developer account, 3. send the logins for the servers and services on the attached list?

If there’s anything outstanding between us, let me know and we’ll sort it out.

5. Transfer the accounts properly

App Store: Apple has an app transfer process. The current Account Holder starts it and the receiving Account Holder accepts it, so you’ll need your own developer account first.
Google Play: Google has a transfer process between developer accounts too, and it asks for details from both accounts.
Everything else: ask to become owner or admin, and move billing to your company. The developer can stay on as a normal user if they’re still involved.

6. If they never reply

Accounts in your company’s name: use the provider’s account recovery, and have your business documents and payment records ready.
App published under their account: contact Apple Developer Support or Google Play support and explain. They may not be able to move it without the account holder, so don’t count on this.
Last resort for the listing: publish a new listing from your own account. It starts with no ratings, and existing users have to install the new app, so tell them before you switch.
Domain: if it’s registered in their name, contact the registrar. Your paperwork will matter here.
Code you can’t get: if there’s no copy, the working parts usually have to be rebuilt, using the live app and any designs as your guide.
Money or ownership disputes: speak to a lawyer in your country. This checklist isn’t legal advice.

7. Secure everything once you’re in

Do this only after you have owner access, so you don’t lock yourself out of something you need.

Remove old users, and change passwords on every account.
Turn on two-factor authentication, using a company phone or authenticator.
Replace API keys and other secrets, then check the app still works.
Make a backup of the code and database that you control.

8. Decide what happens next

Ask someone independent to read the code before you commit to more work. They should be able to tell you what works, what’s risky and whether to finish or rebuild. Don’t let anyone give you a firm answer on that before they’ve seen the code.

Whoever you work with next, keep the code and accounts in your company’s name from the first day, so this can’t happen again. Our app rescue service starts with this access check and an honest written assessment. If Apple is also rejecting the app, start with our rejection guides.

Questions founders ask

Can I get the code from the published app?

Not in a form that’s useful for continuing development. The published app is compiled, so it’s no substitute for the original source code.

Do I own the code because I paid for it?

Not automatically. It depends on your contract and your country’s law, so check the contract and ask a lawyer if ownership is disputed.

Should I start again from scratch?

Sometimes, but not by default. Often parts of the code are worth keeping. An independent review will show which parts before you spend anything on a rebuild.