Service · Audit & fixes
Audits & fixes for apps already in use.
Is the app slow, a source of complaints, or something your team is afraid to change? We review the user flows, speed, accessibility, basic security and code, then rank the fixes by impact. We can carry out the fixes too, if you want.
The situation
The app is in use, but something is wrong: parents get confused when signing up, pages are slow on phones, errors appear for no clear reason, or the team is afraid to change the code in case it breaks something else.
Rewriting from scratch is rarely the right first answer. It is usually cheaper to find the few points with the most impact and fix those first.
Is it a fit?
A good fit for
- Web, PWA or Flutter apps that already have users
- Teams that have lost their original developer and need to understand inherited code
- Products about to grow that want to know whether the foundations are solid
- Organisations that hold data on children or parents and want to know the basic gaps
Not a good fit for
- You need a certified penetration test or a formal compliance audit
- Nobody uses the app yet: start with consulting or development
- There is no access to the source code or a test environment
What you get
- Written findings, with examples from your own product
- Measurements of page speed and size on phones, before and after the fixes
- An accessibility and basic security review
- A list of fixes ranked by impact and effort
- Fixes carried out directly, if agreed
How it works
Access and scope
We agree which parts to review and what access is needed: code, a test environment or test accounts.
Review
The user flows are tried on real phones, speed is measured and the code is read.
Report and priorities
You receive written findings and a list of fixes ranked by impact and effort.
Fixes, if agreed
We work through the fixes in order, with before and after numbers for every change.
What you own at the end
- A report any team can act on, not only us
- Before and after numbers for every fix we make
- Automated tests added during the fixes, so the same problems do not come back
Cost and time
The figure below is for a small app; the final cost is written down once we have seen the size of the app and agreed which parts to review. Fixes are estimated separately, from the list of findings.
- From
- IDR 10 million
- Estimated time
- 1–2 weeks
Common questions
Do we have to give access to the code?
For a code audit, yes. Without code access we can still review the user flows, speed and accessibility from the outside; the scope is written into the proposal.
Will the app be disrupted during the audit?
Reviews take place in a test environment, or in ways that do not change user data.
Can you audit Flutter apps?
Yes, as well as web apps and PWAs.
What if it turns out to need a rewrite?
We tell you plainly, with the reasons and a staged option that does not stop the app that is already running.