On this page
- Should you test on cloud simulators or a physical device cloud?
- When are cloud simulators and emulators the better fit?
- Can Revyl replace a physical device cloud?
- What happens to Firebase Test Lab?
- How does the Revyl loop work?
- Beyond simulators and emulators: what else Revyl runs
- Sources
- Frequently asked questions
Use cloud iOS simulators and Android emulators for runs on every change (CI, pull requests, agent loops). Physical device clouds such as BrowserStack and Sauce Labs host real handsets for hardware checks. Revyl covers the runs on every change across web, iOS, Android and macOS. Its Free plan includes up to 1,200 free device minutes a month on iOS, Android, web and Mac, with no card and no monthly fee, 40 times Appetize Free's 30 minutes a month.
- Cloud iOS simulators
- Appetize: Yes
- Limrun: Yes
- Genymotion: No
- Revyl: Yes
- Cloud Android emulators
- Appetize: Yes
- Limrun: Yes
- Genymotion: Yes
- Revyl: Yes
- CLI
- Appetize: Yes
- Limrun: Yes
- Genymotion: Yes
- Revyl: Yes
- iOS from Linux
- Appetize: Yes
- Limrun: Yes
- Genymotion: Yes
- Revyl: Yes
YesNo
Show as a table with sourcesHide table
Scroll the table sideways to see all 3 columns.
Scroll the table sideways to see all 2 columns.
Should you test on cloud simulators or a physical device cloud?
Use real device testing when a check depends on handset hardware or wide device coverage, and cloud iOS simulators and Android emulators for scriptable runs that start from CI or from a coding agent. Revyl runs those simulators and emulators on the same platform as its web browsers and macOS computers. Apple’s own guidance draws the same line: simulated devices let you debug on hardware you might not have, and to verify that an app runs exactly as intended you run it on one or more physical devices.
Sauce Labs, TestMu AI, TestingBot and Perfecto each sell real devices and virtual devices.
When are cloud simulators and emulators the better fit?
Cloud simulators and emulators fit work that runs often and in parallel: each change, each pull request, each step of an agent loop. Google’s Android Emulator docs say that in most cases the emulator is the best option for testing. The same page says the emulator can simulate incoming calls and text messages, set the device location, simulate network speeds and simulate rotation, so several checks that sound like hardware work run on an emulator.
Some cloud simulator vendors reach into hardware-adjacent flows. Run Cloud relays a live webcam into the iOS simulator’s camera for camera-dependent apps.
Cloud simulators also take the Mac off the CI host. Limrun documents running xcodebuild, Gradle, XCTest, Maestro and Appium from an Ubuntu runner, and Genymotion’s gmsaas CLI starts Android cloud devices from a script.
Coding agents need what CI needs: a device they can start, drive and read through a tool call. Limrun documents a remote MCP server that creates and drives devices. Corellium serves a narrower case, security research on virtual iOS and Android devices with root-level access.
Revyl is built for this loop. Agents start and drive Revyl’s cloud iOS simulators and Android emulators through the CLI or MCP server, each Revyl test run produces a report, and Revyl’s Free plan includes up to 1,200 free device minutes a month on iOS, Android, web and Mac.
Can Revyl replace a physical device cloud?
For the runs on every change, yes. Revyl starts cloud iOS simulators and Android emulators from CI or an agent, runs them in parallel on each pull request, and turns each run into a report, Atlas data and, with proof of changes, a verdict on the pull request.
Checks on the handset hardware itself are the scope of a physical device cloud. Apple says simulators don’t replicate the performance or features of a physical device, and BrowserStack, TestMu AI and Kobiton list SIM, camera and biometric checks on real handsets. Those checks can run before a release while simulators and emulators cover each change. For what physical device clouds and cloud simulators cost in the same units, see device cloud pricing explained.
What happens to Firebase Test Lab?
Firebase Test Lab is deprecated and will be fully shut down on September 30, 2027. Google points users to Developer Device Platform, which offers physical devices and emulators on Google Cloud in public preview. For other options, see Firebase Test Lab alternatives and the migration guide.
How does the Revyl loop work?
Revyl runs cloud iOS simulators and Android emulators that a script, CI job or agent can start and control, and a Linux CI runner can drive an iOS simulator that Revyl hosts.
The Revyl loop starts with a remote build in Revyl’s cloud, then opens that build on a cloud device (quickstart). Each test run produces a report with the video, a step-by-step timeline, performance metrics, device logs and, for iOS and debuggable Android builds, network traffic. Atlas records the screens and transitions that runs have observed. With proof of changes, Revyl installs a pull request’s build in a live session, runs through the changed flows and posts a verdict on the pull request.
Agents reach Revyl through its MCP server or the CLI, and a CI workflow can run Revyl tests on each pull request. Revyl publishes guides for Claude Code and Codex.
Beyond simulators and emulators: what else Revyl runs
The platform that runs your every-change simulator checks also covers the app’s other surfaces:
- Web browsers: Revyl runs web apps in Chrome sessions streamed to your browser, from a bundle it builds or a preview URL you register, on every plan (Revyl).
- macOS computers: a Revyl Mac computer is a full macOS environment with a desktop streamed to the browser, a shell, files and processes, and it runs GitHub Actions jobs that set runs-on: revyl-macos (Revyl).
- Atlas: every test, session and exploration adds the screens, states and transitions it observed to Atlas, which maps web, iOS and Android apps the same way (Revyl).
- Agent access: through the Revyl CLI or MCP server, an agent can start an iOS, Android or web session or a macOS computer, take screenshots, and wait for a pull request’s build (Revyl).
- PR previews, verdicts and reports: with the GitHub App, Revyl builds the pull requests that match your configured triggers and leaves a pull-request comment with a live preview link to the PR’s build and evidence of the change. Each test run produces a report with video, a step timeline and logs, and with proof of changes, Revyl runs a pull request’s changed flows on iOS, Android or web and posts a verdict on the pull request.
Sources
Facts were checked against these public pages on November 11, 2026. Spot an error? Email support@revyl.ai and we will correct it.
- Apple: Running your app on simulated or physical devices (checked 2026-11-11)
- Android Developers: Run apps on the Android Emulator (checked 2026-11-11)
- BrowserStack App Automate pricing (checked 2026-11-11)
- BrowserStack MCP server docs (checked 2026-11-11)
- Sauce Labs pricing (checked 2026-11-11)
- Sauce Labs Real Device Cloud (checked 2026-11-11)
- AWS Device Farm developer guide (checked 2026-11-11)
- Firebase Test Lab usage, quotas and pricing (checked 2026-11-11)
- Google Developer Device Platform (checked 2026-11-11)
- Kobiton real device testing (checked 2026-11-11)
- TestMu AI live testing (checked 2026-11-11)
- Perfecto FAQ (checked 2026-11-11)
- HeadSpin pricing (checked 2026-11-11)
- Limrun docs (checked 2026-11-11)
- Limrun remote MCP server (checked 2026-11-11)
- Run Cloud simulators (checked 2026-11-11)
- Corellium (checked 2026-11-11)
- Revyl device infrastructure (checked 2026-11-11)
- Revyl mobile quickstart (checked 2026-11-11)
- Revyl remote builds (checked 2026-11-11)
- Revyl test reports (checked 2026-11-11)
- Revyl Atlas (checked 2026-11-11)
- Revyl proof of changes (checked 2026-11-11)
- Revyl MCP server (checked 2026-11-11)
- Revyl tests in CI (checked 2026-11-11)
- Revyl pricing (checked 2026-11-11)
- Revyl Mac computers (checked 2026-11-12)
- Revyl web builds (checked 2026-11-12)
- aws.amazon.com/device-farm/pricing
- kobiton.com/pricing
- testingbot.com/pricing
- www.testmuai.com/pricing
- www.testmuai.com/pricing.md
- www.perforce.com/products/perfecto/build-a-quote
- appetize.io/product
- appetize.io/pricing
- limrun.com/pricing
- run.cloud/pricing
- www.genymotion.com/product-cloud
- docs.genymotion.com/tools/saas/gmsaas
- www.genymotion.com/pricing
- support.corellium.com/subscriptions/pricing
- docs.revyl.com/integrations/cursor/setup
Frequently asked questions
Is an iOS simulator or Android emulator good enough for mobile app testing?
Yes, for most functional checks during development. Google says that in most cases the Android Emulator is the best option for testing, and it can simulate calls, text messages, location and network speeds. No, for checks that depend on hardware: Apple says simulators don't replicate the performance or features of a physical device, and recommends physical devices to verify that an app runs as intended.
Do I need real devices to test biometrics, the camera or SMS?
Usually, when the check exercises the hardware itself. Physical device clouds list these as real-device features: BrowserStack Device Cloud Pro offers OTP and SMS checks on SIM-enabled devices, TestMu AI Real Device Plus lists camera image injection and biometric authentication, and HeadSpin lists SIM and eSIM support on selected devices. Some cloud simulators cover part of this: Run Cloud relays a live webcam into the iOS simulator's camera, and the Android Emulator can simulate incoming texts.
Can I run cloud iOS simulators from a Linux CI runner?
Yes. Limrun documents running xcodebuild, Gradle, XCTest, Maestro and Appium from an Ubuntu runner, and Revyl documents a Linux CI runner controlling an iOS simulator that Revyl hosts. In both cases the CI host does not need a local simulator.
Which device clouds offer both physical devices and emulators?
Sauce Labs sells a Real Device Cloud and a Virtual Device Cloud. TestMu AI, TestingBot and Perfecto list both real devices and virtual devices. Firebase Test Lab runs physical and virtual devices until its shutdown, and Google Developer Device Platform offers physical devices and emulators in public preview.
Is Firebase Test Lab shutting down?
Yes. Google's Test Lab documentation says Firebase Test Lab is deprecated and will be fully shut down on September 30, 2027, and points users to Developer Device Platform on Google Cloud.
Can AI coding agents use a physical device cloud?
Yes. BrowserStack documents an MCP server that can start App Live sessions, and Sauce Labs says AI agents can discover devices, debug and manage test sessions in natural language. On the simulator side, Limrun and Revyl both document MCP servers that let an agent start and drive cloud devices.
What else does Revyl do?
Revyl runs web browsers and macOS computers next to its cloud iOS simulators and Android emulators. Teams and coding agents start sessions from the dashboard, the Revyl CLI or its MCP server, and each test run produces a report. Atlas records the screens, states and transitions that runs observed in web, iOS and Android apps, and with proof of changes, Revyl runs a pull request's changed flows and posts a verdict on the pull request. Mac computers give a whole Mac in the cloud, streamed to your browser, for work such as Xcode builds or GitHub Actions jobs with runs-on: revyl-macos.