Existing web apps · Next.js and Supabase · UK businesses

Find out what's
going wrong.
Then plan the repair.

Edits disappear. Two people see different records. An app works for one user but gets unreliable when the team uses it together.

I'm Nick. I review the affected code and data handling, then explain what the evidence supports. A description of the symptoms is a starting point, not a diagnosis.

Ask about an app review

I'll normally reply within 24 hours. Don't send passwords or customer records with your enquiry.

One agreed area, £450 total

The review takes five working days after we agree the scope and access is ready. NRB is not VAT-registered, so no VAT is added. A large codebase or several unrelated faults needs a separate scope.

Review the code and schema involved in the reported problem.
Inspect relevant Supabase row-level access and storage rules where they're part of the agreed scope.
Investigate how concurrent or offline changes behave, where relevant and reproducible.
Write down the findings, unresolved questions and a priority-ordered repair plan with indicative effort estimates.
Provide a handover written for the person who will maintain the app.

You keep the report whether or not you ask me to do the repairs. The £450 review fee is credited against a follow-on repair sprint commissioned within 60 days.

What the review doesn't promise

This isn't a penetration test, compliance certificate or guarantee that an app is secure. It doesn't include implementing fixes or reviewing every part of a large application.

Some faults need logs, a reproducible example or more access before the cause can be established. The report will say what's confirmed and what still needs investigation. I won't turn a guess into a fixed-price repair quote.

Start with the symptoms

Tell me what the app does, who uses it and what they see when it goes wrong. Mention the framework and database if you know them. A screenshot with personal details removed is useful.

We agree the review boundaries, payment terms and data handling before work starts. Read-only repository access, a staging environment and redacted examples are the preferred starting point. I can sign an NDA before access.

Describe the problem

Common questions

Can you fix the app after the review?

Yes, if the work fits my expertise. Repairs get a separate scope, quote and acceptance checks. A seven-day sprint is an option for bounded work, not a deadline for any fault.

What if I built the app myself?

That's fine. The handover can explain why each proposed change matters and what to watch for when you edit that area later.

Does the app need AI?

No. Data integrity, access controls and reliability are software problems whether or not the app uses AI.

Is this the right service for a website contact link?