Simple, Transparent Pricing

We typically need a build (APK/AAB or Play Console internal testing link), a short list of the critical flows you want validated (e.g. login/onboarding/payments/push), and any setup notes. If test accounts are required, we recommend test-only accounts with least-privilege access.

Most test runs are completed within 24–72 hours depending on device coverage and scope. If you have an urgent release, select ASAP in the request form and we’ll confirm the fastest available turnaround.

Yes. We work with Australian and international teams remotely. You can provide builds via secure link or Play Console internal testing, and we deliver results and artefacts digitally.

Yes. We can run smoke and regression suites on real devices as on-demand runs or scheduled bundles. If you already have automation (e.g. Appium), we can execute it on physical devices and return artefacts and reporting aligned to your workflow.

Yes. We support Australian and international teams remotely. You can provide builds via secure link or Play Console internal testing, and we deliver reports and artefacts digitally.

Release Validation typically includes install/upgrade checks, critical flow validation, UI compatibility observations, stability checks (crash/ANR observation), and a concise report with findings, repro steps and recommendations. Device coverage depends on the chosen scope.

We prefer test-only accounts and least-privilege access. Credentials are used only for the requested testing scope. If you have specific security requirements (restricted accounts, IP allowlists, etc.), tell us and we’ll align the approach.

We test on real Android devices, with Samsung Galaxy as primary coverage. If you need a specific model or Android version, request it and we’ll confirm availability and recommend a device matrix aligned to your user base.

Subscriptions reserve physical Android devices for your use each month. They’re ideal for teams shipping frequently or running continuous testing. You can scale device count up or down and combine subscriptions with on-demand runs for release peaks.

No long-term lock-in is required for one-off packs. Subscriptions are billed monthly. If you need reserved capacity, custom device coverage, or enterprise terms, we can structure that on request.

You receive a pass/fail summary, device/OS coverage matrix, findings prioritised by severity/impact, reproduction steps, and supporting artefacts (screenshots/logs) where applicable—written for fast engineering triage.

Yes. If you provide the device model, Android version, and repro steps, we’ll attempt reproduction on our available devices and report results. If the exact model isn’t available, we’ll recommend the closest equivalents.

We’ll recommend a cost-effective mix of subscriptions (reserved devices) plus scheduled automation runs to match your release cadence and reduce release risk.