Skip to content

App rescue

Your developer disappeared. Here's how to get your app finished

Developer abandoned your app? Recover your code and store accounts, find out what really works, and decide: fix, finish or rebuild. A step-by-step plan.

By Arshad Mehmood, co-founderPublished 4 min read

On this page

Key takeaways

  • If a developer goes quiet, first secure every account, then get a full copy of the code, then have someone independent check what works.
  • A compiled app in the store can't be turned back into usable source code, so you need the original repository with its full history.
  • Only the Apple Account Holder can start an app transfer, and Google Play transfers are also requested from the current owner's account.
  • Don't remove the developer's access until you have a full copy of the code; then change every key and password they held.
  • Finishing is usually cheaper if the core flow works and the code is readable; a rebuild can cost less if nothing runs or the accounts are lost.

If your developer has stopped replying, or the app has been "80% done" for months, do three things in this order: secure every account you can reach, get a full copy of the code, and have someone independent check what actually works. Only then decide whether to fix it, finish it or rebuild. Moving accounts and code into your name first keeps your options open.

You're not the first. Founders who've been through it describe the same pattern: a few thousand spent, months of delay, and a half-finished app at the end (one public account). Others describe a developer going silent for weeks, or asking for more money before handing over the code. The steps below work in all of these cases.

The first 48 hours: secure your accounts

Start with a list. For each account, find out who the owner is, whose email it's under, and whether you can log in today.

AccountWhat to checkWhy it matters
Apple DeveloperWho is the Account HolderOnly the Account Holder can transfer the app
Google Play ConsoleWho owns the developer accountTransfers start from the current owner
DomainRegistrar login and renewal dateYour website, email and privacy pages live here
Hosting and databaseFirebase, Supabase, AWS or similarThis is where your users' data lives
GitHub or other code hostWho owns the repositoryNo repository, no code
PaymentsStripe or the stores' payment accountsYour money, and your customers' card records
Email, push, analyticsThe services that send messages and track crashesThe app may break if they lapse

If an account is already in your name, add a second admin you control, turn on two-factor login, and change the passwords the developer knows. Don't remove the developer's access until you have a full copy of the code. You may still need their help.

If an account is in the developer's name, ask them to move it. Apple's app transfer is started by the membership Account Holder. On Google Play, the request is made "from your original account to a different account," and Google's support team reviews it (Play Console help). You'll need your own developer accounts ready to receive the app: Apple's program is $99 a year and Google's is a one-time $25 (Apple, Google). While the app sits in the developer's Google account, their Google Play trader status declaration and contact details are the ones your customers see.

Get the code (and the rest)

The app in the store is not the code. A compiled app can't be turned back into source, so you need the original repository. Ask for it in writing, with a short list and a date. Keep the tone neutral: a calm request gets answered more often than a threat.

  • Access to the code repository with its full history, every branch
  • The backend code, not just the mobile app
  • A database export and the database login
  • A list of every outside service, API key and who pays for it
  • The Android signing key and its passwords
  • Design files and any written spec
  • Instructions to build and run the app
  • A list of what's finished, what's half-done and what's known to be broken

Once you have the code and keys, change every key and password the developer held. Treat that as routine, not an accusation.

If the developer won't hand over the code, check your contract for who owns the work and when. Ownership terms vary by country and by contract, so a short call with a lawyer is worth more than forum advice.

Find out what you really have

A demo the developer controlled tells you little. You need someone who hasn't built it to install it, read the code and tell you plainly what works.

A useful review answers five questions:

  1. Does it run? Can a new developer build it from the repository and install it on a phone?
  2. Does the core flow work on real data, start to finish?
  3. Is it safe? Are keys exposed, is user data protected, are backups on?
  4. Would the stores accept it? Account deletion, privacy policy, demo login, Sign in with Apple where needed.
  5. Who controls what? Every account, mapped to a named owner.

PerceptiaAI's App Check does exactly this: $249 or $449, in 2–4 working days. You get a plain-English report on what works, the safety problems, likely store rejections and who controls which accounts, with a clear fix, launch or rebuild answer and one fixed price.

Decide: fix, launch or rebuild

SituationUsually the right callWhat it costs with PerceptiaAI
The app runs, a list of bugs remainsFixFix Sprint: $990 for one week, up to 40 hours
It works but isn't in the stores yetLaunchStore Launch: $1,190 or $1,990
It won't build, the code is unreadable, or the accounts are lostRebuildApp Preview $299, then Starter $3,990 or Growth $7,500

A rebuild isn't a failure. If you still have the spec, the designs and what you learned from the first attempt, the second build starts with a clearer brief than the first one did. If you rebuild, start with an App Preview: your core flow clickable on your phone and one fixed price, before you commit to the build.

How to avoid this next time

Most abandoned apps share a cause: you paid before you could check anything, and the developer held the keys. Fix both before the next project starts.

  • Ownership from day one. Your Apple, Google, domain, hosting, database and payment accounts are opened in your name. The code is in your GitHub from the first commit. You invite the developer, not the other way round.
  • A build on your phone every week. Not a screen recording. An installable test build you can open yourself. If a week passes with no build, you know the same week.
  • Milestones you can check. Pay in stages tied to working builds and store submission, and keep back a final share until the app has run in the stores for a while.
  • A named lead. Meet the person who will build your app before you sign, and ask who writes the code day to day.
  • A handover pack. A README, release steps and an account list, so any developer could take over if they had to.

These are the defaults in every PerceptiaAI build: test builds every week, a plain-English Friday update, payment in stages (five on Starter and Growth) with the last 10% held until 30 days after launch, and the option to stop at any milestone and keep everything built so far. For more questions to ask before you hire, see how to choose an app development company and questions to ask an app developer.

For how a takeover runs, step by step and with prices, see the concept app: Deskhaus, a rejected app rebuilt and relaunched.

Questions people ask

Who owns the code if my developer disappears?

It depends on your contract and where you are. Many contracts pass ownership on payment, but some say nothing. If the code matters and the developer won't hand it over, talk to a lawyer in your jurisdiction.

Can a new developer get the code from the app in the store?

No, not in a usable form. A compiled app can't be turned back into the source code a developer works on. You need the original repository.

My app is in the developer's Apple account. Is it lost?

Not necessarily. Apple lets the Account Holder transfer an app to another developer account, and Google has a transfer process too. Both need the current account owner to start it, so ask early and politely.

Is it cheaper to finish the app or rebuild it?

It depends on what's there. If the core flow works and the code is readable, finishing is usually cheaper. If nothing runs, the accounts are lost or the code is a tangle, a rebuild can cost less than fixing. An independent review tells you which.