Web Base integration

Web Base provides a ready-made Cloud Phone workbench with device lists, individual and batch operations, apps, files, backups, and Task progress. Use it on its own or add it to an existing website.

Who this is for

Your need	Recommended approach
Start managing your own Cloud Phones quickly	Open the standalone workbench and enter the Core URL, Key, and Secret
Let customers manage Cloud Phones within your website	Keep your existing login and connect your website backend to Core

For an existing website, you can use the full workbench or select only the individual device operations, apps, files, backups, or Task progress views. How you combine these views does not change your existing login or backend permission checks.

What to prepare

• A reachable Core URL and management credentials.
• The devices and operations allowed for each customer.
• Where the workbench will appear on your website, and how people will use it on computers and phones.

A standalone administrator enters their own Key and Secret in a trusted workbench. When integrating with a website, keep service credentials in your own backend. Customers use their existing accounts without entering management credentials.

Integration steps

1. Choose your pages. Use the standalone workbench, or add the full workbench or selected operational views to your website.
2. Connect devices and permissions. Verify the connection for standalone use. For a website integration, your backend checks which devices the current customer can view and operate.
3. Add screen access. Integrate the independent Player if users need to view the screen, click, or type.
4. Check real use. Verify operation results, file transfers, and mobile display. After sign-out or an account switch, the previous account's data and operations must not carry over to the new account.

Hiding buttons does not replace backend permission checks. A submitted Task does not mean the device has completed the operation; check the final result.

Integration examples

Example 1: Standalone administrator workbench

Ready-made workbench → Core → Machine room → Cloud Phone

An administrator opens the workbench and enters the Core URL, Key, and Secret to manage authorized devices. Check common operations after connecting. There is no need to build a website or install an SDK first. Add Player if screen access is needed.

Example 2: Add it to an existing React website

Web Base within your page → Your backend on the same origin → Core → Machine room → Cloud Phone

Keep your existing branding, navigation, and login, and place StandardWorkbench directly in your React page. After a customer signs in, the browser calls your website backend. Your backend holds service credentials and makes the final checks on which devices and operations that account may access.

This short example only shows how browser requests connect to your backend, for your developers' reference:

Developer example: Route workbench requests through your backend

import {
  createSessionClient,
  createWorkspaceApi,
  createDataProvider,
} from '@cloud-mobile-web-base/session-client'
const client = createSessionClient({
  host: {
    url: window.location.origin,
    apiPrefix: '/core-workbench',
    identity: bootstrap.identity,
    csrfToken: bootstrap.csrfToken,
  },
  onUnauthorized: () => disconnectHostWorkspace(),
})
const api = createWorkspaceApi(client)
const dataProvider = createDataProvider(client)

This is not a complete application. You still need backend routes, account and permission checks, and the shared React and React Admin contexts with the workbench. Your backend supplies bootstrap. On sign-out or an account switch, call client.clear(), clear cached data from the previous account, and mount the workbench again.

Example 3: Add app management to a device details page

Your device details page → App or file view → Your backend → Core

Keep your website's existing login and page container. Reuse ApplicationsContent within the same connected workbench context to show apps for the selected device. Add files, backups, or Task progress as needed without rebuilding the entire workbench. Your page provides any dialog or side panel.

Responsibilities

The platform provides	You are responsible for
A shared workbench, reusable operational views, and the independent Player	Your branding, navigation, accounts, orders, and billing
Core device operations, permission checks, and Task results	Customer device and operation access, page placement, and integration acceptance

Each website still needs its own integration work. An available standalone workbench does not mean your business system is already connected.

Learn more

Core integration · Platform architecture · Cloud Phone listing capability · Screen access API

Download the English technical reference · Download the complete documentation bundle