Mobile app testing for remote QA roles: Appium, native tools and real devices
By the QAAnywhere team · Published November 8, 2026
A small market with specific demands
Mobile testing is a smaller niche than web testing in remote QA hiring, but it is a distinct one, with its own tools and problems. On 8 November 2026, of the 254 remote QA roles on QAAnywhere, 9 named Appium and 7 had "mobile", "iOS" or "Android" in the title, from "QA Analyst, Mobile" to "Staff Software Engineer, Mobile QA". Among the 99 roles with a full description, 23 mentioned mobile platforms somewhere.
Two patterns stand out in those listings. Mobile skills are usually asked for alongside web automation: of the 9 Appium roles, 6 also named Selenium and 4 named Playwright or Cypress. And the two mobile QA roles that stated a salary were senior and staff engineering roles, at $186,065–218,900 and $218,025–286,500 a year: mobile quality work at that level is paid as engineering. Mobile testing is a good specialism to add to web skills rather than a separate entry route.
What makes mobile testing different
The core of testing is the same, but mobile adds problems web testers rarely meet:
- Device and OS fragmentation. Many screen sizes, Android versions and manufacturer customisations; on iOS, fewer devices but strict OS adoption timelines.
- Interruptions. Incoming calls, notifications, losing network, switching apps, low battery mode, the app being killed in the background.
- Permissions. Camera, location, notifications and contacts, each with allow, deny and "ask next time" paths.
- Install and upgrade paths. A fresh install, an upgrade from last year's version with old data, and the minimum supported OS version.
- Release cycles. App store review means a bad release cannot be fixed in minutes. That raises the cost of a missed bug and the value of good testing before release.
- Gestures and hardware. Swipes, long presses, orientation changes, biometrics and the on-screen keyboard covering inputs.
A strong mobile tester has a checklist for all of these and knows which ones matter for the app in front of them.
Appium: one API for iOS and Android
Appium is an open-source automation framework that drives native, hybrid and mobile web apps using the WebDriver protocol, the same standard behind Selenium. That is why Appium roles so often also mention Selenium: the concepts, and much of the client code, carry over.
Since Appium 2, the core server is separate from the drivers that talk to each platform. You install the ones you need:
npm install -g appium
appium driver install uiautomator2 # Android
appium driver install xcuitest # iOS (requires a Mac with Xcode)
Tests are written with a WebDriver client in the language of your choice (Java, Python, JavaScript, C# and others). Appium Inspector helps you explore the element tree of a running app and find stable locators.
Practical advice that interviewers listen for:
- Ask developers for accessibility IDs on important elements. They make locators stable across platforms and improve accessibility for real users at the same time.
- Avoid XPath for anything but a last resort; it is slow and brittle on mobile.
- Wait for conditions, not time. Mobile UIs animate; explicit waits for an element state beat fixed sleeps.
- Reset state deliberately. Decide per suite whether to reinstall the app, clear data, or keep state, and be explicit about it.
Native frameworks: Espresso, XCUITest and others
Many mobile teams, especially where developers write most of the tests, use the platform's own frameworks:
- Espresso for Android, written in Kotlin or Java, runs inside the app process and is fast and reliable.
- XCUITest for iOS, written in Swift, is Apple's UI testing framework, integrated with Xcode.
The listings reflect this: among the Appium roles, iOS was mentioned in 5 and Android in 6, and the two SDET roles with "iOS" and "Android" in their titles are platform-specific. If you want those roles, learn the native framework of the platform as well as Appium; being able to read and contribute to developers' Espresso or XCUITest code is a real advantage.
Newer tools such as Detox (for React Native apps) and Maestro (simple YAML flows for both platforms) came up in 3 of the 9 Appium roles. They are worth knowing about, and quick to learn once you understand the underlying problems.
Real devices when you work remotely
An office mobile QA team usually has a drawer of devices. Remote testers need another approach:
- Emulators and simulators for most automated runs. Android emulators and iOS simulators are fast and free, and good enough for most functional checks.
- Cloud device farms such as BrowserStack, Sauce Labs or LambdaTest for real hardware across many models and OS versions. They were named in 3 of the 9 Appium roles. Know how to run a suite against one and how to read its videos and logs.
- A small personal set of devices for exploratory testing: ideally one recent iPhone, one recent mid-range Android and one older, slower Android. Many companies will ship test devices to remote testers; ask during the offer stage.
Note that iOS automation needs a Mac. If you are building mobile skills at home on Windows or Linux, start with Android and use a cloud service for iOS.
Exploratory testing still finds the worst bugs
Automation catches regressions; exploratory sessions catch the problems nobody wrote a test for. On mobile that means using the app the way people really do: on a train with patchy signal, with the system font size turned up, with dark mode, in another language, half way through a payment when a call comes in. Write short session notes with what you tried and what you found. Remote teams value them because they make your work visible.
Building a mobile testing portfolio
- Automate a few flows of an open-source Android app with Appium, run them in CI on an emulator, and publish the repository with a clear README.
- Add an exploratory testing report for the same app: a page of findings with screenshots and device details.
- On your CV, name platforms, frameworks and devices precisely ("Appium with Java on Android 12–15; XCUITest for iOS smoke tests; BrowserStack for device coverage").
The roles below are open now and name Appium. Each listing shows where you can work from, so check that before applying.