Skip to content

Documentation

appdyno drives and measures iOS and Android apps from your Mac. New here? Start with the README.

Each one takes you through a task.

guide read it to
Connecting a client join appdyno to your MCP client and get a phone ready, signing included
Flows record what an agent did, replay it with no model, run it in CI
Evidence leave a video, a report, a network log or a visual diff behind
Measuring performance measure an app, keep a baseline, and fail a pull request that makes it slower

Look things up here.

reference what it holds
Tools every tool and its inputs, and what each platform can and cannot do
How the tools were tested what each tool was run on, and what the runs showed
Command line every command, and the server’s flags and variables
Library driving a device from TypeScript
The window and the hub the live window and the hub: every control, pane and state, and their limits
How the window works how the picture and input travel, the wire, and what was run on which device
Performance what each measure reads on each device, the gate, and how fast each call is
How the measures were validated each measure against a known cost: on which device, on which day, at what load
Protocol the bytes between the host and a device’s agent
CI and releases every check, the device suites, how a release is made
The strict lint how the code meets a type-checked rule that leaves a choice

Each one runs as it is.

example try it to
Shop find the crash in a checkout with an agent, then keep it fixed with a flow
perf-gate.yml fail a pull request that makes the app slower, on a GitHub runner

Architecture says how the parts fit and why, for someone about to change them.

CONTRIBUTING says how to set up, run the checks and send a change. SECURITY says what appdyno can reach, and how to report a problem.

This site counts visits with Cloudflare Web Analytics, without cookies.