Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app is half built and I need to know what it will take to finish

Short answer

A finish estimate starts with a review of what exists, not a guess. A developer reads the code, runs the app, lists what works, what is broken and what was never started, then writes the remaining work as a scope. Gather your access, designs and notes first so the review can start.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The first developer stopped, ran out of budget or went quiet and the app is not finished.
  • I can see screens, but I do not know what actually works behind them.
  • Each new developer says the work has to start again from zero.
  • I have been given a date to launch and no one can tell me what is left.
  • I do not know whether the code I paid for is worth keeping.

Why does this happen?

  1. Nobody wrote down what was done

    Many half-built apps have no list of finished and unfinished features. Screens that look complete can still have no working logic behind them, so a quick glance gives a wrong picture.

  2. The code may be fine or may be hard to continue

    Whether to continue or rebuild depends on how the existing code is organised, whether it runs, and whether you can get it. A review of the code gives that answer, an opinion from a screenshot does not.

  3. Access is scattered

    The code, the server, the store accounts and the design files are often held by different people. An estimate cannot be written until someone can open them.

What can I do about it today?

  1. Collect everything you haveDesigns, the original brief, chat history, invoices, test builds and any login details for the code repository, hosting and store accounts. Share only what you control.
  2. Write down what the app must do at launchA plain list of the things a customer must be able to do, in order of importance. Separate must-have from nice-to-have.
  3. Ask the previous developer for a handoverAsk politely, in writing, for the source code and a list of what is finished. Keep the reply.
  4. Do not pay for a rebuild before a reviewAsk any new developer whether they have run and read the existing code. If they quote without seeing it, treat the number as a guess.
  5. Do not share passwords in chatAdd people as users to your repository, hosting or store account instead, so you can remove them later.

When should I bring someone in?

  • The previous developer will not hand over the code or does not answer.
  • A launch date, investor or customer is waiting on the app.
  • Two developers have given very different answers about what is left.

How do I handle it?

  1. Review before any numberI get read access, run the app, and walk through each feature. I mark every item as working, partly working, broken or not started.
  2. Decide: continue or rebuildI tell you in writing whether the existing code can be built on, and why. Continuing is not assumed.
  3. Write the remaining work as a scopeA list of what is left, in the order that gets you to a launchable app first, with the risks named.
  4. Agree the first sliceThe first piece of work is small and testable, so you see real progress before committing to the rest.
  5. Keep it yoursThe code lives in a repository your company owns, from the first day.

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 you give me a number without seeing the code?

No. Without reading the code and running the app, any number is a guess. A short review comes first.

Will you rebuild everything?

Not by default. I assess whether the existing code can be continued and tell you the reason either way.

What if the first developer will not give me the code?

Then the review starts from what exists in the store, on the server and in your records. I say plainly what that allows. If ownership is in dispute, speak to a lawyer.

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.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.