Mobile release confidence without more QA headcount
Every release checked. Your team’s time back.
mini runs the full regression on every release candidate. Your team decides what ships.
2 days → 1 hourWeekly releases, from fortnightlyFrom a pilot customer
What changes for your team.
The full regression, every release.
iOS, Android and web in parallel; about an hour, paced by your plan.
Coverage without hiring for it.
mini writes and maintains the tests. No automation engineer per squad.
Your gate, your call.
Checks inform by default. You choose when a failure blocks a release.
Findings your team can act on.
The recording, failed criterion and fix prompt, in the PR and Slack.
The questions before a pilot.
What it costs
Sized by full suites a month and devices and browsers at once. Our failures aren’t billed. A pilot comes first.
See pricingWhat your team does
Share a build or repo, add test accounts and review what mini finds.
How the regression runsWhat security will ask
What leaves your environment and to which model providers, EU or US hosting, SSO and SCIM on Enterprise, SOC 2 audit in progress.
Security and enterprise
Teams that ship with mini.
“For the first time, I ran a pilot without a single technical bug. Testing my native iOS and Android apps in real conditions let me catch bugs upstream. Minitap saves me time and gives me confidence in every release.”
Sandra KhirecheFounder, Impakt- 48 hoursTo full coverage
From a pilot customer.
Helmit
Memrise
Nanogram
Impakt
Trippin
MindStash
Clutch
Good questions.
Who decides what ships?
Your team. mini’s check on a pull request informs by default, and you choose when a failing run blocks the merge. In a release pipeline, the GitHub Action can wait for the run and hold the deploy until it passes.
Will it need babysitting?
Less than a script suite. mini reads the screen rather than element IDs, keeps the tests current as the product changes, and lists every change it makes. Your team reviews what mini finds. When your team marks a finding Not a bug, mini puts the note to use on the next run.
How does it fit our pipeline?
GitHub is native: a comment on every pull request to your main or release branches, a check on every run, and a GitHub Action for release runs. Any other CI starts runs and reads the verdict through the minitest CLI. Findings also land in Slack.
Does it cover the flows that cause escapes?
Yes. One test can drive up to three iOS or Android devices, like a buyer and a seller, and go out of the app and back for email codes, magic links and deep links. mini can also mock a location, and cut the network mid-run on Android and the web.
How soon do we see results?
Once mini has a build and test accounts, it explores the app, writes its first tests and runs them, and we go through the first report with your team. One pilot customer had full coverage in 48 hours.
Does mini replace our QA team?
No. mini takes the repeat work of writing, running and updating the regression suite. Your QA team keeps the judgement on what counts as a bug and what ships, and gets its time back for exploratory testing and new features.For QA teams
What can’t mini test?
Face ID and fingerprint, NFC, Bluetooth, real SMS and calls, real payments, tablets, watches and TV. Payments run in the store’s sandbox or with a test card.
Scope a pilot on your next release.
Bring a build. We agree what a pilot measures on one release.