Run the same test
Script a flow once, run it on one phone or a whole fleet, schedule it to repeat, and review the screen recording next to the traffic it captured.
Manual regression testing
Simulators miss real-device bugs, and manually tapping through a login flow on ten physical phones before every release is a job nobody wants.
For QA and mobile teams who need a login flow, a purchase path, or a regression suite exercised on real hardware — not a simulator — across more than one device, on a schedule, without someone holding every phone.
Busymate's Phone Farm turns a Mac with a USB hub into a self-hosted device lab. Connect Android or iOS phones and they're provisioned automatically — install and launch apps, run find-and-tap flows, batch a script across every connected device, and schedule the whole thing to repeat.
One Mac,
Control and capture live in the same feed — not two products stitched together.
Automate the whole fleet
Find-and-tap flows, app installs and launches, batch automations, schedules and screen recordings — run them on one phone or across all of them at once.
Devices, provisioned instantly
Connect a phone and it appears in the dashboard, provisioned and ready to control — no per-phone wiring, no lab software to babysit.
Capture rides along for free
Every farmed phone's HTTPS routes through the same capture pipeline as everything else, so a failed run comes with the exact requests it made — not just a screenshot.
- Farm
- Android
- iOS
- Dashboard
- MCP
How it works
A Mac with a USB hub is the lab; the dashboard is the control room.
- 01
Plug the phones into the host
Run the farm host on the Mac that drives the phones. Android devices are adopted automatically over USB debugging; iOS devices are provisioned after the one-time Developer Mode and Trust taps. Each phone appears in the dashboard with a stable identity that survives replugs and reboots.
- 02
Script the flow you want repeated
Build a flow from the actions the farm exposes — install and launch an app, find an element by its label and tap it, type text, take a screenshot. Run it against one phone first and watch the live mirror while it goes, then select every connected device and run it across all of them at once.
- 03
Schedule it, then review each run
Attach a schedule so the flow repeats nightly or before every release. Every run leaves a screen recording next to the HTTPS traffic the phone made during it, so a failed step comes with the exact request that failed, not just a picture of the screen.
Before you plug in,
Do I need a device-lab service, or my own hardware?
Your own. The farm is self-hosted: a Mac, a hub, and the phones you already have. There is no per-minute meter and no seat fee — you run the host and the dashboard drives it.
Can one script run on iOS and Android?
The actions are shared — install, launch, find-and-tap, type, screenshot — but element labels differ between platforms, so a flow usually needs a per-platform variant for the steps that touch the UI.
Can an AI agent drive the runs?
Yes. Every farm action is also an MCP tool, so an agent connected to the MCP server can install an app, run a flow and read back the recording and the traffic — under the same role and confirmation rules a human operator has.
What happens when a phone drops off USB?
The host reconnects it and keeps its identity, so schedules aimed at that phone resume without a re-setup — a replug, a reboot or a hub change never turns it into a new device.
Test on real phones,
Connect your first device and run a scripted flow across the fleet today.