Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

Set up a target device: an Android emulator via Android Studio's Virtual Device Manager, or an iOS Simulator via Xcode
Install Maestro (CLI or Maestro Studio) per the official quickstart
Create a Flow: a YAML file starting with an appId: header, a --- separator, then a list of step commands
Add commands such as launchApp, tapOn, inputText, and takeScreenshot to drive and verify the UI
Run the flow locally via Maestro Studio's Run button, or via the Maestro CLI for CI/CD
Split larger scenarios into modular, reusable flows per Maestro's Flows guide

Known gotchas

Maestro's documented Android emulator support targets specific API levels; check the current compatibility list before assuming the newest API level works
If Xcode was installed without ever being opened, iOS simulators won't appear until xcodebuild -runFirstLaunch is run
Flows are declarative YAML by design; real conditional/programmatic logic requires dropping into evalScript/runScript JS rather than native YAML constructs

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Write and run a basic Maestro flow to test a mobile app's UI

Steps

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?