# An AI agent for your mobile apps.

For mobile app automation, give your AI agent a Mobilebox phone: it installs the app, reads the screen, taps through the task and checks the result, over MCP or REST. A cloud Android phone costs $0.01 a minute while it runs. Use it to test your own app, or to run tasks in apps you use with your own account.

[Get started](https://mobilebox.dev/docs) [Test an APK from CI](https://mobilebox.dev/blog/android-apk-ci-smoke-tests)

Sign up with GitHub. New workspaces get free credit.

## Two uses that fit

And one we don't support.

### Test your own app

- Install your APK from a URL

- Walk a flow and check each screen

- Run it from CI and delete the phone after

### Your tasks, your account

- Tasks in apps you use, signed in as you

- Park the phone to keep the login

- Within each app's terms

### Not for this

- Mass or fake accounts

- Spam, bulk messages or automated swiping

- Getting around an app's limits or checks

## How a run works.

Batch the steps you know. Observe the ones you don't.

[Batching actions](https://mobilebox.dev/blog/retry-mobile-actions-safely)

1. Install the app
   `install_app` takes an APK or split bundle from a URL. Google Play isn't included.

2. Run the task
   `observe` reads the screen. `act` runs up to 20 taps, typing and swipes per call.

3. Check the outcome
   Read the final screen, keep a screenshot as evidence, then park or delete the phone.

## Questions

Which apps, which uses, and the rules.

Which apps work?

Most apps you can install from an APK. In our 4 November 2026 check, WhatsApp, Telegram, Signal, Firefox, Wikipedia and Bitwarden installed and opened on a Mobilebox phone. Apps with strict integrity checks may not run on a cloud phone; for those, pick a [real Android device](https://mobilebox.dev/real-devices).

Can I test my own app in CI?

Yes. A CI job installs your APK, checks the first screen and deletes the phone, even when the check fails. See [APK smoke tests from CI](https://mobilebox.dev/blog/android-apk-ci-smoke-tests) and [testing with Claude Code](https://mobilebox.dev/blog/claude-code-android-app-testing).

Can my agent use Tinder, Hinge or Uber Eats for me?

Only with your own account and within each app's terms. We haven't checked those apps on a Mobilebox phone, and they may need Google Play or pass integrity checks a cloud phone can't. No mass or fake accounts, automated swiping or bulk messages.

Does the agent stay signed in?

Parking keeps apps, data and logins, and stops billing. An app's own session can still expire, so the agent should check it's signed in before it starts. See [park and resume](https://mobilebox.dev/blog/park-resume-android).

What's the difference from Appium?

Appium is a test framework you script. Mobilebox is the phone and a small action set an agent drives directly. See [Mobilebox or Appium](https://mobilebox.dev/blog/mobilebox-vs-appium), or what a [phone agent](https://mobilebox.dev/phone-agent) is.

App names are trademarks of their owners; no affiliation.

## Read more

[Will this Android app work on a cloud phone? Check APK architecture, exposed UI, device services, physical features and attestation before promising a particular app workflow. Decisions4 min read](https://mobilebox.dev/blog/android-app-compatibility) [How to evaluate an Android agent without grading its own story Define testable outcomes, separate environment and control failures, include recovery cases, keep a small acceptance contract and retain evidence for every attempt. Engineering4 min read](https://mobilebox.dev/blog/android-agent-evaluations)

New to this? Start with a [mobile sandbox](https://mobilebox.dev/mobile-sandbox) or compare [AI sandboxes](https://mobilebox.dev/ai-sandbox).

## 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=app-automation and follow it.
```

[What your agent reads](https://mobilebox.dev/setup.md?via=app-automation)

## Next questions

- [Cloud phone or a local emulator?](https://mobilebox.dev/blog/mobilebox-vs-local-emulator?via=next-emulator)

- [Mobilebox, Limrun or Mobilerun?](https://mobilebox.dev/blog/mobilebox-vs-limrun?via=next-limrun)

- [How do I add it to Cursor, Codex or VS Code?](https://mobilebox.dev/blog/android-mcp-cursor-codex-vscode?via=next-setup)

- [Can my agent run 50 phones in parallel?](https://mobilebox.dev/blog/run-android-phones-in-parallel?via=next-parallel)

- [Can my agent use an iPhone?](https://mobilebox.dev/ios?via=next-iphone)

- [Can each phone get a residential IP?](https://mobilebox.dev/blog/residential-ip-per-phone?via=next-residential-ip)

- [Does my agent stay logged in between runs?](https://mobilebox.dev/blog/park-resume-android?via=next-logins)

- [Can I watch my agent work live?](https://mobilebox.dev/live-view?via=next-live)
