atlas

Research map / Multi-agent systems and games / LLM agents

AndroidWorld: A Dynamic Benchmarking Environment for Autonomous Agents

ICLR 2025 · Multi-agent systems and games › LLM agents · approach: GUI agent memory and trajectories · 2 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Introduces AndroidWorld, a dynamic, reproducible Android environment with 116 parameterized tasks across 20 apps (plus 92 MobileMiniWoB++ tasks) and a multimodal agent M3A, reporting that the best agent completes 30.6% of tasks versus 80% for humans.

Problem

Evaluating autonomous computer-control agents on mobile devices lacks realistic, reproducible benchmarks with automated outcome-based rewards; existing mobile benchmarks are small or use static test specifications.

Approach

Use Android system state (adb-accessible databases, files, settings) as durable reward signals and randomly parameterize tasks with seeds, so each task has initialization, success checking, and teardown logic that remains valid across many task instantiations.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
Add M3A's guidelines and reflection mechanisms compared with M3A-Simple (ablation)M3A with GPT-4 Turbo on AndroidWorld · AndroidWorldsuccess rate: 19.8% vs 30.6%Helped
Add M3A's guidelines and reflection mechanisms compared with M3A-Simple (ablation)M3A with GPT-4 Turbo on MobileMiniWoB++ · MobileMiniWoB++success rate: 67.7%No clear effect
Use SoM screen input in addition to the accessibility tree instead of accessibility-tree-only input (ablation)M3A with GPT-4 Turbo · AndroidWorldsuccess rate: 30.6 -> 25.4Hurt
Use SoM screen input in addition to the accessibility tree instead of accessibility-tree-only input (ablation)M3A with GPT-4 Turbo · MobileMiniWoB++success rate: 59.7 -> 67.7Helped
Use SoM screen input in addition to the accessibility tree instead of accessibility-tree-only input (ablation)M3A with Gemini 1.5 Pro · AndroidWorldsuccess rate: 19.4 -> 22.8Helped
Use SoM screen input in addition to the accessibility tree instead of accessibility-tree-only input (ablation)M3A with Gemini 1.5 Pro · MobileMiniWoB++success rate: 57.4 -> 40.3Hurt
Evaluate M3A across different task-parameter seeds rather than reporting only a single seedM3A with GPT-4 Turbo and accessibility-tree input · AndroidWorldsuccess rate: 27.6%, 26.3% and 33.2% (mean 29.0%)Mixed
Change device and OS from Pixel 6 (Android 13) to Pixel 5 (Android 12)M3A · AndroidWorldsuccess rate: 28.4%Mixed
Use M3A instead of SeeActGPT-4 Turbo agent on AndroidWorld · AndroidWorldsuccess rate: 15.5 -> 30.6Helped

Surprising findings

Limitations

Experimental setup

Datasets: AndroidWorld tasks MiniWoB++

Benchmarks: AndroidWorld MobileMiniWoB++

Metrics: success rate

Baselines: SeeAct M3A-Simple Human

Builds on: ReAct Reflexion SeeAct Set-of-Mark AndroidEnv MiniWoB++

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy