Phone farm glossary: devices, accounts, automation and metrics

Phone farm terminology mixes hardware, accounts, networking and content operations. The easiest way to understand it is to follow one job: an operator opens a phone, confirms the brand's signed-in account, publishes an approved video, then checks the result. Each stage uses a different set of terms.

The examples below use the fictional brand Northline Desk. Its account is ACC-NL-01, its assigned phone is DEV-NL-01, and one approved video is AST-TRAY-01-v2. These are example naming conventions, not identifiers that PhoneFarm generates for you.

Phone environments and infrastructure

Phone farm and device fleet

A phone farm is a group of phone environments operated as a coordinated system. A device fleet is the broader management term for a collection of devices. The important change from owning several phones is shared organization: identifying each device, assigning work, monitoring availability and handling failures. See what a phone farm is.

Physical phone, cloud phone and emulator

A physical phone is a hardware handset. A cloud phone is a phone environment reached remotely; the term alone does not tell you its underlying implementation. An emulator reproduces aspects of another system in software. These are different attributes, so “remote” and “physical” are not opposites. Ask which operating system, hardware and app capabilities the offered environment provides. See the environment comparison.

Instance and provisioning

An instance is a particular allocated environment. Provisioning is the process of allocating and preparing it. A newly provisioned instance may still need network configuration, an installed app and account login. “Created” should therefore not be read as “ready to publish.”

Fleet capacity and effective capacity

Fleet capacity is the phone resource available to your operation. Effective capacity is the work it can actually complete after accounting for availability, task duration and dependencies. Ten phones with three unusable sessions provide seven usable phone environments at that moment. If the editor can finish only four videos, the content pipeline may be the tighter limit.

Host, rack and powered hub

A host is a computer or service that manages connections to devices. A rack organizes physical devices. A powered hub provides multiple connections with an external power supply; its available power and data capabilities still need to match the intended equipment. These matter for an owned fleet but may be supplied as part of hosted service. See phone farm equipment.

Accounts, identity and access

Product login and social account

Your PhoneFarm login gives access to the dashboard. A social account is a separate account inside TikTok or another app. Being signed into the dashboard does not mean the phone is signed into the intended social account. Check the profile in the native app before account-specific work.

Account owner, operator and reviewer

The owner is accountable for the account and recovery. The operator carries out authorized work. The reviewer approves content or decisions. These are team responsibilities used throughout this guide, not a promise that PhoneFarm has matching built-in permission roles. One person may hold several responsibilities, but the responsibility should still be explicit.

Account register and device assignment

An account register maps a stable account ID to its platform, current handle, owner, assigned phone and recovery contact. Device assignment records where that account is normally operated. Handles and phone labels can change; a stable internal ID keeps old publication records understandable. See account inventory.

Session and session persistence

A session is an authenticated or interactive connection with state. A social-app login session and a PhoneFarm live-control session are different things: control can disconnect while the app remains signed in. Persistence means specified state survives between uses. Ask which state persists across stopping, replacing or resetting a phone before relying on it.

Recovery and two-step verification

Recovery is the supported process for regaining access to an account. Two-step verification adds another verification step to sign-in. Recovery email, phone access and backup mechanisms need an owner who remains reachable when an operator leaves. They should be stored through your credential process, rather than copied into a public task sheet. See access and recovery.

Network and location terms

IP address and exit IP

An IP address identifies an interface or endpoint in an IP network. The exit IP is the public address observed by a destination for a particular connection. Checking it from your laptop reports your laptop's route, not necessarily the route taken by a remote phone.

Proxy and VPN

A proxy intermediates supported network requests. A VPN carries selected traffic through a tunnel according to its configuration. Neither label alone proves that every app, protocol or request follows the intended route. For operational work, verify the actual phone connection. Read proxies and networking for the setup concepts.

Static, rotating, residential and datacenter

Static describes an address intended to remain stable over an agreed period; rotating describes a service that changes its exit address. Residential and datacenter describe network classifications used by suppliers and databases. Classification is not a promise about audience reach, account approval or uninterrupted service. Check the service contract and observed behavior.

Latency, bandwidth and connectivity

Latency is delay. Bandwidth describes transfer capacity. Connectivity means the required destination can be reached. A phone may load a small page but struggle to upload a large video; a live-control session may feel slow even when an upload eventually completes. Report the specific symptom rather than saying only “the internet is broken.”

Fingerprint and audience geography

A device fingerprint is a combination of observable characteristics that may help distinguish environments. Audience geography describes where viewers are reported to be. It is a result to measure, not another name for the phone's network location. A country-matched connection does not guarantee that every viewer comes from that country.

Content and publishing operations

Campaign, creative brief, format and variant

A campaign connects content to a business objective. A creative brief defines the audience, message and desired action. A format is a repeatable presentation structure, such as a before-and-after desk demonstration. A variant changes a defined element within it, such as the opening shot. See campaign planning and content experiments.

Asset and version

An asset is a media file or other creative component. A version identifies a particular revision. AST-TRAY-01-v2 should refer to the same approved file for the editor, reviewer and publisher. “Final-final.mp4” is difficult to distinguish from another file with the same name.

Library, phone media, draft and publication

A file in the Videos library is available in that library. A file in phone media is present on the device. A draft is content prepared inside a workflow or app but not yet published. A publication is the resulting post on the platform. These are separate states; success at one stage does not prove the next.

Task, queue, attempt and retry

A task describes intended work. A queue holds work waiting to execute. An attempt is one execution of that task. A retry is another attempt after an unresolved or failed execution. Two attempts should not automatically be counted as two successful posts. Check an uncertain outcome before retrying a publication.

Scheduling and orchestration

Scheduling determines when work should run. Orchestration coordinates dependencies and resources: the right asset must be approved, the account usable, and the phone available. A scheduled time does not guarantee completion at that moment. Use only the scheduling controls available for your current product workflow.

Reliability and measurement

Availability, readiness and freshness

Availability means a resource can be reached. Readiness means it can perform the intended job. Freshness tells you when the observation was made. “Phone running, profile not checked today” is more informative than a single green status that hides both facts.

Baseline, median and outlier

A baseline is your reference performance under comparable conditions. The median is the middle observed value after sorting, or the average of the middle pair. An outlier is an unusually different observation. For 80, 120, 180 and 620 views, the median is 150 and the mean is 250; the unusually strong post raises the mean. See weekly reviews.

View, engagement rate and conversion

A view uses the platform's counting definition. An engagement rate divides named interactions by a stated denominator. A conversion is a defined business event, such as an order or qualified lead. Always name the metric source and observation window; “5% engagement” is incomplete without the formula.

Attribution, incrementality and contribution

Attribution assigns credit under a rule. Incrementality asks how much additional outcome an activity caused. Contribution is revenue remaining after specified variable costs, before the additional operating costs you are evaluating. A tracked order may be attributed to social without proving it would not otherwise have happened. The contribution guide works through the arithmetic.

Control tools and fleet reliability

ADB (Android Debug Bridge): Android's device-communication tool, used in development and device administration. It can identify connected devices and support app installation or diagnostics. ADB access is a specific interface, not something every hosted phone service exposes.

UI Automator: An Android framework for UI tests that interact with user and system apps. It helps a test locate controls and wait for relevant interface states.

XCTest / XCUIAutomation: Apple's testing frameworks for exercising and checking app behavior, including the user interface. Android tooling and Apple tooling have different setup requirements.

Appium: An automation framework using platform-specific drivers and language clients. The installed driver determines how it connects to the target environment. Compare these tools and customer-facing routes in phone automation methods.

Heartbeat: A recent signal that a monitored component is responding. A control service's heartbeat does not prove that the phone's social app is signed in or that its last publication succeeded.

Baseline: A recorded working configuration or performance reference. In a fleet, this can include device model, OS and app versions, connection and expected task result. A content baseline describes a different thing, such as typical performance over a defined observation window.

Canary update: A limited rollout to a representative small part of the fleet before expanding the change. The purpose is to observe compatibility and failures while their impact is contained. See device lifecycle and maintenance.

Device/OS test matrix: A deliberate selection of device, operating-system, app and regional combinations used to check a workflow. Its coverage should reflect the users and failure risks being studied; more rows are not automatically better coverage. See mobile QA and regional checks.

Idempotency: The property that repeating a request has the same intended effect as performing it once. Do not assume an app's publish button has that property: a second submission can create a second post. Publication verification explains how to handle an uncertain result.