You are taking over an application, or your own has stalled. Before committing to any development, you need to know what holds up, what has to be reworked, and what it costs.
Nobody on the team really knows what is inside it, or what taking it over will cost.
Your provider quotes estimates you have no way of judging.
You want to know what you are buying, technically, before signing.
Every new feature breaks another one somewhere else, and nobody knows why.
Readability, structure, duplication, test coverage. The real question is not whether the code is elegant, but how long it takes someone new to work in it without breaking anything.
Separation of responsibilities, dependencies, technical choices and how long they will last. A library abandoned by its maintainer is a rewrite that has not yet announced itself.
Authentication, data storage, communication with the server, secrets shipped inside the app, and how personal data is handled under GDPR.
Start-up time, smoothness, battery use, binary size. Plus everything around release: continuous integration, store publishing, monitoring, backups.
Non-disclosure agreement signed, then read access to the repository, the production accounts and any existing documentation. We agree on what you most need to know.
Reading the code, mapping the architecture, reviewing security, measuring performance on a real device. Every finding is located in the code and dated.
A written document, ranked by severity, with a prioritised roadmap and an estimate in days for the recommended work. Readable by a director as much as by a developer.
We go through the report together, with your developers if you wish. You leave with what you need to settle a budget, not only to fix lines of code.
Thirty minutes is enough to find out. Sometimes the answer is no, and I will say so.
Book a 30-minute call →