I want to run Selenium-based automated web tests not just on desktop browsers but on real mobile devices (Android and iOS). Instead of emulators or simulators, I want access to physical phones in the cloud so I can catch device-specific browser issues (rendering, touch behaviors, layout quirks).
My key requirements:
-
Real device cloud (not just VMs)
-
Support for Selenium WebDriver
-
Good variety of mobile browsers + device-OS combos
-
Ability to run in parallel (CI integration)
-
Debugging support (logs, screenshots, video)
Which tools or platforms are commonly used / most reliable for this setup? Preferably ones that are mature and stable.
If I were building the automation grid, I’d strongly consider LambdaTest and BrowserStack:LambdaTest: Their automation cloud supports Selenium on 3,000+ real desktop & mobile browsers.
Their Real Device Cloud supports 10,000+ real Android and iOS devices.
They also allow parallel execution, network throttling, and detailed logs to debug Selenium runs.
On the QA side, I’ve seen Kobiton work really well:
Kobiton
Allows running Selenium WebDriver-based web tests on real Android and iOS devices.
Provides a “device-in-hand” feel via remote real devices, plus detailed logs, video, and screenshots for test diagnostics.
Also has good CI integration, so you can plug in your Selenium tests into your pipeline easily.
If you want high-fidelity real-device testing, Perfecto and Kobiton are great QA-friendly options.
From a leadership / strategy perspective: here are some of the top picks to run Selenium on real devices, along with when to pick what:
LambdaTest → Best for scalability + cost efficiency + device coverage. Because they have 10k+ real devices, you can run broad Selenium tests without owning the hardware.
Kobiton → Lightweight but powerful; good when you want real-device test execution without overpaying on very big device farms.
Pro tip: Make sure to align the device cloud with your Selenium grid strategy , run your most critical or flaky device/browser combos on real devices, and less risky tests on VMs or emulators. That way, you optimize your budget and get the reliability where it matters.