It happens more than anyone admits. The demo looked good, payments went out on schedule, and then the replies slowed down and stopped. Now you have a half-finished app, a launch date, and no idea what's actually in the code. This is recoverable. Here is the order I'd work in.

Step 1: Secure Everything You Own, Today

Before anything technical, make sure you control the accounts. Check access to:

  • The code repository (GitHub, GitLab, Bitbucket). You should be an owner, not a guest.
  • Hosting and servers (AWS, Vercel, DigitalOcean, Firebase).
  • Your domain and DNS.
  • The database and its backups.
  • Apple Developer and Google Play accounts, registered in your company's name.
  • Third-party services: payments, email, SMS, maps, analytics. API keys belong to you.

If any of these were registered under the developer's personal account, request a transfer in writing now, while you still have a contact. This is the one step that can't wait.

Step 2: Get an Honest Code Assessment

A new developer should spend a few days reviewing what exists before quoting the rest. A useful assessment answers: does it build and run? Which features truly work end to end? Is the database design sound? Are there obvious security problems, such as passwords stored in plain text or secret keys committed to the repository? And is there anything resembling tests or documentation?

Be wary of anyone who says "rebuild everything" within an hour of seeing the code, and equally wary of anyone who promises to finish it without looking.

Step 3: Fix or Rebuild?

Usually worth fixing when:

  • It uses a mainstream stack (React, React Native, Node.js, PostgreSQL, MongoDB).
  • The data model makes sense, even if the screens are rough.
  • Core features mostly work and the problems are in the unfinished parts.

Often better to rebuild when:

  • Nothing runs, or only runs on the old developer's machine.
  • The data structure is wrong for what the business does, so every new feature fights it.
  • It's built on an obscure or abandoned framework nobody else can maintain.

A partial rebuild is common too: keep the backend and database, redo the app on top, or the reverse.

Step 4: Restart With Protections

Whoever finishes the project, set it up so this can't happen twice: code pushed to your repository at least weekly, working builds you can install and test, milestone payments tied to things you can see, and a short handover document as part of the deliverable, not an afterthought. My guide to hiring a freelance developer covers the questions worth asking up front.

Frequently Asked Questions

Can another developer finish an app someone else started?
Usually, yes, as long as you have the source code and it uses a mainstream technology. Expect a few days of review before an honest estimate, since the new developer has to understand the existing decisions first.
What if I don't have access to the source code?
Ask the previous developer for a transfer in writing, and check your contract for ownership terms. If the app is live, some assets can be recovered from hosting, but without the source code a rebuild is often the only realistic path.
Is it cheaper to fix the existing code or start over?
Fixing is usually cheaper when the stack is mainstream and the data model is sound. Starting over can be cheaper when the code doesn't run or fights every new feature. A short paid assessment is the fastest way to know.
How do I prevent a developer from disappearing again?
Own every account, require weekly pushes to your own repository, pay against working milestones you can test, and ask for handover documentation as part of each delivery.

The Bottom Line

An abandoned project feels like a disaster, but it is usually a solvable one. Lock down your accounts first, get an honest assessment second, and make the fix-or-rebuild call based on what the code actually contains rather than on frustration.