Help for owners
My developer keeps missing deadlines and my app is months late
Short answer
Repeated missed dates usually mean the work is not broken into small, checkable pieces, so nobody can see real progress. Ask for a working build you can open on your phone this week, a short list of what is done and what is left, and confirm you own the code and accounts before deciding anything else.
Does this sound like your situation?
- Every date my developer gives me moves, and the reason is always different.
- I have not seen the app running on a real phone for weeks.
- Each update says 'almost done' but I cannot tell what is finished.
- New costs or new extra work keep appearing near every deadline.
- I do not know if the code is safe in a place I control.
Why does this happen?
The work was never cut into small, checkable pieces
A plan such as 'build the app in three months' hides the real state. Without a list of small deliverables that each end with something you can open and try, a project can look fine until the last week.
The scope grew without anyone writing it down
Each small request sounds quick, but together they move the finish line. If changes are not written next to the date they affect, the original date stays in everyone's mind while the work behind it has changed.
The developer is stuck on something hard and has not said so
Some problems, such as an integration that does not behave, a store requirement or a performance issue, take far longer than first estimated. A developer who is embarrassed may stay quiet instead of asking for help.
Too many projects share one person
A freelancer or small agency with several clients can only give your app the days left over. Delays then have nothing to do with how difficult your app is.
What can I do about it today?
- Ask for a working build this weekNot a screenshot or a video: an installable test version or a test web link you open yourself. What runs today is the only honest measure of progress.
- Ask for a one-page list of done, in progress and leftPlain language, one line per feature. Compare it with the original agreement and mark what changed since.
- Write down every date that was promised and missedKeep the messages. A short factual timeline helps whether you stay with this developer, renegotiate or leave.
- Check who owns the code and the accountsAsk where the source code lives and make sure your own company is an owner of that repository, the store accounts and the domain. You do not need to ask this in an angry way.
- Do not stop paying out of frustration or sign a new contract in a hurryHold payments to what your agreement says, but do not threaten to stop everything before you have a copy of the code. Take stock first, then decide.
When should I bring someone in?
- You cannot get a working build or a straight list of what is left after asking twice.
- The code or the store accounts are not in your company's name.
- You need a neutral technical opinion on how much is really left before you decide to stay or leave.
How do I handle it?
- Read the code and run the appI get a build running and compare what exists with what was agreed, so you get a plain list of done, half done and not started.
- Estimate what is left in small piecesEach piece is small enough to check, with the risks written beside it. I say so when something cannot be estimated yet.
- Secure the code and accounts firstBefore any change of plan, I help you get the repository, store accounts and servers under your company's name.
- Give you options, not pressureYour choices are to finish with the current developer under a clearer plan, to share the work, or to hand it over. I write down each with its trade-offs and you decide.
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?
Should I fire my developer now?
Not before you hold a copy of the code and the accounts. First get a working build and an honest list of what is left. After that the decision rests on facts, not on frustration.
Can you take over a half-built app?
I read the code first and tell you what is solid and what is not. Whether to continue with it or rebuild parts is decided after that review, not before.
Is a delay always the developer's fault?
No. Changes in scope, late feedback or a slow third party also move dates. That is why I compare the original agreement with what was asked later.
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.