Help for owners
My developer is only part time and my app is waiting
Short answer
A part-time developer can run an app well if the hours, the reply time and a backup person are agreed. When any of those are missing, urgent problems wait. Write down what must be handled quickly, agree fixed hours for it, and make sure someone else can reach the code and accounts.
Does this sound like your situation?
- I wait days for an answer on a simple question.
- A bug in my live app sits unfixed because my developer is on another job.
- I do not know which days my developer actually works on my app.
- If my developer is ill or away, nobody else can touch the app.
- I have no way to ask for something urgent.
Why does this happen?
Hours were never agreed
A project agreed as 'whenever I have time' has no schedule. Your app competes with every other client and falls to the bottom when someone else shouts louder.
One person is the whole team
A single developer cannot also be a backup for themselves. Holidays, illness and a busy week all stop your app.
Urgent and planned work are treated the same
A crash that costs you customers and a new feature idea sit in the same queue. Nobody has agreed which kinds of issue jump the line.
Knowledge lives in one head
If the setup is not written down and the accounts are in the developer's name, no one else can step in quickly, even for a small fix.
What can I do about it today?
- List what must never waitFor example: the app will not open, payments fail, customers cannot log in. These are the problems you want answered fast. Everything else can be planned.
- Ask for fixed days and a stated way to reach themAgree on which days your app gets attention and how to flag something urgent, in writing.
- Ask where the code and accounts areThe repository, store accounts, servers and domain should have a company owner you control, so help can start without waiting for one person.
- Get a named second person for emergenciesIt can be another engineer you pay only when needed. What matters is that they can read the code and know where things are.
- Check whether the work, as it is, even needs a full-time personMany live apps need steady care in small amounts, not a full-time developer. Decide from the list of tasks, not from the number of hours.
When should I bring someone in?
- A live problem has waited for days with no reply.
- Your developer is the only person with access to the code or accounts.
- You want a steady, agreed amount of attention without hiring full time.
How do I handle it?
- Learn the app and list the routine workI read the code and the setup and write down what normally needs doing: updates, fixes, store releases and monitoring.
- Agree the hours and the urgent path in writingA regular amount of time each month and a clear way to flag urgent issues, so nothing depends on goodwill.
- Write the setup downWhere the code, accounts, servers and keys are, and how to release an update, so a second person can step in.
- Work alongside your current developer if you wishI can be the backup and the reviewer without replacing anyone, or take over fully if you decide to change.
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?
Is part time always a problem?
No. It works when the hours, the urgent path and a backup person are agreed. The trouble starts when none of them are.
Do I need a full-time developer instead?
Often not. A live app usually needs steady care in small amounts. I help you work out from the task list whether full time is justified.
Can you be the backup without taking over?
Yes. I can read the code, keep notes and be ready for urgent fixes while your current developer continues the main work.
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.