Your app developer disappeared. Here is what to do next.
An app handover checklist to take ownership this week, and a fixed-price audit that tells you what you actually own.
If the app is already broken, or the project stalled half-built, skip the reading and email me now: mostafa@keystonesystems.eu. For exactly that situation there is the Emergency Project Analysis: EUR 1,500 fixed, a decision-ready report in 5 working days. Everyone else, start with the checklist below, or go straight to the audit.
The person who built your app is gone. Maybe the developer quit. Maybe the agency stopped supporting the app when the contract ended. Maybe you let them go and the handover never happened. Whatever the reason, you now own an app that nobody on your side understands.
The app still runs, and that is the dangerous part. An abandoned app rarely breaks right away, so fixing the situation never feels urgent. But something will break. Apple ships a new iOS every year and old code often breaks under it. Certificates expire. A backend bill goes unpaid because nobody knew it existed. When that day comes, you will be paying a stranger to learn your entire codebase in the middle of an outage.
You can deal with this in two steps. Take ownership of everything first. Then find out what you actually have.
App handover checklist: take ownership of what you have
Do this now, while the developer still answers email. Every week that passes makes each item harder to recover. All of this is free advice. None of it requires me.
1. Get the source code from your developer
Find where the code lives. Usually that is GitHub, GitLab, or Bitbucket. You want ownership of the repository or the organization transferred to you, not a zip file. A zip loses the history, and the history tells a new developer why things are the way they are. Once you have access, confirm someone can actually clone the code and that the newest version matches what is in the App Store.
2. Transfer the app to your own Apple Developer account
Check which account the app is published under. It should be a company account you own, with you as the Account Holder. If the app sits in the developer's personal account, Apple lets you transfer an app between accounts in App Store Connect in most cases, though some app configurations block the transfer. Ask for it now. Collect the signing certificates and provisioning profiles, and note the yearly membership renewal date so it does not lapse. If you have an Android version, do the same for the Google Play Console and keep your own copy of the upload keystore.
3. Take ownership of the backend and hosting
Most apps depend on a server. Find out where it is hosted. AWS, Google Cloud, Firebase, or a rented server somewhere. Get owner access to that account, move the billing to your own card, and get access to the database. Do the same for the domain name. Apps have gone offline because a hosting invoice went to an inbox nobody read.
4. Collect the third-party service logins
List every outside service the app uses. Crash reporting, analytics, push notifications, payment providers, email and SMS senders, maps. Each one has a login and often an API key. Get all of them into a password manager you control.
5. Save whatever documentation exists
Ask for anything written down. Architecture notes, a README, the original proposal, handover notes, even old chat threads about why a decision was made. Most inherited apps come with nothing, and that is workable. But anything you can save now is worth saving.
If your app developer is not responding, or will not hand over the source code, check your contract. In most contracts the code you paid for belongs to you. A short, firm email that quotes the contract usually gets the repository transferred within days.
How to take over an app from a previous developer
Getting control of the accounts protects the app. It does not tell you whether the app is any good.
That is the question that matters now. Can a new developer maintain this codebase, or does it need a rewrite? What will it cost to keep running each year? What should the next person work on first? Right now you cannot answer any of that, and every developer you interview will have an opinion and an incentive.
This is what my app audit is for. I am Mostafa, a senior iOS engineer with more than nine years of building apps. The full Mobile App Audit is a fixed price of EUR 2,900 and takes 7 to 10 working days. If the project is stalled or half-built and you mainly need a decision basis fast, the Emergency Project Analysis is EUR 1,500 and takes 5 working days.
You get a scored report across five lenses: architecture, code quality, performance, stability, and the delivery pipeline. Every risk is priced in plain terms, so you know what it means for your business and not just for the code. The report ends with a prioritized fix plan with an effort estimate for each item. Two follow-up calls are included, and there is no lock-in of any kind.
After the audit you know whether the app is maintainable, roughly what it costs to keep running, and what any new developer should do in their first month. When someone quotes you three months for a small feature, you can check that against the report instead of taking it on trust.
To start, I need read access to the code repository and about an hour of your time for questions. That is all.
Get the app audit, fixed price
What the report looks like
To show you exactly what you get, I audited Homelab, a real app whose developer stopped working on it and archived it. Its code is public. You can download the full 9-page report.
Some of what it found:
- Two dashboards that are 92 percent identical, because the app grew by copying files.
- A monitoring app that silently shows zeros when its data fails to load, so users trust numbers that are wrong.
- A build that shipped 33 releases on a green checkmark that only ever proved the code compiled, never that the tests passed.
- Credit where it is due: genuinely disciplined performance work that scored 7 out of 10. The report says what is good, too.
Overall score: 5.3 out of 10, with a clear verdict: restructure in 6 to 8 engineer weeks, no rewrite needed. That is exactly the kind of answer you want before you decide what to do with an inherited app. A second sample on the audit page, a mature codebase that scored 6.6, shows the same method on well-kept code.
What happens after the audit
The report is yours. There are two common paths from here.
You hire someone to take over the existing iOS app. Hand them the report on day one. It replaces the handover that never happened. It tells them how the app is built, where the risks are, and what to fix first. It also gives you a way to judge their work, because you can watch the top items on the plan get done.
The app needs real work. If the audit shows deep problems, I take on Remediation & Takeover engagements, EUR 15,000 to 45,000, scoped from the audit findings and split into phases of 2 to 4 weeks. Each phase has its own price and you approve it before it starts, so the estimate risk stays mine, not yours.
Either way, you stop depending on trust alone. You have a written, scored account of what you own.
Common questions
The developer abandoned my app and I do not have the source code. What now? Get the code first. The checklist above covers where to look and how to ask. If the developer has vanished completely, your contract and a formal letter usually recover it. If the code is truly gone, there is nothing to audit, and the honest answer is that the app will need a rebuild. Email me before you spend anything and I will tell you which case you are in.
How do you work without documentation? I read the code. Almost every inherited app I see comes with no documentation at all, so the audit assumes none. The report I write becomes the documentation your next developer starts from.
Do you only audit iOS apps? iOS is where I have spent nine-plus years and it is the core of the work. I also audit Flutter, React Native, and native Android apps, plus the backend behind the app, because that is often where the real problems are.
How fast can you start? It depends on my current bookings, so email me and I will give you a date. The full audit takes 7 to 10 working days once I have access to the code, the emergency analysis takes 5. If something is already broken, say so in your first email and I will tell you honestly which one fits your situation before you pay.
Stop guessing about your own app
The developer is gone. You can keep the app running without them. Take back the accounts this week, then get a written answer on what you actually own.
Get the app audit, fixed price published
Questions first? Email me: mostafa@keystonesystems.eu