Talos
Try Talos

Practical Android automation

Give repetitive app workflows a clear goal.

These examples use Talos’s screen observation, Android actions, milestones, continuous tasks and per-task models. Adapt each goal to an app and device you can test.

Developers · demo preparation

Create test data through the app UI

You need a recognizable contact for a demo or app interaction, and entering the same details manually interrupts setup.

In Contacts, add Alex Morgan with the number 5550100. Confirm the saved contact appears in the list.

How Talos handles it

Talos opens the app, navigates to the form, fills the fields and looks for the saved contact. Milestones make each expected screen explicit.

Expected result and what to check

A test contact created through the visible UI, plus a run history to review. Use a disposable test profile and check for existing contacts before repeating the task.

QA · exploratory checks

Check a multi-screen Android app journey

You want to exercise a user journey before investing in a scripted test, or understand where navigation gets stuck.

In our demo app, find the item named Blue Notebook, open its details and add it to the basket. Stop when the basket shows Blue Notebook. Do not place an order.

How Talos handles it

Define checkpoints for search results, product details and the basket. The agent reads the current interface and chooses actions toward each checkpoint.

Expected result and what to check

An inspectable journey showing completed milestones or a failure to investigate. This is an example to adapt to your app, not a verified integration or a deterministic release test.

Developers · device preparation

Prepare visible device settings

Before a test session, you repeatedly navigate Android settings to establish the same starting conditions.

Open Android Settings, find Display and set screen timeout to 5 minutes if that option exists. Confirm the selected value; report failure if it is unavailable.

How Talos handles it

Talos can open Settings, read labels, scroll to the relevant control and verify its visible state. Define the desired value instead of a fixed pixel path.

Expected result and what to check

A reviewed starting configuration for your session. Available options vary by Android version and device; try the goal on your target device first.

Technical operators · recurring work

Revisit an app in continuous cycles

A workflow needs repeated attention, with context carried from the previous visit rather than a fresh manual start each time.

Open our test app and check the status of Demo Job. Read its current status and include it in the cycle summary. If nothing has changed, finish this cycle and wait.

How Talos handles it

Select continuous mode, a pause between cycles and, if needed, working hours such as Monday–Friday 9:00–17:00 (server time). After success, Talos schedules another cycle and carries forward a summary. Temporary problems such as an unreachable API or a disconnected phone are retried up to four times; Stop, a reached limit or a configuration error stops the task.

Expected result and what to check

Repeated UI checks with a per-cycle timeline and model-generated memory — not an exact event ledger. With a daily budget, the task waits for the next day once the budget is spent, and a notification can tell you when it stops, hits a limit or loses its phone.

Technical operators · one phone, several jobs

Run several tasks on one phone, each on the right model

A quick, frequent check and a longer multi-screen workflow need the same test device, but not the same model or budget.

Open our test app, go to the account screen and confirm that the profile name is Demo User. Report the name you see and change nothing.

How Talos handles it

Assign both tasks to the same phone. Give the quick check a lower-cost model with low effort and the multi-screen workflow a stronger model. Talos runs one task at a time per phone, in the order of their scheduled time, and each run records the model and effort it used.

Expected result and what to check

Two workflows on one device, with the model and cost of every run in the timeline, so you can compare the cost of completed tasks. Export a tuned task to a .talos-task.json file to reuse it on another phone or installation; the file holds the definition, not the device or run history.

Make the outcome observable

Good milestones tell the agent what to look for.

“Data is saved” leaves room for interpretation. “Alex Morgan appears in the contact list” gives the agent a visible condition to check.

Start with a short task, inspect the first run and refine the instructions. UI changes, permissions and model decisions can affect completion.

Create your first task →
Example task One-time run

Your goal

“In Contacts, add Alex Morgan with the number 5550100. Confirm the saved contact appears in the list.”

  1. 01
    Open the contact form

    Success: name and phone fields are visible.

  2. 02
    Enter the contact details

    Success: the fields show Alex Morgan and 5550100.

  3. 03
    Save and check the result

    Success: Alex Morgan appears in Contacts.

40 iterations15 minutes$0.50 budget threshold

Illustrative task definition, not a recorded run. The final model call can exceed the budget threshold.

Start with one workflow

Give your next repetitive Android task to Talos.

Try it on your own emulator or phone. Bring an ADB connection, a clear goal and your model provider.

Get a free trial key Read the setup guide

No card required for the licence trial. AI usage is billed separately.