mobile-next/mobilewright

What it solves

Mobilewright is a framework for automating mobile devices (iOS and Android), designed to replace complex setups like Appium or Detox. It provides a unified, cross-platform API that allows developers to write tests or automation scripts that work across different mobile operating systems without needing to write platform-specific code for every action.

How it works

Built on top of mobilecli, Mobilewright uses a Playwright-inspired architecture. It interacts with the device's accessibility tree—a deterministic, semantic representation of the UI—rather than relying on raw coordinates or vision models. This allows it to perform actions like tapping, filling text, and swiping with high reliability.

For hybrid apps, it can bridge into the DOM of a WebView to provide a full Playwright-compatible Page API for web content embedded within a native app.

Who it’s for

• QA Engineers and Developers: Those who want a Playwright-like developer experience for mobile automation with built-in auto-waiting and semantic locators.
• AI Agent Developers: Those building agents that need to control mobile phones. Because it exposes the accessibility tree, agents can interact with the device using token-efficient, readable semantic actions instead of processing screenshots.

Highlights

• Playwright-style API: Uses familiar methods like getByRole and expect for element discovery and assertions.
• Auto-waiting: Actions automatically wait for elements to be visible, enabled, and stable before interacting.
• Cross-platform: A single API for both iOS and Android devices, simulators, and emulators.
• AI-Ready: First-class support for AI agents via the accessibility tree, removing the need for vision models.
• Hybrid App Support: Seamlessly transitions from native automation to web automation within WebViews.
• Zero Config: Automatically discovers booted simulators and emulators.