Update README.md
Browse files
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 |
-
|
| 14 |
|
| 15 |
-
|
| 16 |
-

|
| 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 |
+

|
| 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 |
|