本页面暂无您所用语言的版本，您正在阅读英文原文。
Glossary
Device farm
A device farm is a rack of real phones or computers, one account to a device, used to keep accounts apart by hardware.
What a farm is made of
A farm is devices plus everything that keeps them running: power, a line each, a way to drive them and someone to reset one that hangs.
A cloud service rents the same thing by the hour, usually to test an application on a real handset rather than to hold accounts.
The devices
Phones, tablets or small computers, racked in a room or rented by the hour from a cloud service.
A line per device
Separate exits are what the rack is for, and one office connection behind all of them undoes most of it.
Hands or scripts
Something has to tap, sign in and recover a device, and that cost grows with the rack.
What hardware buys
Each device reads as itself, because it is itself. Storage, graphics, sensors and the network stack belong to one account and never meet another.
That is the deepest separation on the market and the reason farms exist at all.
A rack also answers checks that read hardware rather than values: a camera, a microphone, a message delivered to a number.
What hardware costs
A device per account, a boot per session, a shelf and a person near the shelf. Growing means buying rather than clicking.
A rack also fails in ways software does not: a flat battery, a session lost to an update, a handset that stopped seeing the network.
Where profiles sit instead
A profile is a browser of its own on one computer: its own storage, its own exit and its own machine readings.
How many open at once is computed from this machine's memory and the number is yours to set. Asking for one more than that is refused, and a group launch waits for a free place instead of writing the profile down as failed.
Windows remember where they were left and can be laid out in a grid, which is what makes a screen full of profiles workable.
Phone profiles are not a rack
A phone profile is an ordinary profile on the Android template: the same cookies, proxy and schedule as any other.
If a check reads a value, it answers as a phone. If something needs hardware to act, to shoot or to receive a message, nothing is under it.
The handset arrives whole. Screen, graphics pair, cores and fonts come from one model rather than being mixed from pools.
One address is still one cluster
Rack or profiles, what a platform matches is what the accounts had in common. Four or more profiles behind one exit is the shape a workspace names first.
A group that arrives inside one minute reads as one script, so launches are spaced by a random pause rather than fired in a row.
Profiles that have no proxy do not enter that shape at all. They leave through your own address, and the dashboard says so on a line of its own.
What this does not do
- It does not add hardware. There is no camera, no SIM and no sensor under a profile, and counts are stated rather than captured.
- It is not a phone in a rack. A phone profile renders on the desktop engine wearing an Android template.
- It does not stretch one computer. How many profiles open at once follows that machine's memory, and renting real handsets is a different purchase.
- It does not separate as deeply as separate machines. Profiles are processes on your own kernel, and they share that kernel with each other and with you.
Check it
Each claim here is one place in the code and one stand.
- The ceiling for profiles open at once is computed from the machine's memory, and one more is refused
- apps/desktop/test/предел-открытых.js
- A group launch waits for a free place instead of writing a profile down as failed
- apps/desktop/test/очередь-запуска.js
- The pause between launches is random, measured on the real group loop
- apps/desktop/test/запуск-не-залпом.js
- A phone template arrives as a whole handset, and windows really move when they are tiled
- apps/desktop/test/mobile-really-mobile.js · apps/desktop/test/раскладка-живьём.js
Questions
- Is a profile as separate as a device?
- Not as deeply. Storage, exit and machine readings are separate per profile, while the kernel under all of them is one.
- How many profiles fit on one computer?
- The ceiling is computed from the machine's memory, and the Engine screen takes your own number. Opening one more than the ceiling is refused rather than left to crawl.
- Do I still need real phones?
- For anything that needs hardware: a camera, a SIM, a message to a number, an application that is not a website.
- Can a farm of profiles share one proxy?
- It can, and then it is one cluster. Four or more profiles on one address is the first shape a workspace names.
- Can profiles be driven like a rack?
- Flows run on a schedule and profiles open in groups. The pause between launches is random on purpose, because an even pause is a pattern of its own.
Open a group without buying a rack
Profiles open in a queue on one computer, each with its own storage and its own exit.