Mobile app testing services on real iPhones and Android phones
Our mobile app testing services check your app the way your users and the app stores will: on real iPhones and Android phones, on a weak network, with large text and a screen reader, through sign-in, payment and every flow that matters. You get clear bug reports, a store-readiness check before you submit, and automated tests for the core flows that stay in your repository. The team that tests your app also builds and runs its own apps on the App Store.
- Fixed price, agreed before work starts
- A one-off job with no follow-on contract
- Logins stay in your company's name
What we test
- Functional testing. Every screen and flow against what the app should do, including the edge cases: empty states, wrong input, expired sessions, a phone that goes offline halfway through a payment.
- Device and OS coverage. Real devices across the iOS and Android versions you support, small and large screens, notched and foldable phones, light and dark mode.
- Store readiness. A review against Apple's App Review Guidelines and Google Play's policies before you submit: metadata, privacy labels, demo accounts, permission prompts, subscriptions and the reasons apps are most often sent back.
- Accessibility. VoiceOver and TalkBack, dynamic text sizes, contrast, touch target sizes and order of focus, checked against WCAG 2.2.
- Payments and subscriptions. In-app purchases and subscriptions in the store sandboxes: buy, restore, upgrade, cancel, renew and refund, plus what the app shows in each state.
- Network and performance. Slow and lost connections, start-up time, memory, battery and data use, and what happens when the server is slow.
- Notifications, links and widgets. Push notifications in every app state, deep links and universal links, widgets and Live Activities where the app has them.
- Security basics. What the app stores on the device, what it sends over the network, and how it handles sign-in, checked against the OWASP MASVS.
- Localisation. Every language the app ships in: truncated text, date and number formats, right-to-left layouts where they apply.
The store rules testing has to cover
A good share of app testing is about the stores, not the code. Apps that work can still be rejected, and a rejection costs days. The rules that shape our test plans most often are these (all read on 11 November 2026):
- Apple App Review. Guideline 2.1 of the App Review Guidelines asks for final versions with all metadata and working links, apps tested on-device for bugs and stability before submission, and an active demo account or a full demo mode when the app has sign-in. Our store-readiness check goes through those points one by one.
- TestFlight. Apple's TestFlight page states that you can add up to 100 internal testers from your team and invite up to 10,000 external testers, and that the first build for external testers must be approved by App Review. We use internal testing for our own rounds and external groups for your pilot users.
- Google Play closed testing. Google Play requires personal Play Console accounts created after 13 November 2023 to run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before applying for production access. Organisation accounts are not bound by that rule, but a closed test before launch is still the right step.
- Accessibility law. The European Accessibility Act, Directive (EU) 2019/882, applies to services provided to consumers after 28 June 2025, among them e-commerce, consumer banking and air, bus, rail and waterborne passenger transport, and for transport it names mobile applications explicitly. The W3C published WCAG 2.2 as a Recommendation on 5 October 2023 (current version 12 December 2024), and it is the practical yardstick for app accessibility testing.
Manual testing and automated testing
Both are needed, for different jobs. The mistake is to rely on only one.
| Manual testing | Automated testing | |
|---|---|---|
| Best at | New features, usability, visual problems, store readiness, accessibility with real assistive technology | Flows that must work in every release: sign-in, purchase, the core task |
| When it runs | Before each release and after larger changes | On every build, automatically |
| Typical tools | Real devices, screen recording, the store sandboxes | XCUITest on iOS, Espresso or UI Automator on Android, cross-platform tools such as Maestro or Appium |
| What it finds | What nobody thought to script | What a change broke without anyone noticing |
We start with manual and exploratory testing, because that is where the important bugs are found in a young app. As the app settles, the flows that break most often or cost most when they break become automated tests in your continuous integration, so every build is checked before a person ever opens it.
How a test round runs
- Test plan. What the app should do, who uses it, which devices and OS versions, which flows are critical and what counts as a release blocker. One page, approved by you.
- Test build. You share a build through TestFlight or a Google Play testing track, with test accounts and any sample data the flows need.
- Testing. Functional, device, accessibility and store-readiness passes, in the order the plan sets. Blockers are reported as soon as they are found.
- Report. Every bug with steps, expected and actual result, device, OS version, recording and severity, in your issue tracker. A summary says whether the build is ready to submit.
- Retest. When fixes arrive in a new build, we check them and run the core flows again, because fixes break things too.
Testing before launch, and after
Before a first launch, the most valuable work is a full pass plus a store-readiness review, and for a new personal Google Play account, the closed test that production access needs. After launch, testing becomes a rhythm: a regression pass before each release, a check of every new iOS and Android version in beta before it reaches your users, and a look at crash reports and store reviews, which often point at a device or a flow the plan missed. Apple and Google raise their minimum requirements every year, so an app that is not tested against the new versions in beta finds out in production.
Proven on our own apps
We test the same way for our own products. Every app we publish goes through internal TestFlight, a real-device pass and a store-readiness review before it is submitted, and the same checklist is the one we use for clients. You can see the apps on our apps page. If you also need the app built or rebuilt, see app development, iPhone app development, Android app development and cross-platform app development.
You own it
Test plans, bug reports and automated tests are written in your company's tracker and repository from the first day. Test accounts are created in your store accounts, and our access is removed when the work ends. Any team can keep running the regression suite after us. For a deeper look at the app's security and the backend behind it, add a security audit. For where testing sits among the other steps, see the mobile app development process. For web applications, APIs and back-office systems, see software testing outsourcing, and for updates after launch, mobile app maintenance services. See prices.
Questions we get
Can you test an app another team built?
Yes. We need a test build through TestFlight or a Google Play testing track, test accounts and a short description of what the app should do. We do not need the source code for most testing, though access to it helps when we write automated tests.
Which devices do you test on?
On real iPhones and Android phones chosen from your own analytics or, for a new app, from the devices common in your market: the oldest supported iOS version, the newest one, a small and a large screen, and Android phones from more than one manufacturer. Emulators add coverage for screen sizes, not instead of real devices.
Do you only test manually?
No. Exploratory and store-readiness testing are manual, because that is where people find what a script cannot. Flows that must work in every release, such as sign-in, purchase and the core task, become automated tests that run on every build.
How do you report bugs?
Each bug has steps to reproduce, the expected and actual result, the device and OS version, a screen recording and a severity. Reports go into your issue tracker, or into one we set up in your account.
Can you help us pass Google Play's testing requirement?
Yes. New personal Play Console accounts must run a closed test with at least 12 opted-in testers for 14 days in a row before applying for production access. We plan that test, run it with a structured test plan and help you answer Google's questions about it.
Who owns the test plans and automated tests?
Your company. Test plans, bug reports and the automated test code sit in your own repository and tracker, so any team can keep running them.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.