How the driver works

The mobile driver controls the phone inside a session. Its reliable loop is:

Observe the current screen.
Point at a target with a locator, by visible text or a description.
Tap, type, swipe, or press a key.
Observe or wait for the expected result.

A locator action finds its target on the screen at that moment and waits until it can act, up to 5 seconds by default, so most steps need no separate wait. Start with a dedicated-phone session, then use the interface that fits your program.

CLI
Python SDK
Go SDK

axilio phone observe
axilio phone tap --query "the search icon"
axilio phone tap --query "the Search field"
axilio phone type "axilio"
axilio phone key enter
axilio phone observe

from axilio.platform import Client

client = Client()

with client.session("android", phone_id="ph_123") as driver:
    driver.locator(query="the search icon").tap()
    driver.get_by_text("Search").fill("axilio")
    driver.key_press("enter")
    screen = driver.observe()

if _, err := driver.Locator(mobile.Query("the search icon")).Tap(); err != nil {
    log.Fatal(err)
}
if _, err := driver.GetByText("Search").Fill("axilio"); err != nil {
    log.Fatal(err)
}
if err := driver.KeyPress(mobile.KeyEnter); err != nil {
    log.Fatal(err)
}
screen, err := driver.Observe()
if err != nil {
    log.Fatal(err)
}
fmt.Println(len(screen.Texts))

Phone control uses the session’s Device Control Protocol WebSocket. The CLI and SDK drivers expose these actions; they are not REST endpoints.

The basics

Find

Locate something by its text or by describing it.

Tap

Tap a target or press and hold.

Type

Type into a field.

Swipe

Swipe, scroll, or drag.

Keys

Press Enter to submit a form or search.

Observe

Read the whole screen at once.

Wait

Wait for the screen to change before acting.

Screenshot

Capture the current pixels as a PNG.

Semantic targets and coordinates

Use text or a natural-language query for a tappable target whenever possible. Coordinates are appropriate for gestures that move the whole screen or for a fixed point you derived from the current observation. Only tap, long-press, and swipe have raw coordinate forms. Finding, waiting, typing, key presses, observation, and screenshots use their own typed inputs. For complete Python signatures and the corresponding Go methods, see the Driver and Locator references.

Drivers

Mobile driver

Models

How the driver works

The basics

Find

Tap

Type

Swipe

Keys

Observe

Wait

Screenshot

Semantic targets and coordinates

​The basics

Find

Tap

Type

Swipe

Keys

Observe

Wait

Screenshot

​Semantic targets and coordinates

The basics

Semantic targets and coordinates