Help for owners
My only developer is unavailable and my app or site needs attention
Short answer
First find out whether anything is actually broken, and tell customers if it is. Do not guess at fixes or share your passwords. Gather the accounts and records you hold, wait a reasonable time for a reply, and bring in a second developer with limited access if it is urgent. Then reduce the dependence on one person.
Does this sound like your situation?
- My developer has not answered for days and something needs fixing.
- My site or app is down and the only person who knows how it works is away.
- I do not know where my code, servers or app store accounts are.
- I am the only one with a login, and I do not understand what it is for.
- I worry this will happen again.
Why does this happen?
Everything depends on one person's memory
When one person knows how the app is built, deployed and hosted, their absence stops all work. Nobody else can see where things are.
Accounts are in the developer's name
If hosting, the code repository or the store accounts are held by the developer, you cannot even see what exists. Google Play Console, for example, lets an owner or admin invite other users, so a second person can be added when the owner is in charge.
Confirmed by support.google.com
There is no written handover
Without notes on how to deploy, where backups go and which services are used, a new person must reverse-engineer the setup.
Urgent changes get rushed
A hurried fix by someone who does not know the system can make the problem worse, so a calm first assessment matters.
What can I do about it today?
- Check whether anything is really brokenOpen your app and site as a customer would, on a phone and a computer. Note what fails, with screenshots.
- Tell customers if neededA short honest notice that you are aware and working on it is better than silence.
- Contact the developer through every channelEmail, message and a short call request. Keep the messages as a record.
- Collect what you already holdDomain registrar login, hosting emails, app store accounts, invoices and any documents. Make a single list.
- Do not share your passwords or ask someone to guessIf you bring in someone else, invite them as a named user with limited access, and keep your own login.
- Do not delete or reinstall anythingRestarting from scratch can lose data that cannot be recovered. Wait for a person who has looked at it.
When should I bring someone in?
- Customers cannot use the app or site and payment or orders are affected.
- Your developer has not replied for several days and nobody else has access.
- The domain, certificate or a store account is about to expire.
How do I handle it?
- Assess without changing anythingWith your agreement I look at what is running, what is down and what the logs say, using read-only access where possible.
- Stabilise firstIf something must be fixed, I take a backup first, make the smallest change and keep a way back.
- Map what existsI write down where the code, servers, domain, stores and third-party services are, and who holds each login.
- Fill the missing documentsA short runbook covers how to deploy, where backups are and whom to call, so the next absence is less severe.
- Share the knowledgeWhere you want it, I stay available on a monthly basis so there are always two people who know the system.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can a new developer take over quickly?
It depends on whether the code, accounts and notes are available. I first assess what exists before saying how long it takes.
What if the developer never comes back?
Gather proof that the work is yours, such as contracts and invoices, and make sure you hold the domain and store accounts. I can help you take over.
Should I hire a second developer now?
A second person who knows the system reduces the risk. It does not need to be full time.
What should I never do in an emergency?
Do not delete data, reinstall the server or share your owner passwords.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.