Mobile app testing services
Mobile app testing services for iOS and Android: manual testing on real phones and tablets, automation in Appium, Espresso, XCUITest and Maestro, runs on device farms, testing of React Native, Flutter and .NET MAUI apps, and release checks before store submission, with dedicated mobile QA engineers for your team or mobile testing projects delivered end to end.
Mobile testing we do
Testing on real phones and tablets
Manual and exploratory testing on the iPhones, iPads and Android devices your analytics show customers use, across OS versions, screen sizes and manufacturers, with each defect filed with the device, the build and a screen recording.
Appium automation
Cross-platform suites in Appium with the UiAutomator2 and XCUITest drivers, written in Java, TypeScript, Python or C#, for one suite across both platforms or for testing a built app without its source code.
Native UI tests in Espresso and XCUITest
Fast, stable tests kept in the app’s own repository: Espresso and Compose UI tests for Android and XCUITest for iOS, run by the build on every pull request.
Device farm runs
Suites run in parallel on real devices in BrowserStack, Sauce Labs, TestMu AI (formerly LambdaTest), AWS Device Farm or Google Cloud’s Developer Device Platform, the successor to Firebase Test Lab, with logs and video for every device.
React Native, Flutter and .NET MAUI apps
Cross-platform apps tested with Detox for React Native, Flutter’s integration tests, Appium for .NET MAUI or Maestro flows written in YAML, together with the native modules and platform differences each framework leaves to you.
Interruptions, networks and battery
Calls, notifications, backgrounding, rotation, low storage and permission changes in the middle of a flow, slow and dropped connections simulated with network conditioning, and battery and memory use measured in Xcode Instruments and the Android Studio profilers.
Push, deep links and in-app purchases
Push and in-app messages, universal links and Android App Links, subscriptions and in-app purchases in the App Store and Google Play sandboxes, and Apple Pay and Google Pay through the payment provider’s test mode.
Release and store readiness
Builds distributed through TestFlight and Google Play testing tracks, checked against Apple’s App Review Guidelines and Google Play policies before submission, and upgrades from older app versions tested so existing users keep their data.
Privacy and permission checks
Data stored on the device, permission prompts, Apple privacy manifests and Google Play data safety answers checked against what the app actually does, with deeper security testing against the OWASP MASVS when you need it.
Hire mobile QA engineers
Dedicated mobile QA engineers
Mobile QA engineers who join your team full time, work in your tools and process, and report to your lead. You interview them; we carry the Ukrainian contract, payroll, invoicing and leave.
Mobile app testing projects
A defined piece of mobile app testing with a scope, a fixed plan and a named lead on our side who owns the result and reports progress in your channels.
Ongoing mobile app testing
Mobile app testing as a continuing service: the same people every month, a backlog you prioritise, and hours you can see in our portal and on the invoice.
The dedicated team page explains how specialists join your team, and the outsourcing page covers project delivery, take-overs and how we charge.
Who works on your mobile app testing
Mobile QA engineers
Device testing, test design and release checks
Mobile test automation engineers
Appium, Espresso, XCUITest and Maestro suites
iOS and Android developers
Testability hooks and native UI tests
DevOps engineers
Mobile CI, code signing and device farm runs
How we test mobile apps
The device list comes from your analytics: the models and OS versions that carry most of your users are tested by hand on real hardware, and the long tail runs on a device farm. Emulators and simulators give fast feedback during development, but a release is signed off on real devices.
Automated suites run in the mobile pipeline, on GitHub Actions with macOS runners, Bitrise, Codemagic or Xcode Cloud, so every build that reaches testers has passed them. Each release ends with a checklist covering upgrades from the previous version, store metadata and the flows that earn money, followed by a staged rollout watched in Crashlytics or Sentry.
Other software testing services
Manual testing
Manual testing services: functional, regression and exploratory testing, test case design, cross-browser and cross-device testing and UAT support, with dedicated manual QA engineers or project delivery.
Test automation
Test automation services: Playwright, Selenium, Cypress and WebdriverIO suites, SDET work, API and visual tests, and CI integration, with dedicated test automation engineers or project delivery.
API testing
API testing services: REST, GraphQL and gRPC tests in Postman, REST Assured and code, contract testing with Pact, OpenAPI validation and service mocks, with dedicated API test engineers or project delivery.
Performance testing
Performance and load testing services: load, stress and soak tests in k6, JMeter, Gatling and Locust, bottleneck analysis, capacity planning and Core Web Vitals, with dedicated performance engineers or project delivery.
Accessibility testing
Accessibility testing services: WCAG 2.2 audits, screen reader and keyboard testing, axe checks in CI, remediation support and conformance reports, with dedicated accessibility testers or project delivery.
Questions about mobile app testing
Which industries do your mobile QA engineers work in?
Mostly fintech and banking apps, where sign-in, payments and card controls are tested on every release; e-commerce and retail apps with catalogues, carts and loyalty schemes; media, streaming and consumer apps used on a wide range of devices; healthcare and fitness apps that read sensors and health data; and companion apps for connected devices, tested with the hardware they control.
How many devices do you test on?
As many as your users need. A typical matrix covers the current and previous major iOS versions, the Android versions and manufacturers behind most of your installs, a small phone, a large phone and a tablet. The matrix is written down and reviewed as your analytics change.
Do you need our source code to test the app?
Not for manual testing or Appium suites, which need only a build from TestFlight or a Google Play testing track. Espresso and XCUITest suites live in the app’s repository, so for those our engineers work in your code.
How quickly can mobile QA engineers start?
When the right mobile QA engineer is available, the start is gated only by your interview and the NDA and IP assignment. Otherwise we run a search, which typically produces candidate profiles within two to three weeks, and nobody starts until you have said yes.
How do we hire mobile QA engineers through BigTree108?
Tell us the work, the seniority and the hours you need. We propose one or two people with their profiles, you interview them the way you would interview your own hire, and you sign one agreement with BIG TREE 108 LLC and receive one invoice a month.
Who owns the work they produce?
You do. Every specialist has a signed contract with BigTree108 that assigns all work product to the company, and our agreement with you assigns it onward. Code, designs and documents are delivered into your own repositories and tools, not kept where only we can change them.
Releasing a mobile app?
Tell us the platforms, how the app is built and distributed, and which devices your users have. You get an answer within one business day: a device matrix and test plan, candidate profiles, or a scope for automation.