Apple cluster control is a plain idea: one computer acts as the controller, and work you used to tap through by hand becomes one dispatch and a batch run. The iPhone itself does not need a jailbreak.
A team that makes programming tutorials ran the numbers. Ten videos on Douyin, from picking the asset to tapping publish, take under half an hour. The same ten pieces on Bilibili take forty minutes each.
Inside those forty minutes you wait for the upload, wait for transcoding, and wait for review, and you also fill in the category, tags, cover, and description. Hands-on work is under five minutes. The other thirty-five minutes are waiting. For Bilibili batch uploads, the time is mostly waiting.
Where the forty minutes on one upload go
One submission passes several gates. Upload is one. Short video is usually tens of megabytes. Mid-length and long video is hundreds of megabytes to several gigabytes. On the same network, upload time can differ by two orders of magnitude. Transcoding is the second gate. Bilibili converts the video into its own format. You do not control that, and the time depends on video length and the queue at the moment. Review is the least predictable. Machine review is usually a few minutes. A manual review can take hours or a day. Filling in details means category, tags, cover, description, and multi-part. Bilibili is stricter about category and tags than short-video platforms, and a wrong choice affects recommendation. After all of that, you publish.
Upload and transcoding are time and bandwidth. Review is uncertain. Filling in the details can be standardized. The script belongs on that step.
Multi-part is a Bilibili structure: one submission holds several video segments, and viewers watch them in sequence on one page. Tutorials, course series, and collections fit multi-part well. Batch publishing has to handle a whole set of parameters: part order, a title for each segment, which segment is the cover, and how the description is written. Filling that in by hand can take several minutes for one submission. When the content itself fits multi-part, such as a course with twenty lectures, that parameter set is worth turning into a template. Forcing an ordinary single video into multi-part only adds another layer of settings.
Asset delivery and review: which steps a script can take
Short-video files are small, so cloud sync or a bulk push from central control stays light. A Bilibili file is hundreds of megabytes to several gigabytes. Pushing that to dozens of devices uses time and bandwidth quickly. Two approaches work. One is to push in batches. Do not push everything at once. Follow device priority: push five first, finish the run, then push the next batch, so the network is not saturated in one shot. The other is to let each device download: put the video at an address the phone can reach, and the script starts the download on each device, so bandwidth is spread across the phones. The cost is that every phone waits, and a failed download has to be handled on its own. Small files and few devices: sync. Large files and many devices: download.
Review cannot be automated. You do not know how long a given submission will sit in review, and you cannot hurry it. The reason for a rejection is sometimes vague: copyright, category, or the content itself. A batch job cannot be managed by “publish and verify immediately.” After you submit, log it: upload time, title, and submission ID. Run a check later, see whether the status changed, and handle it when it has. The time stays predictable, and one item stuck in review does not hold the rest.
What fits a script is this set of jobs: submission status checks, so you regularly see which are in review, which passed, and which were returned; data collection, pulling plays, danmaku, and comments into one place; and bulk preparation of assets and parameters, including titles, descriptions, and tags that can be templates. Fully automatic uploading is a poor fit. Large files, long waits, and uncertain review stack together, so the gain is small and the cost of tracing a failure is high. A person uploads, and a script records it. That is steadier. Skipping review, reposting someone else’s content, and faking originality are rules. Those cannot be done. Standardizing the parts that can be standardized is enough. The whole flow does not have to go into the script.
Multiple accounts need more care
Bilibili needs more care than a short-video platform. The content ecosystem rests on the individual creator brand. Viewers follow that person. Ten accounts with no identity are often worth less than one account with a regular audience. Repost judgment and originality requirements are also stricter than on short-video platforms. The same material spread across several accounts is more likely to be recognized, and the penalty is heavier. If you do it, split by content direction. One account for technical tutorials, one for product reviews, one for industry commentary. Three accounts with a clear position do not mix their audiences, and they are harder to treat as a matrix.
Warm-up takes a long time. From registration to normal weight can take weeks or months. The devices have to keep running for that long. Do not use machines you assembled for a week. On Apple cluster control, iPhones of the same model share resolution and system behavior, so size, coordinates, and waits in the script can be reused and you do not retune when you swap a device. Android models are more fragmented. Mixing models adds a lot of debugging. Match the device count to the accounts you will actually run. Ten half-dead accounts are worth less than putting the devices on two or three.
For more, read How do you schedule multi-account publishing with Apple cluster control? Short-video scheduling and asset management, A one-tap sync publishing plan for Douyin matrix accounts, One system for Douyin, Xiaohongshu, and Kuaishou, and Apple cluster control for Zhihu content distribution: compliant bulk answers and topic traffic.
About EasyClick: A mobile automation script development platform covering three phone ecosystems: Android without root, iOS without jailbreak, and HarmonyOS. It also offers Apple script writing, Apple cluster control, Android cluster control, remote cloud control, and AI phone cluster control. → Explore all products · Apple cluster control
Ready to build it for real?
Every approach in this article can be built with EasyClick capabilities on iEasyClick — full documentation, developer tools and automation products, free to try.