Independent mobile QA and release assurance

Ship with confidence.

Independent iOS and Android testing for startups, agencies and software teams without an in-house QA team. Reproducible bug reports, focused regression checks, and a clear release recommendation.

You send the build. We agree the coverage, test the important journeys, and explain what needs attention before release.

20+ yearsSoftware experience
iOS + AndroidNative only — no Flutter or RN
Release reportA recommendation, not a guarantee
A phone in morning light on a pale wooden desk, beside a small olive plant.

The problem

Your app works in the demo. Is it ready for customers?

Sign-in, purchases, onboarding and upgrades deserve an independent check. Developers can cover the happy path and still miss interrupted flows, upgrades, device differences and regressions.

Code-Dash tests the agreed release journeys, writes findings your team can reproduce, and leaves the release decision with you.

Two phones on a bright windowsill, the kind of pair used for an iOS and Android check.
iOS and Android, looked at side by side.

The offer

Start with one release. Stay if you ship again.

Starting prices are illustrative GBP figures for this preview. Scope, devices and retest limits are agreed in writing before booking. VAT treatment is still to be confirmed.

Launch readiness audit

One platform, one candidate build, up to 5 key journeys and 20 agreed cases, on 2 device and OS combinations. Report, findings call, and one retest of up to 5 fixes.

from £995 Target 5 business days · up to 10 hours

See what is included

App Store submission review

One store, one version. Listing details, reviewer access and the submission questions that usually stall a release.

from £395 Target 3 business days · up to 4 hours

Compare packages

Ongoing QA

Scheduled regression for teams that release regularly, with a named monthly allowance for cycles, cases and retests.

from £499 per month · Starter, Growth, Agency

See monthly plans

How it works

Three steps. You keep the release decision.

Five business days of review is not five business days of repair in the same week. Book early enough to fix and retest.

Scope the release

Share the build, the journeys that matter, the platform and the release date.

Test and document

Receive reproducible findings with severity, evidence and the device or OS where each one showed up.

Review and retest

Prioritise fixes, use the included retest allowance, and get the final recommendation.

Proof

A labelled demonstration report, until a client one exists.

The sample is invented so you can see the format. Real case studies appear only with written permission. The default is that the company, the product, and our involvement stay between us. No invented testimonials.

Demonstration

Harbour Notes, build 2.4.1

Release recommended with conditions. One major defect on purchase restore, a blocked push check, and a written recommendation the team can act on.

Read the sample report

What a real write-up will show

Scope, one defect, what changed

The agreed coverage, a representative finding, what the team changed, and what was verified on the replacement build.

What it will not claim

Revenue saved, or a guaranteed approval

The report covers the tested build and the agreed cases. Your team decides whether to ship.

Other services

Build, automation, and AI product work are still here.

Release assurance is the front door. These remain separate offers when that is the actual job.

Build

Native iOS and Android apps, from a spec or on a codebase you already have. No Flutter, no React Native.

See the build offer

Automate

Workflow automation for an existing process, for any business. Powered by Hermes Agent.

See the automation offer

AI build

A new AI-native product or feature, built with Cursor Ultra. A different job from checking a release.

See the AI build offer

Next

Book the review before the release week, not during it.

Tell us the platform, the release date, and the journeys that matter. Builds and passwords come later, on a channel we agree.