Blog
What to do when your app developer disappears
A practical checklist, not a panic response — what to gather, what to do first, and what a rescue engagement actually involves.
Short answer
The short answer.
You're very likely not stuck. Gather whatever access and documentation you can find, make one direct attempt to contact the original developer if possible, and then get a technical audit rather than assuming a full rebuild is the only option. Most apps in this situation are recoverable in some form — the question is what it costs to recover versus rebuild, and that's answerable once someone actually looks at the code.
First, gather this
The access checklist.
Before anything else, work out what you actually have access to. This is the single biggest time-saver in a rescue situation — a lot of "the app is broken" problems turn out to be "we can't get into the accounts that would let anyone fix it."
- Source code repository access (GitHub, GitLab, Bitbucket, or wherever the code lives)
- Apple Developer account access, or at minimum, who the account is registered to
- Google Play Console access, or the same ownership detail
- Backend/hosting account logins (Firebase, AWS, a VPS provider — whatever the app runs on)
- Domain and DNS access, if the app depends on your own domain or subdomain
- Third-party service accounts: payment provider, push notifications, analytics, error tracking
- Any design files (Figma, Sketch) the original developer worked from
- Any documentation, README files, or the original contract/statement of work
What to do first
Order of operations.
1. Secure access before anything else. Change passwords on any accounts you do control, and start the ownership transfer process on Apple Developer and Google Play Console accounts immediately — these can take time, so start them in parallel with everything else rather than waiting until you've decided on a path forward.
2. Make one direct attempt to contact the developer. Ask specifically for repository access and account ownership, not a general check-in. Give it a reasonable, defined window — a few days, not weeks — then proceed with what you have.
3. Get an honest technical assessment before deciding anything. Resist the urge to commit to a full rebuild out of frustration, and resist the urge to assume the existing code is fine just because the app still technically runs. A proper audit — reviewing the codebase, dependencies, and deployment setup — is what tells you which situation you're actually in.
What happens next
What an app rescue engagement actually involves.
It's rarely an immediate rebuild. A proper rescue starts with a paid technical discovery or codebase audit — reviewing code quality and structure, how the app is built and deployed, dependency health, and security and data handling — before any larger commitment is made on either side. That audit tells you honestly whether stabilising the existing app or a targeted rebuild of specific parts is the faster, cheaper path. We don't promise every app can be rescued as-is; we do promise to tell you which situation you're actually in before you spend real money finding out.
For the full process — including what a codebase audit checks and how a stabilisation plan gets prioritised — see our Legacy App Modernisation page.
FAQ
Common questions.
Tell whoever you talk to next exactly what you do have — even if that's just store listings or a partial export. Assessing what's recoverable is the actual job of a technical discovery engagement; missing access changes the plan, it doesn't automatically mean starting over.
It's worth one clear, direct attempt — asking specifically for repository access and store account ownership, not a general check-in. If they don't respond within a reasonable window, proceed with what you have rather than waiting indefinitely.
No. Most apps are recoverable in some form, even without the original developer, because the compiled app is still live in the stores and often still has recoverable source somewhere (your own accounts, a former employee, an old laptop). The real question is what it costs to recover versus rebuild, which a proper audit answers.
It depends entirely on what state the code is in, which is exactly why a rescue engagement starts with a paid technical discovery or audit rather than a guessed number. That audit tells you honestly whether stabilising the existing app or a targeted rebuild is the cheaper path — see our general app cost guide for realistic build ranges once you know which one you're facing.
Transferring an Apple Developer account or Google Play Console ownership can take anywhere from a day to a couple of weeks, depending on how responsive the current account holder is and whether Apple or Google need to verify the transfer. Starting that process immediately, in parallel with a technical audit, is usually the fastest path.
Related
Where to go next.
Legacy App Modernisation
The full audit and recovery process for a stalled or broken app.
How much does an app cost?
Realistic ranges once you know whether you're rebuilding or rescuing.
Get in touch
Tell us what state the app is in — no obligation to commit to anything yet.
Talk to us