What Is a Phone Farm? Device Labs, Real Uses and Abuse

A phone farm is a group of real phones, often dozens or hundreds, connected to computers and controlled together. The same hardware setup is called a device lab or device farm when it is used for testing apps. What makes a setup good or bad is not the rack of phones. It is what the phones are made to do.

How a phone farm works

Most Android phone farms are built from the same pieces:

• Phones on stands or shelves, usually with the screen always on
• Powered USB hubs or a network connection, so one computer can reach many phones
• ADB to install apps, send taps and key presses, read logs and capture the screen
• Software on top that runs the same steps on every phone, from simple scripts to test frameworks such as Espresso, UI Automator, Appium or Maestro

Because ADB works the same on every Android device, one computer can drive many phones at once. If ADB is new to you, start with what ADB is.

Legitimate uses

These are the reasons app teams, QA companies and device makers build device labs:

• Compatibility testing. An app that works on a Pixel can break on a budget phone with an old Android version, a different screen ratio or an aggressive battery saver. A lab with a spread of brands and versions finds those bugs before users do.
• Automated regression tests. Running the same test suite on every build, on real hardware, catches crashes that emulators miss, such as camera, Bluetooth, GPU and vendor-specific issues.
• Performance and battery checks. Measuring start-up time, memory and battery drain needs real devices, not emulators.
• Localization and store screenshots. Capturing the same screens in many languages and screen sizes for review or for the store listing.
• Manual QA at scale. Testers working through checklists on several devices side by side.
• Kiosks, signage and fleet setup. Preparing many company devices with the same apps and settings, or monitoring screens in shops and offices.
• Support and demos. Reproducing a customer's issue on the same model, or showing an app on several devices at once.

Cloud services such as Firebase Test Lab and AWS Device Farm rent this kind of lab by the minute. Teams build their own when they need specific models, physical access, a private network or lower long-term cost. A practical guide is in how to build an Android device lab.

Abusive uses

The term "phone farm" is also linked to activity that breaks platform rules and, in many countries, the law:

• Fake engagement: inflating views, likes, follows, reviews, installs or streams
• Ad and click fraud: generating fake ad impressions or clicks for payouts
• Fake accounts: creating or running large numbers of accounts to spam, scam, evade bans or manipulate rankings
• Vote and poll manipulation, coordinated inauthentic behaviour and harassment campaigns
• Bypassing limits: getting around one-per-person promotions, rate limits or anti-fraud checks

These hurt real users, advertisers and creators. App stores, social networks and ad networks actively detect them and ban the accounts and devices involved, and ad fraud can bring legal action.

Where ADBKit stands

ADBKit is a browser workspace for controlling Android devices over USB and your network. Today you can connect up to six devices in one browser tab, each with its own live screen, logcat, shell and file manager. That already fits small device labs and QA desks.

We get asked about larger setups and automation, and we want to support real device labs well. But tools that drive many phones at once are exactly what abusive farms want too. So we take one rule seriously: we only build multi-device and automation features once we understand the workflow they serve. We talk to the team, learn what they test and why, and design the feature around that job. We do not build generic tools whose main use would be fake engagement, fraud or account farming, and we turn down requests aimed at that.

More on that approach in where ADBKit is heading.

Building a phone farm or device lab?

If you run or plan a device lab for testing, QA, kiosks or fleet management, we would like to hear from you. Tell us what devices you use, what a day of testing looks like and what slows you down: cellhubsapp@gmail.com. Clear workflows are what we build from.