# Real device cloud or cloud phones: what does your AI agent need?

A cloud Android phone for UI tasks, a real device cloud for attestation, hardware and performance. What each covers, where device labs stop, and how Mobilebox runs both over one API.

By [Mustafa Yenler](https://mobilebox.dev/about#mustafa) [LinkedIn](https://www.linkedin.com/in/mustafa-yenler) Updated 16 November 2026

Decisions4 min read

In this article

Use a cloud Android phone when your agent’s task lives in the UI: install a build, read the screen, tap through a flow and check the result. Use a real device cloud, physical phones you reach over the network, when the task depends on hardware, on device attestation or on performance that has to match a real handset.

Mobilebox runs both, cloud Android phones and [real Android devices](https://mobilebox.dev/real-devices), over the same API and MCP, so your agent’s code doesn’t change when a check moves to hardware.

## What a physical device adds

Attestation is the clearest dividing line. In Google’s [Play Integrity verdicts](https://developer.android.com/google/play/integrity/verdicts), `MEETS_DEVICE_INTEGRITY` means "the app is running on a genuine and certified Android device". The verdict is blank when the app is "not running on a physical device (such as an emulator that does not pass Google Play integrity checks)". An app that gates sign-in or payment on that verdict needs a device that earns it.

Hardware is the second. Android’s [testing strategy guide](https://developer.android.com/training/testing/fundamentals/strategies) notes that media players and camera apps "might depend on specific hardware features". Its example plan runs application tests on emulators plus one phone and one foldable, and release candidates on eight phones, a foldable and a tablet. The [hardware device guide](https://developer.android.com/studio/run/device) is direct: "Always test your Android app on a real device before releasing it to users."

## A real device is not always a phone line

Check the exact feature with the vendor. [AWS Device Farm](https://aws.amazon.com/device-farm/faqs/) runs tests on real devices, yet its FAQ says the devices "do not have carrier connections and cannot make phone calls or send SMS messages". It offers network shaping and a GPS override instead. "Physical" answers the attestation and hardware questions; it does not by itself answer the SIM question.

## Choose by the task

| The task depends on | Cloud Android phone | Physical device |
| --- | --- | --- |
| Installing an APK and reading its first screen | Fits | Also works, with more setup |
| A multi-step UI flow with a checkable outcome | Fits | Also works |
| Keeping a login between agent sessions | Park and resume | Depends on the lab’s reset rules |
| Play Integrity device verdicts | May not pass | Needed |
| Camera, sensors or release-grade performance | Not the right test | Needed |
| Calls or SMS | Not the right test | Only if the device has carrier service |

Most agent work sits in the top rows. Move a check to hardware when a failure could only be explained by the device.

## What the cloud phone gives your agent

Mobilebox runs cloud Android 14 phones (arm64). Your agent drives them over REST or a hosted MCP server: it observes the screen as numbered elements, then taps, types and swipes, installs APKs, and parks the phone to keep apps, data and logins. A ready phone costs $0.01 per minute, and apps with strict integrity checks may not run. The [compatibility checklist](https://mobilebox.dev/blog/android-app-compatibility) helps you test that before you build a workflow on it. To connect an agent, start with the [quickstart](https://mobilebox.dev/docs).

## Real devices on Mobilebox

Real Android devices cost $0.01 per phone-minute, the same as a cloud phone; ask for one with `device: "real"` ([reference](https://mobilebox.dev/docs/reference#devices)). Every response says which device your agent got (`device: "real"` or `"cloud"`): treat a cloud phone’s results as cloud evidence, not device evidence.

Hosted labs cover the physical half as well. [Firebase Test Lab](https://firebase.google.com/docs/test-lab) runs tests on real, production devices in a Google data center, and also offers Android emulators, until it shuts down on September 30, 2027 ([what replaces it](https://mobilebox.dev/blog/mobilebox-vs-firebase-test-lab)). AWS Device Farm offers [remote access and automated runs](https://docs.aws.amazon.com/devicefarm/latest/developerguide/welcome.html) on physical phones and tablets. Keep both results tied to the same build, and say which risk each one covered.

Sources reviewed on November 4, 2026.

[Mustafa Yenler](https://mobilebox.dev/about#mustafa) is the founder of fifteenA and builds Mobilebox, from Berlin and San Francisco. [LinkedIn](https://www.linkedin.com/in/mustafa-yenler)

## Try it in your agent in 60 seconds

Paste this into Claude Code, Cursor, Codex or any agent that can read a web page. It asks for your email, gets its own key at once and adds the phone tools; the 6-digit code from your inbox keeps the workspace.

```
Set up Mobilebox for me: read https://mobilebox.dev/setup.md?via=real-android-devices-vs-cloud-phones and follow it.
```

[What your agent reads](https://mobilebox.dev/setup.md?via=real-android-devices-vs-cloud-phones)

In this article

[All articles](https://mobilebox.dev/blog)

## Next question

- [What replaces Firebase Test Lab?](https://mobilebox.dev/blog/mobilebox-vs-firebase-test-lab?via=next-firebase)
