I will automate manual UI and feature testing for your mobile app
About this Gig
Manual mobile QA does not scale. Every build, someone taps through onboarding, login, payments and settings on a couple of devices, and the bug still ships on the one screen nobody checked.
I set up Maestro so that entire pass runs on its own. Not unit tests. Real screens, real taps.
Maestro drives your real release build at the UI layer. No code changes, no special test build, no instrumentation. Flows are plain YAML your team can read and edit without learning a test framework.
What you get:
- Your real user journeys as Maestro flows: onboarding, auth, payments, deep links, offline states
- Works with native iOS, native Android, React Native, Flutter and hybrid apps
- Runs on real Android devices, emulators and iOS simulators
- Screen recordings and screenshots of every run, so you watch the failure instead of reading a log
- Reusable subflows for login and setup, so the suite stays maintainable
- CI wiring for GitHub Actions, GitLab, Bitrise or Codemagic
Note on real iPhones: Maestro officially supports iOS simulators. Real iOS hardware needs a device cloud, which I will set up if you want it.
Send me your build and I will tell you what is worth automating first.
Testing application:
Mobile app
Device:
PC
•
iPhone
•
iPad
•
Android mobile phone
•
Android tablet
FAQ
Do you need access to our production environment?
No. Staging or a local build is better, and safer. If you only have production, I use a dedicated test account and read-only flows, agreed with you in writing first.
What if our app has no test IDs?
Common, especially in AI-generated code. I use role, label and text-based locators that survive refactors, and where a screen genuinely needs test IDs I add them as a small, reviewable PR.
Who owns the tests?
You do, entirely. Plain Playwright and Maestro in your repo. No platform subscription, nothing that stops working if you stop working with me.
What happens when a test fails in CI?
You get the recording, the screenshots and the full trace attached to the run. You watch the failure instead of guessing at a stack trace.
Can you test on real iPhones?
Maestro supports iOS simulators; real iPhone hardware needs a device cloud, which I can set up. The cloud subscription is billed to you directly. Real Android devices work without any of that.
Will these tests catch every bug?
No, and anyone promising that is selling you something. UI tests catch regressions in flows you've decided matter. I'll tell you upfront which risks the suite covers and which it doesn't.
Will you sign an NDA?
Yes, before I look at anything.

