Someone who bought cluster control and never got it running
Last winter someone in cross-border trade came to see me. Six months earlier he had bought a cluster control package. It was installed, the phones were connected, and he had run it twice.
I asked where he got stuck. He said it wanted scripts, and he does not write them.
I run into this a few times a year. When people pick iOS automation software, they look at how many devices it can connect, how clear the mirroring is, and whether it supports three systems. What stalls them after it is running is who describes the job to it.
Apple cluster control and iOS cluster control now have three routes that need no code. Record once and let it replay. Buy a script somebody already wrote. Or use AI phone control and say the job in one sentence. Each route has its own situation.
Controlling a phone from a computer depends on which route you pick, and on whether the job should be handed over at all.
| Record once and replay | Buy a ready-made script | AI phone control | |
|---|---|---|---|
| What it takes | Being able to use a phone | Finding the right person | Being able to say it in ordinary words |
| Time to first run | Same day | Depends on their schedule | Same day |
| After an app update | Record again | Ask the author to change it, paid per edit | Usually nothing to change |
| A different platform | Record again from scratch | Buy another one | Say it a different way |
| Suits | Jobs with fixed steps | A flow that stays the same for a long time | Layouts that move, and lots of one-off jobs |
| Several phones at once | Yes, replayed per device | Yes | Yes, dispatched by group |
Connecting phones from a computer is similar across the three routes. All of them can connect several devices. What separates them is the task layer: who describes the job, and who decides.
What each of the three routes costs
Record once and replay is the most direct. You perform the action on the phone. The tool stores where you tapped and what you typed, and plays it back next time.
You can record several flows in an afternoon. What it stores is coordinates and positions. One app update scraps the whole recording. It has no judgement. A popup, a slow load, or a page that never appeared still gets the taps it planned.
The case for it is clear: few steps, an interface that will not move for six months, and only one or two phones. Recording that kind of job once is enough.
Buying a ready-made script is the route many people running iOS cluster control take. It is also the route many users of iOS automation software actually take. Specialists write scripts and sell them one by one. You import one and run it.
It skips the time spent figuring the flow out yourself, especially when you already know how the job is done and simply do not want to write it. The problem is the deliverable. Most scripts sold one by one arrive as an executable, not as source. When the platform changes, you go back to the author and pay per edit.
Ask three things before you pay: what form they deliver, what one change costs, and whether you can take it over yourself. Those three answers matter more than the price. I have seen someone save a few hundred by buying a version they could not edit, then spend three times that on one platform update.
Saying the task out loud to an AI has only become usable in the last couple of years. You do not describe tap here, then tap there. You say what the job should accomplish. The AI looks at the screen, finds the entry point, and decides the next step.
Two things differ from the first two routes. It holds up after an update, because it follows the words and buttons on the screen. The other two routes store fixed coordinates. It can also take one-off jobs. Some work shows up once a month. A script for that is a poor use of time. Say the job once and let the run finish.
What is still worth saving as a fixed flow is the action you repeat every day, with steps that barely change. Once it is a workflow, it runs on its own when the time comes. Repeated runs of a saved flow do not consume model calls. The model is used only when you ask it to plan on the spot.
To skip writing scripts, look at iEasyRun. It is an AI phone control workstation that runs on your own computer. iPhones connect over a cable. Android and HarmonyOS each have their own connection method. Installation is on the deployment page. The illustrated steps for the iOS cable route are here.
Where people who do not write code get stuck, and which route he picked
The first hurdle is deciding what you want it to do. People who write scripts are used to splitting work into steps. People who do not write code often say the job too broadly, for example “put the products online.” The AI does not know which store, which category, or where the price comes from. Spelling that out is the only homework.
The second hurdle is sorting the device layer first. If the phone is not in the list, has no alias, or shows as offline, nothing you say will run. This step usually takes longer than you expect. Finish it before you talk about tasks.
The third hurdle is spreading out too fast. Connect twenty phones on day one, the first day goes wrong, and day two you give up. Get one phone running one job, then add a second. Along the way you learn which parts stay stable.
The three routes can sit together. Over the last few years, the change in Apple cluster control has been mainly on the task layer. Writing a script used to be required. There are now three routes that skip it.
Actions that never change run on a recording or a bought script, which costs the least. Flows whose positions keep moving go to the AI. A job that shows up once gets said in the workstation. The three sit on the same phones without getting in each other’s way. They cover different tasks.
When you pick phone automation software, two things matter: whether devices are detected reliably, and whether a task can be described the way you already speak. The number of rows on the feature list does not help that judgement.
I told him to leave scripts alone for now. Pick one job he does every day and write it in ordinary words, including which phone and what counts as done.
He wrote down replying in the comment sections of several accounts. We walked through it and found three cases he had left out: how to answer when someone asks the price, leaving it when someone is rude, and looking the stock up when someone asks. Adding those three made the setup complete.
His setup now is this. Comment replies run on the AI every day. Product listings still use a script someone else wrote, because that flow has not changed in six months. Each route covers half.
Frequently asked questions
- Can I still do this if I cannot write code at all?
- Yes, and there are three routes. Record an action once and let it replay, which suits fixed steps. Buy a script somebody already wrote, which suits a flow that will not change. Or use AI phone control and describe the job in plain words. None of the three needs code.
- What separates record-and-replay from AI?
- What happens after the interface changes. A recording stores where you tapped, so an app update breaks every position and you record again. The AI reads what the screen says and what buttons exist before deciding where to tap, so an entry point that moved is still found. For apps that update often, that saves a lot of upkeep.
- Can a script I bought be edited?
- Usually not. Ask what the deliverable is before paying: source code, an editable project, or a file that only runs. Only source code lets you fix things yourself when the platform changes. Without it you go back to the author and pay per edit.
- Do Apple cluster control and AI phone control replace each other?
- No, they handle different layers. Cluster control handles devices: connecting several iPhones to a computer, mirroring them, grouping them, dispatching in batch. AI handles the task: what the job actually is and which step comes first. The two layers work well together, and either can be used on its own.
- Does operating an iPhone with AI need a jailbreak?
- No. Over a cable, you install one program on the phone and accept the developer trust prompt, with no jailbreak and no reflashing. Over wireless, the phone and the computer just need to be on the same Wi-Fi network.
- Do several iPhones running at once interfere with each other?
- No. Each device runs its own session and tasks do not cross. Once devices are in the list with aliases and groups, a task can go to a whole group or to just a few of them.
- Does re-running a saved flow keep costing money?
- No. Once something is saved as a workflow, repeated runs do not consume model calls. The model is used when it has to work out the plan on the spot. So fixed actions belong in a workflow, and one-off jobs belong in a conversation.
- Is this worth it for fewer than three iPhones?
- It depends how often the job runs. Something done dozens of times a day is worth it on three phones. Something done once a week can just be described in a conversation and run once, with no flow to maintain. At small scale, getting the feel of it matters more than anything.
Not writing scripts?
Describe the job once and let AI operate the iPhone
The software is completely free and runs on your own computer. No code, and no buying someone else's script.