Cloud simulators vs real device clouds: which should you use?

Revyl Team4 min read

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.

At a glance4 tools, 4 features, public sources checked November 11, 2026
  • 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 sources
FeatureAppetizeLimrunGenymotionRevyl
Cloud iOS simulatorsYesYesNoYes
Cloud Android emulatorsYesYesYesYes
CLIYesYesYesYes
iOS from LinuxYesYesYesYes
Physical device clouds and cloud simulators compared (checked 2026-11-11)
FeatureWhat it runsBest forPricing model
BrowserStackPhysical iOS and Android devices (30,000+ device units advertised)[3]Automated suites on a wide range of real handsets, including SIM-enabled devices for OTP and SMS checks[3]Subscription per parallel test[3]
Sauce Labs10,000+ real devices, plus a separate virtual device cloud of emulators and simulators[6]Teams that want physical and virtual devices from one vendor[5]Subscription by plan and parallel tests (1 to 5 concurrent sessions on self-serve plans)[5]
AWS Device FarmPhysical phones and tablets hosted by AWS[7]Teams on AWS that want metered or per-slot access to physical devices[29]Per device minute, or a flat fee per device slot[29]
Firebase Test LabPhysical and virtual devices; deprecated, with full shutdown on September 30, 2027[8]Existing Test Lab users planning the move Google points to, Developer Device Platform[8]Per device-hour, with separate physical and virtual rates[8]
Google Developer Device PlatformPhysical devices and emulators on Google Cloud, in public preview[9]Checking app performance across OEM form factors, chipsets and OS versions[9]Per device minute during preview; per-slot subscriptions announced for April 2027[9]
KobitonReal device cloud[10]Manual and scripted tests that Kobiton says need real devices, such as biometric authentication, cameras and push notifications[10]Monthly minute allowances; Enterprise by quote[30]
TestingBotReal iOS and Android devices, plus simulators and emulators[31]Small teams that want live and automated testing with a pay-as-you-go option[31]Subscription by parallel tests, or one-time minute packs[31]
TestMu AI50,000+ real Android and iOS devices, plus emulators and simulators[11]Real-device automation with camera image injection and biometric authentication support[32]Per parallel session[33]
Perfecto10,000+ devices, real and virtual[12]Enterprise programs that run 2 to 24 or more parallel executions[12]Quote-based, licensed by parallel executions, 12-month minimum[34]
HeadSpinReal devices on a public cloud, or dedicated devices on private, on-premise or air-gapped deployments[13]SIM and eSIM, geolocation and performance KPIs on real devices[13]Contact sales (no public list price)[13]
AppetizeCloud iOS simulators and Android emulators in the browser[35]App previews, customer support, training and testing in a browser tab[35]Monthly plans with included streaming minutes, then per minute[36]
LimrunCloud iOS simulators and Android emulators, plus Xcode and Gradle builds[14]Coding agents and Linux CI runners that build and drive mobile apps[14]One-time 120-credit trial (60 iOS minutes), then monthly credit plans[37]
Run CloudCloud iOS simulators and Android emulators[38]Camera-dependent flows, with a live webcam relay into the simulator's camera[16]Per active simulator minute[38]
GenymotionAndroid virtual devices[39]Android teams that start cloud emulators from a CLI (gmsaas) in CI[40]Per minute per active virtual device, or a flat monthly fee per device[41]
CorelliumArm-native virtual iOS and Android devices[17]Security research and pentesting that need root-level access[17]Per device-hour on Solo Explorer; enterprise plans through sales[42]
RevylWeb browsers, iOS simulators, Android emulators and macOS computers[24]Runs that must become evidence for agents and reviewers: a pull-request comment with a live preview link, a report, Atlas data and a pull-request verdict[43]Free: up to 1,200 free device minutes a month on iOS, Android, web and Mac on 2 devices at once; Pro: pay as you go with no monthly fee, $0.075 per device minute on iOS and Android, $0.05 a minute on web and Mac, 10 devices at once[26]
What each kind of device can check, in the platform owners' and vendors' words
FeaturePhysical device cloudsCloud simulators and emulators
Guidance from Apple and GoogleApple: to verify that your app runs exactly as intended, run it on one or more physical devices[1]Google: in most cases, the Android Emulator is the best option for your testing needs[2]
Hardware-specific featuresApple: simulators don't replicate the performance or features of a physical device[1]Apple: run on one or more physical devices to verify the app runs as intended[1]
PerformanceDeveloper Device Platform: test performance across OEM form factors and chipsets (CPU, GPU, NPU)[9]Apple: simulators don't replicate the performance or features of a physical device[1]
SMS and callsBrowserStack Device Cloud Pro: 2FA with OTP or SMS and interrupt testing on SIM-enabled devices[3]Android Emulator: simulate incoming phone calls and text messages[2]
CameraTestMu AI Real Device Plus: camera image injection and QR code scanning[32]Run Cloud: live webcam relay into the iOS simulator's camera[16]
Location and networkHeadSpin: geolocation testing in 17 locations on Lite and Go, 50+ on Pro[13]Android Emulator: set the device location and simulate network speeds[2]
Device rangeBrowserStack: 30,000+ real iOS and Android device units[3]Android Emulator: predefined phone, tablet, Wear OS, Android Automotive OS and Android TV configurations[2]
Linux CI and coding agentsSauce Labs: AI agents discover devices, debug and manage test sessions in natural language[6]Limrun: run xcodebuild, Gradle, XCTest, Maestro and Appium from an Ubuntu runner[14]

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.

  1. Apple: Running your app on simulated or physical devices (checked 2026-11-11)
  2. Android Developers: Run apps on the Android Emulator (checked 2026-11-11)
  3. BrowserStack App Automate pricing (checked 2026-11-11)
  4. BrowserStack MCP server docs (checked 2026-11-11)
  5. Sauce Labs pricing (checked 2026-11-11)
  6. Sauce Labs Real Device Cloud (checked 2026-11-11)
  7. AWS Device Farm developer guide (checked 2026-11-11)
  8. Firebase Test Lab usage, quotas and pricing (checked 2026-11-11)
  9. Google Developer Device Platform (checked 2026-11-11)
  10. Kobiton real device testing (checked 2026-11-11)
  11. TestMu AI live testing (checked 2026-11-11)
  12. Perfecto FAQ (checked 2026-11-11)
  13. HeadSpin pricing (checked 2026-11-11)
  14. Limrun docs (checked 2026-11-11)
  15. Limrun remote MCP server (checked 2026-11-11)
  16. Run Cloud simulators (checked 2026-11-11)
  17. Corellium (checked 2026-11-11)
  18. Revyl device infrastructure (checked 2026-11-11)
  19. Revyl mobile quickstart (checked 2026-11-11)
  20. Revyl remote builds (checked 2026-11-11)
  21. Revyl test reports (checked 2026-11-11)
  22. Revyl Atlas (checked 2026-11-11)
  23. Revyl proof of changes (checked 2026-11-11)
  24. Revyl MCP server (checked 2026-11-11)
  25. Revyl tests in CI (checked 2026-11-11)
  26. Revyl pricing (checked 2026-11-11)
  27. Revyl Mac computers (checked 2026-11-12)
  28. Revyl web builds (checked 2026-11-12)
  29. aws.amazon.com/device-farm/pricing
  30. kobiton.com/pricing
  31. testingbot.com/pricing
  32. www.testmuai.com/pricing
  33. www.testmuai.com/pricing.md
  34. www.perforce.com/products/perfecto/build-a-quote
  35. appetize.io/product
  36. appetize.io/pricing
  37. limrun.com/pricing
  38. run.cloud/pricing
  39. www.genymotion.com/product-cloud
  40. docs.genymotion.com/tools/saas/gmsaas
  41. www.genymotion.com/pricing
  42. support.corellium.com/subscriptions/pricing
  43. 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.

Revyl Team

Published November 11, 2026