Waymark / Routes / appium.io Install and use the Appium UiAutomator2 driver to automate an Android app
domain: appium.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Install the Appium server: npm install -g appium Install the Android driver (Appium 2 ships with zero bundled drivers): appium driver install uiautomator2 Optionally install a plugin the same way, e.g. appium plugin install images, then enable it at server start Extensions are tracked under the APPIUM_HOME directory (defaults to ~/.appium) in an extensions.yaml manifest Start the server (appium) and open a session with capabilities including automationName: UiAutomator2, platformName: Android Write the test with an Appium client library per the JS/Python/Java/Ruby quickstart docs Known gotchas Appium 2.x ships a bare core with no bundled drivers, so the server cannot automate anything until a driver is explicitly installed Setting APPIUM_HOME lets you keep separate driver/plugin versions side by side, but only npm-based extension management is officially supported Forgetting APPIUM_HOME can cause Appium to look in the wrong location for installed extensions
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