You send a message asking for a status update. No reply. A day passes, then a week, and the invoices you were expecting, the builds you were promised, and the developer you were paying have all gone quiet. Whether you hired a freelancer, a small agency, or an offshore team, a developer disappearing mid-project is one of the most stressful moments in building an app — and panic is the worst response to it.
Table of Contents
This guide walks through what to do in the first 48 hours, how to figure out what you actually own and control, and how to get the project moving again without losing more time or money than you already have.
Quick Answer
Stop trying to reach the developer and start securing what you have: confirm you own the code repository, hosting, domain, app store accounts, and database credentials. Document the missed communication and unfinished work, then get a new developer or agency to audit the existing codebase before anyone writes another line of code. Don’t hand it off blind — a rushed handoff usually costs more than the delay did.
Step 1: Secure Your Access Before You Do Anything Else
Before you worry about finishing the app, make sure you can still get to everything that makes it exist. Check that you (not just the developer) have owner-level access to the source code repository, whether that’s GitHub, GitLab, or Bitbucket. If the developer created the repo under their personal account, ask to be added as an owner or have it transferred — most git hosts support a repository transfer or ownership-change feature for exactly this situation.
Do the same check for your hosting provider or cloud account (AWS, Google Cloud, DigitalOcean, Firebase), your domain registrar, your Apple Developer and Google Play Console accounts, your database, and any third-party API keys (payment processors, analytics, push notification services). If you don’t have admin rights to any of these, request access immediately, in writing, with a deadline. If credentials only exist in the developer’s head or personal accounts, that’s your biggest exposure — treat regaining control of it as the top priority.
If you genuinely cannot get access to code or accounts and the developer stays unresponsive, you may need to rebuild locked-out pieces (a new App Store listing, a new hosting account) rather than wait indefinitely.
Step 2: Know What You Legally Own
This surprises a lot of first-time app founders: if you never signed a written contract that explicitly assigns copyright or IP to you, the developer may legally own the code they wrote, even though you paid for it. Payment alone does not transfer ownership — only a written agreement does. Independent contractors are not automatically covered by “work made for hire” rules unless a signed agreement says so.
Pull up whatever contract, proposal, statement of work, or even email exchange you have and look for language about IP ownership, deliverables, and what happens if either party stops performing. If you hired through a platform like Upwork or Fiverr, their standard terms typically grant you ownership of paid work, which gives you more legal footing than an informal arrangement. If there’s no agreement at all, consult a lawyer before assuming you can freely hand the code to a new developer — in most cases using code you paid for is low-risk, but it’s worth understanding your position, especially for a commercial product.
Going forward, this is the single easiest thing to prevent next time: get IP assignment in writing before any project starts.
Step 3: Document Everything and Try Formal Contact
Before writing the relationship off, send one clear, dated message (email is better than chat, since it creates a record) outlining the outstanding deliverables, the last date of contact, and a specific response deadline — five to seven business days is reasonable. Keep a simple log of every attempted contact: dates, channels used, and what was said. This record matters if you later need to dispute a payment, file a chargeback, or pursue a freelance-platform’s dispute process.
If you paid through a marketplace like Upwork, use their built-in dispute process rather than going it alone. On Upwork, if a freelancer doesn’t respond to a refund or milestone-cancellation request within about seven days, funds are returned to the client automatically; if they do respond and disagree, the case goes to Upwork’s dispute team, who typically provide a non-binding resolution within a couple of days after both sides submit their case. Fiverr and similar platforms have comparable resolution centers. If you paid via a bank transfer, PayPal, or credit card outside a platform, check your payment method’s dispute or chargeback options — timing windows are usually 60 to 120 days, so don’t wait too long to start that process if it comes to it.
If the developer was under a signed contract, review it for a termination clause and a cure period (a window they’re given to fix the breach before you can end the agreement) — following that process protects you if you end up needing to recover payment through small claims court or arbitration.
Step 4: Get the Existing Code Audited Before Hiring a Replacement
The instinct is to immediately hire a new developer and say “just finish it.” Resist that. Half-finished codebases are often messier than they look, and a new developer working blind can waste weeks just figuring out what exists, what’s broken, and what was never actually started despite being marked “done.”
Instead, have a new developer, agency, or freelance code auditor spend a short, paid engagement (often just a few hours to a couple of days) reviewing what you have: does the app actually build and run, is the code organized in a way that’s maintainable, are there tests, is the database schema documented, and how far from your original spec is the current state. This audit gives you a realistic estimate for finishing the project instead of a guess, and it often reveals whether it’s faster to continue the existing codebase or restart key parts of it.
Use the audit findings to get comparative quotes from two or three developers or agencies before committing, especially if the remaining work is substantial.
Tips / Common Mistakes
Don’t keep paying invoices hoping the developer resurfaces — pause payment the moment communication breaks down, and only resume once work resumes and is verified. Don’t skip the code audit to save money; it almost always costs less than the rework caused by a blind handoff. Don’t rely on one person for all your project knowledge going forward — require documentation, regular check-ins, and shared repository access from day one on any future contract, so a single disappearance can’t stall the whole project again. And don’t assume silence means malice: developers often go quiet because they’re overwhelmed, in over their head on scope, or dealing with a personal emergency, not because they’re scamming you — but your response (securing access, documenting, and moving forward) should be the same either way.
Explore more: More app development guides.
app developer going silent mid-project FAQs
How long should I wait before assuming my app developer isn’t coming back?
Give one clear, written deadline of about five to seven business days after your last real update. If that passes with no response, start securing access and looking for a replacement in parallel — you can always resume with the original developer if they reappear with a good explanation.
Can I use the code my developer already wrote if they never respond?
Usually yes if you paid for it, but your legal footing depends on whether a contract assigned you the copyright. Without a written IP clause, the developer may technically own the code even though you paid for it. Check any contract or platform terms first, and when in doubt, get a quick legal opinion before building a commercial product on disputed code.
Should I file a dispute or try to get a refund instead of finishing the project?
That depends on how much usable work exists. If the codebase is a mess or barely started, a refund (via your payment platform’s dispute process or a chargeback) may be faster than salvaging it. If there’s substantial working code, it’s often cheaper to pay a new developer to finish than to start over, so weigh the audit results before deciding.
How do I prevent this from happening on my next project?
Require a written contract with an IP assignment clause, keep repository and hosting accounts under your own admin account from day one, split payment into milestones tied to working deliverables rather than time, and ask for regular, documented check-ins instead of relying on informal updates.
Build It With GTStudios
Need help with your website, app, or small-business tech? GTStudios builds web, apps, and software for small businesses. See how GTStudios can help.
Photo by Razlan Hanafiah on Unsplash.