We hear it often: "I have an app, but whoever built it is gone," "I can't update it," or "one day it just stopped working." The good news is that you do not always have to throw it away and start from scratch; often it can be rescued. Here is how we see it, with no empty promises.
The first step is always an honest diagnosis. Before promising anything, we have to see what is really there: the source code, the accounts (stores, servers, domains), what technology it is built with and how out of date it is. Sometimes the biggest problem is not the code but that no one has the access. That diagnosis is cheap and tells you the truth before you spend on the fix.
What we usually find: old dependencies that no longer compile, services or keys that are down, the app pulled from the store for not meeting Apple's or Google's new requirements, or a developer who left without handing over access. Almost everything can be fixed; what drives the cost is how much was documented at the time and how much was lost.
Then comes the key decision: rescue or rewrite. If the foundation is healthy, we update it, stabilize it and recover control — and that costs less than starting over. If the foundation is rotten or there simply is no code, sometimes rewriting the core is more worthwhile. The honest thing is to tell you which one makes sense, with numbers, not push you toward the more expensive option.
Recovering control matters as much as the code. The App Store and Google Play accounts, the domain, the server and the backups should be in YOUR name, not that of a third party who can leave again. An app without its own access is an app that will be abandoned again the moment there is a problem.
If you have a stalled app or a developer who disappeared, tell us what happened and what access you still have. We start with the diagnosis and tell you clearly whether it can be rescued or should be rebuilt, and what each path costs. Write to us through the contact form or on WhatsApp and a real team in Quito answers.