Help for owners
My app has no documentation and only one person understands it
Short answer
An undocumented app is a risk because everything depends on one person's memory. You do not need a big manual. Write down where the code, accounts, servers and keys are, how to build and release, and how to restart things. That short page lets another engineer take over without a long guess.
Does this sound like your situation?
- If my developer leaves, I do not know who could fix the app.
- I cannot say which services or accounts the app depends on.
- Nobody has written down how to release an update.
- A new developer asked for notes and there are none.
- Every change takes long because people have to work out what the code does.
Why does this happen?
Documentation was never in the scope
A quote usually covers features. Notes, diagrams and handover pages are not requested, so nobody builds them.
The first developer carried everything in their head
With one developer, notes seem unnecessary. The risk only appears the day that person is unavailable.
Setup steps live on one laptop
Build settings, secret keys and scripts that were never saved in the repository make a clean build impossible for anyone else.
The app changed faster than the notes
Where notes existed, they went out of date after a few releases, and out-of-date notes are as risky as no notes.
What can I do about it today?
- Write the list of accounts and who owns eachCode repository, Apple and Google accounts, hosting, domain, email sending, payment provider, analytics. One line each: where it is and which company email owns it.
- Ask your developer to record how to releaseA short video or a numbered list of steps from 'code is ready' to 'update is in the store' is already valuable.
- Make sure the code sits in a repository you can openYour company should be an owner of it, not just a guest.
- Ask where secrets are keptPasswords, API keys and signing files should be in a password manager or vault your company controls, not in chat messages or on one machine.
- Do not ask for a huge documentA few accurate pages beat a long manual nobody keeps updated. Start with the items above.
When should I bring someone in?
- Your only developer is leaving or has become unreachable.
- A new engineer cannot build the app from the code you have.
- You are preparing to sell the company, raise funds or pass a technical review.
How do I handle it?
- Read the code and run itI get the app building from a clean machine. Where that fails, I note exactly what was missing.
- Write the handover pagesAccounts and owners, how the pieces connect, how to build and release, and how to restart or roll back. In plain language first, technical detail after.
- Add short notes where the code is confusingI leave comments and a short map of the main parts, so the next engineer is not guessing.
- Keep the pages in the repositoryThe documents live next to the code so that they change with it, and I note when each page was last checked.
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?
Do I need full documentation?
Usually not. A short, accurate handover covering accounts, release steps and recovery gives most of the protection.
Can you document code someone else wrote?
Yes. I read it, run it and write down what I find. Where I cannot tell what something does, I say so rather than guess.
Why not ask my developer to do it?
You should, and it is cheaper. An outside engineer is useful when the developer is gone or when you want the notes checked by someone who has to use them.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.