My developer disappeared and my app is half-built. What do I do first?

By Ranjit Bhinge, founder of Blur Studio · Updated · 8 min read

Short answer: First, secure access before you do anything else: your code (stored in a repository, which is an online folder of your app's files and history), your hosting, your domain name and your app store accounts. Make a list of every account the app touches, check which ones you own and which sit under the developer's name, and request transfers in writing. Once you hold the keys, get the code reviewed and choose between repair and rebuild using a simple rule: repair if the app mostly works and is understandable, rebuild if you cannot get it to run or nobody can explain how it works.

Ranjit Bhinge

Your developer has gone quiet, the app is not finished, and you do not know what you actually own or how to get it back.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

This happens more than people admit. A freelancer takes a better job, an agency closes, a friend gets busy, or someone simply stops answering. You are left with an app that is half-built and no idea where it lives. The good news is that most of this is recoverable. The order of steps matters, so read the first section before you send any angry messages.

What not to do first

  • Do not delete anything. Changing passwords or removing the developer from accounts is fine once you hold the owner role. Deleting projects or repositories is not.
  • Do not threaten legal action in your first message. Send a calm, specific request for access and a handover. Most developers who go quiet respond to a clear, short, polite message. If they do not, you still have a paper trail.
  • Do not send extra money in advance to get things back, unless your contract requires it and you can see what the payment buys.

Days 1 to 3: find out what exists and who owns it

Make a table with one row per service the app uses. For each row write: who owns the account (you or the developer), who can log in today, and whether you can get access without the developer. Start with this list. To prepare for a new developer, see what to give a developer taking over your AI-built app.

ServiceWhat it holdsHow ownership moves
Code repository (GitHub, a website that stores code, or a similar service)All your app's files and their historyGitHub: the owner needs admin access to transfer it. The new owner gets a confirmation email, and GitHub's docs say the invitation expires if it is not accepted within one day
Hosting, the computers that run your live app (Vercel, Render, Netlify and AWS are common ones)Where the live app runsVercel's docs say you can move a project between teams with no downtime, but you must be an owner of the team you move it from
Domain nameYour web addressTransferred between registrars (the companies that sell domains). ICANN's policy says the registered name holder's authority overrides the administrative contact in a dispute
Database, where your data is stored (Supabase and Firebase are common ones)Your customer and business dataAdd yourself as owner or invite your own admin account. Export a copy straight away
Apple App Store accountYour iPhone appApple's docs say the Account Holder starts a transfer, and a pending transfer expires after 60 days
Google Play accountYour Android appGoogle's help says both developer accounts must be registered and active, and creating a new one costs a US$25 fee
Payment processor, a company that takes card payments (Stripe is a common one)Money flowing inShould be in your business name from day one. Check it is
Email, analytics, other toolsSending, trackingCheck each one for who owns it

Where do you find this list if the developer will not send it? Look at your own email. Search your inbox for the words "welcome", "invoice", "verify your email" and "receipt". Every service that was set up with your email address will have sent you something. Also look at your bank or card statements for monthly charges, because every paid service leaves a line there. Open the live app in a browser and look at the web address and any text in the footer. These clues usually cover most of the list.

How to ask for access in writing

Send one message by email, not chat. Copy the template below and fill in the brackets.

Subject: Handover of [app name] by [date]

Hi [name]. I need to take over [app name] and want to make this simple. By [date, 7 days away], please give me or transfer to me: the code repository, the hosting account or a team invite with owner rights, the domain registrar login or transfer code, the database, and any app store accounts. Please also send a list of every service the app uses with the account email for each, and any passwords or keys kept outside those accounts. If part of this is a problem, tell me which and why. Thank you.

Keep a copy of every reply and every silence. If your contract says you own the work, that message plus the contract is your record. If you have no written contract, ask a lawyer before you pay more money or do anything that looks like taking the code. Who owns what depends on your agreement and your local law, and I am not a lawyer.

Get a copy of everything now

While you wait for a reply, make copies of whatever you can reach today.

  • Code: if you have any access to the repository, download it as a zip file or ask a technical friend to clone it, which means making a full copy of the files and history on another computer.
  • Data: export your database. Supabase's backup guide says free-tier projects should export regularly with its command line tool and keep off-site copies. Most tools have an export button for tables or CSV files.
  • App store details: Apple's transfer guide tells you to back up app information before a transfer, including your metadata, pricing and dates, and to save sales and download data. Google's guide says payout and earnings reports do not move with the app, so download those first.
  • Screenshots of how the app looks and works, and a short video walk-through of each screen.

If the app is on Bubble, a no-code tool, the plan can be handed over inside the app's settings: Bubble's manual says an admin can transfer the plan to another registered user under Collaboration settings. If you have any questions about moving an app out of a builder tool, how to export code from an AI app builder explains what you can and cannot take.

Days 4 to 10: give the code a proper look

Once you can see the code, do not start building. Get an independent review first. Ask a developer who is not the one who left to look at the app and give you a one-page report. It should answer:

  1. Can the app be run on a fresh computer from the instructions in the repository?
  2. What works, what is half-done and what is missing compared with your original list?
  3. Is there a README (a plain text guide at the top of the repository) and are there tests?
  4. Are secrets such as passwords or keys sitting in the code where anyone with access can read them?
  5. Which services does it depend on, and what do they cost each month?
  6. How much of the code looks AI-generated and untested?

A review like this is a small job compared with a rebuild, so ask the reviewer for a fixed price and a time estimate before they start. It is the cheapest insurance you can buy before you commit to a long build. If you are comparing who should do the review, fractional CTO versus development agency sets out the difference between getting advice and hiring a build team.

Repair or rebuild: a decision rule

Repair ifRebuild if
The app runs and most of your list worksIt will not run, or runs only on the old developer's machine
A new developer can explain the structure in an hourNobody can explain how it holds together
Missing parts are features, not foundationsThe database design is wrong for what you need
The tools used are common and well supportedIt relies on an obscure or abandoned library
Fixing costs under about half a rebuild quoteRepair estimates keep growing as people look closer

Worked example with invented figures. Your app has 12 planned screens. Seven work, three are half-done and two do not exist. A reviewer says the structure is clear. A repair quote of $6,000 against a rebuild quote of $14,000 means repair wins easily. Now change the facts: only three screens work, the data tables are muddled, and the reviewer cannot run it locally. A repair quote of $9,000 with a warning that "more may appear" against a rebuild of $14,000 is much closer, and the rebuild gives you code a person understands. Get both quotes in writing, with a list of what is included. Once you have access, see taking over software from a developer who left.

If the code was largely made by an AI tool and is half-done, half-built app: can AI finish it or do you need a developer goes through that case. If you started as a prototype, prototype with AI, finish with a developer shows a sensible way to split the work. For budget ranges, see AI app development cost.

The one-page handoff brief

Whoever takes over will ask the same questions. Answer them once, in one page, and every quote you get will be better. Include:

  • What the app is for, and who uses it.
  • The list of screens or features, split into done, half-done and not started.
  • Every account and service, with the owner and the monthly cost.
  • What you were promised and what you paid so far.
  • Your deadline and what happens if it is missed.
  • The thing that must work first, such as taking payments or booking an appointment.

Stop it happening again

  • Open every account in your own name and invite the developer as a team member.
  • Put the code in a repository you own from day one.
  • Ask for weekly working demos, not weekly status messages.
  • Pay by milestone, not by date.
  • Keep a running list of accounts that you update monthly.

How I'd approach this

I would treat the first week as a recovery job, not a building job. Secure access, copy everything, then get an outside review before spending real money on a plan. Owners often rush to hire the next developer in a panic and end up in the same position six months later.

My own rule: nothing gets built until you can answer three questions. Do I control every account? Does the code run on a clean computer? Do I have a short list of what is missing? When those three are yes, you can hire anyone, repair or rebuild, and judge their quote properly. If you want help finishing a half-built app, Blur Studio does that work, and the finish page explains what is included.

Questions people ask

Who owns my app if the developer abandoned it?

It depends on your written agreement and local law, so ask a lawyer if there is a dispute. Separate from legal ownership, there is practical control: whoever holds the accounts for the code, hosting, domain and app stores controls the app today. Check each account and request transfers in writing.

How do I get the code if my developer will not respond?

Check whether you have any access to the repository, such as an invitation in your email from GitHub. If so, download a copy now. If not, send a clear written request with a date, and keep the reply or silence as a record. Do not try to get in through someone else's login, and if the contract is unclear, speak to a lawyer.

How do I find out what services my app uses?

Search your email for welcome messages, invoices and verification emails, and check your card statements for monthly charges. Then look at the live app's web address and footer. A reviewer can also read the code for service names and keys. The one-page brief in this guide helps you collect it.

Should I repair or rebuild an inherited app?

Repair if the app runs, most of it works and a new developer can explain the structure quickly. Rebuild if it will not run elsewhere, or nobody can explain how it fits together. Get both quotes in writing. The wider costs are in AI app development cost.

Can AI finish a half-built app that a developer left?

Sometimes, for small gaps in code that already runs and is well organised. It struggles when the foundation is unclear. Read half-built app: can AI finish it or do you need a developer before you decide.

How long does it take to take over an abandoned app?

Securing access and getting a review is mostly waiting on transfers and replies, so it varies a lot; plan on days to a few weeks. Apple's transfer requests expire after 60 days if the other side does not accept, and GitHub's repository transfer invitation expires after one day, so move quickly once you request them. The build time after that depends on your repair or rebuild choice.

More in this topic: Problem solving: AI-built and no-code apps (26 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…