Skip to main content
Read the screen and control a device from your own code. The screen needs a moment after opening an app or tapping; these examples retry UI reads because the SDK has no element-wait helper yet.

Read the screen

Read the filtered UI tree and capture a screenshot. Needs: Cloud Android · API key and DEVICE_ID · no app or device account · device minutes, no task credits or add-ons · one-shot, under 1 min.
Use get_device_ui_state to read the filtered UI state and get_device_screenshot to capture the screen. List the foreground app and each clickable element with its text and bounds.

Tap and type an alarm

Start Clock, create and verify a 07:00 alarm, then delete it. Needs: Cloud Android · standard Clock app · no device account · API key and DEVICE_ID · device minutes, no task credits or add-ons · one-shot, ~1 min · dedicated test device without 07:00 or earlier alarms; remove the test alarm if interrupted.

Run your own loop

Run an observe–decide–act loop to enable Dark theme, verify it survives stop and resume, and turn it off. Needs: Cloud Android · Settings · no device account · API key and DEVICE_ID · device minutes, no task credits or add-ons · one-shot, up to 20 steps.

Run it on many devices

This runs on as many devices as you need: each device is read in parallel.
Read each device’s filtered UI tree and save its screenshot in parallel. Needs: 2+ ready devices · DEVICE_IDS or all ready devices · one-shot

Next steps

Explore device controls to build your own actions.
Start with the first example on a ready device the user names. Uses device UI state, screenshots, app launch, tap, swipe, and keyboard calls. Ask before changing device settings or creating an alarm; never purchase anything or use real accounts. Report the result and any failed step.