Datasets:

Modalities:
Text
Formats:
csv
Size:
< 1K
ArXiv:
License:
Xu0307 commited on
Commit
a6a1109
·
verified ·
1 Parent(s): 1dc1fc0

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +8 -7
README.md CHANGED
@@ -8,16 +8,17 @@ Mobile World is a substantially more challenging mobile-use benchmark designed t
8
 
9
  The difficulty of Mobile World is twofold:
10
 
11
- 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.
 
12
 
13
- 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.
14
 
15
-
16
- ![Uploading image.png…]()
17
 
18
  In this dataset, we provide an overview of all task goals in our benchmark.
19
 
20
- - Githubhttps://github.com/Tongyi-MAI/MobileWorld
21
- - Project Pagehttps://tongyi-mai.github.io/MobileWorld/
22
- - arxivhttps://arxiv.org/abs/2512.19432
23
 
 
8
 
9
  The difficulty of Mobile World is twofold:
10
 
11
+ - 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.
12
+ - 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.
13
 
14
+ ![image](https://cdn-uploads.huggingface.co/production/uploads/63525c3a6cfb8f1498127a34/ndnkD2k9sEJrJrrYLzq-B.png)
15
 
16
+ 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.
17
+ ![image](https://cdn-uploads.huggingface.co/production/uploads/63525c3a6cfb8f1498127a34/mhurYcCzPg3Rv_MRrpjKy.png)
18
 
19
  In this dataset, we provide an overview of all task goals in our benchmark.
20
 
21
+ - Github: https://github.com/Tongyi-MAI/MobileWorld
22
+ - Project Page: https://tongyi-mai.github.io/MobileWorld/
23
+ - arxiv: https://arxiv.org/abs/2512.19432
24