|
|
--- |
|
|
license: apache-2.0 |
|
|
--- |
|
|
|
|
|
# MobileWorld: Benchmarking Autonomous Mobile Agents in Agent-User Interactive and MCP-Augmented Environments |
|
|
|
|
|
Mobile World is a substantially more challenging mobile-use benchmark designed to better reflect real-world mobile usage. It comprises 201 tasks across 20 applications, featuring long-horizon, cross-app tasks, and novel task categories including agent-user interaction and MCP-augmented tasks. |
|
|
|
|
|
The difficulty of Mobile World is twofold: |
|
|
|
|
|
- Long-horizon, cross-application tasks. Mobile World tasks require on average 27.8 completion steps, nearly twice as many as 14.3 steps required in AndroidWorld. Moreover, 62.2% of tasks involve cross-application workflows compared to only 9.5% in AndroidWorld. |
|
|
- Novel task categories. Mobile World extends beyond standard GUI manipulation by introducing (1) agent-user interaction tasks (22.4%) that evaluate an agent's ability to handle ambiguous instructions through collaborative dialogue, and (2) MCP-augmented tasks (19.9%) that require hybrid-usage of GUI navigation and external tool invocations via the Model Context Protocol. |
|
|
|
|
|
 |
|
|
|
|
|
The system architecture of Mobile World consists of two main components. Left: the host machine is where GUI agents receive task instructions and optionally interact with users for clarification, then choose between GUI actions or MCP tool calls to complete tasks. Right: the docker environment contains an isolated Android ecosystem with emulators, self-hosted app backends, and an evaluator that verifies task completion through text matching, backend database, local storage, and app callbacks. |
|
|
 |
|
|
|
|
|
In this dataset, we provide an overview of all task goals in our benchmark. |
|
|
|
|
|
- Github: https://github.com/Tongyi-MAI/MobileWorld |
|
|
- Project Page: https://tongyi-mai.github.io/MobileWorld/ |
|
|
- arxiv: https://arxiv.org/abs/2512.19432 |
|
|
|
|
|
|
