Should you rebuild your app or fix the one you have?

The access problem decides it fastest

Before assessing any code, answer this: do you control the Apple and Google developer accounts, the source code repository, and the backend? In your business name, with credentials you hold?

If the answer is no, the condition of the app is close to irrelevant. You cannot ship an update, respond to a store policy change, or move to another developer. That is not a technical problem, it is an ownership problem, and it usually forces a rebuild regardless of how good the code is.

Establish this before spending money on an assessment.

Fix it when the app fundamentally works

Repair is the right call more often than rebuild, and it is much cheaper.

• It is slow or crashes on some devices — usually diagnosable and fixable.
• It looks dated. Interface refreshes rarely require new foundations.
• It is missing features. Adding to a sound codebase is ordinary work.
• It broke after an OS update. Normally a maintenance job, not a rebuild.

Rebuild when the foundation is wrong

• The framework it was built on is abandoned or no longer supported. Every future change fights the tooling.
• It was built native and should have been a progressive web app. Two codebases and store reviews for something that never needed either is a permanent cost.
• It cannot be updated safely because nobody understands it and there are no tests.
• The backend it depends on is gone or unmaintainable.

The question to ask first

Before either path: is the app used? Check actual active users, not downloads. If usage is negligible, neither fixing nor rebuilding solves your problem — the problem is that nobody wanted the app, and more engineering will not change that.

That is a harder conversation than a rebuild quote, and it is the one that saves the most money.

Common questions

Our developer disappeared and we cannot access our app. What now?

Try to recover the developer accounts through Apple and Google support first — that is worth real effort, since recovering them can save the entire rebuild. If recovery fails you will need to rebuild and republish, and you should treat account ownership as a contract term next time.

How much of an existing app can be reused in a rebuild?

Often the design and the backend, rarely the app code itself. If a rebuild is genuinely needed the code is usually the part that has to go, while the data and the interface work survive.