Mobile App Technical Audit

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.

Duration 4 to 8 days
Rate €750 per day
Deliverable Written report and workshop
Who it is for

Four recurring situations

A

You have inherited an application

Nobody on the team really knows what is inside it, or what taking it over will cost.

B

Delivery timelines keep slipping

Your provider quotes estimates you have no way of judging.

C

You are considering an acquisition

You want to know what you are buying, technically, before signing.

D

Everything keeps breaking

Every new feature breaks another one somewhere else, and nobody knows why.

Scope

What I look at

The code

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.

ReadabilityTestsTechnical debt

The architecture

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.

DependenciesLongevityDecoupling

Security and compliance

Authentication, data storage, communication with the server, secrets shipped inside the app, and how personal data is handled under GDPR.

AuthenticationEncryptionGDPR

Performance and production

Start-up time, smoothness, battery use, binary size. Plus everything around release: continuous integration, store publishing, monitoring, backups.

CI/CDMonitoringBackups
How it runs

Four steps, a week or two

  1. 1

    Access and scoping

    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.

  2. 2

    Analysis

    Reading the code, mapping the architecture, reviewing security, measuring performance on a real device. Every finding is located in the code and dated.

  3. 3

    Report and estimates

    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.

  4. 4

    Feedback workshop

    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.

In short

The terms

Duration 4 to 8 days, depending on project size
Rate €750 per day, agreed before we start
What I need Read access to the repository, the production accounts and any existing documentation
Confidentiality Non-disclosure agreement signed before any access
Afterwards No obligation. The audit stands on its own, and the report stays useful if you hand the work to someone else.

Is an audit the right tool for you?

Thirty minutes is enough to find out. Sometimes the answer is no, and I will say so.

Book a 30-minute call →