Platform overview
The platform provides Android Cloud Phone management, Task execution, app and file operations, backups, and screen streaming. Use the standard workbench directly, or build your business through its APIs.
Who this is for
Administrators managing their own Cloud Phones, and teams building rental, sales, internal tooling, or automation products. Check the prerequisites and limits in the capability catalog to assess your specific business needs.
What to prepare
Identify your target devices, network environment, required operations, and end-user access scope. Devices and Machine Room services need to be connected. Confirm hardware support, Image compatibility, and streaming behavior against the delivered version and on-site acceptance results.
How to start
- Choose the relevant modules and list the scenarios you must support.
- Choose Web Base for an operational interface, or Core APIs for business integration.
- Agree on responsibilities, then validate permissions, operation results, and streaming in the integration environment.
Responsibilities
| Platform | Your business |
|---|---|
| Device resources, technical authorization, Task records, and app and file operations | User accounts, customer ownership, products, orders, payments, and renewals |
| Standard workbench, streaming interface, and device execution path | Your brand, business pages, reporting, and automation workflows |
| Validate operations against the authorized scope | Decide who may use which resources, which operations are allowed, and when access expires |
Task Acceptance does not mean that a device operation has completed. An Unknown Result requires checking the original Task. Restoring a Backup creates a new Cloud Phone on the target Cloud Card; confirm backup contents and compatibility separately.
Next resources
Platform architecture and responsibilities · Core integration · Web Base integration