Benchmark definition
MobileMiniWoB++
2024 mobile adaptationApplicability does not mean evaluated; benchmark result/model score data is outside this UI contract.
About
- Description
- MobileMiniWoB++
- What it measures
- MobileMiniWoB++
- Comparison guidance
- Not published
- Intended difficulty
- Not published
Not recorded for this benchmark: what it does not measure, why it matters, motivation, gap addressed.
Classification
- Categories
- Mobile AgentComputer UseAgentic
- Domains
None recorded
- Evaluation style
None recorded
Structure
1 component. Applicability can differ between them.
Components
- Standard 62-task evaluation subsetSubset
Tasks
Metrics
What a result on this benchmark would be reported as. ctxdex does not carry results.
| Metric | Role | Direction | Unit |
|---|---|---|---|
Task Success Rate Canonical Batch-2 metric code TASK_SUCCESS_RATE; benchmark-specific formula/parameters remain on benchmark_metric and methodology records. | Primary | Higher is better | Percent |
Methodology
None recorded
Evaluation environment
What the benchmark's harness provides and allows. These are properties of the environment, not model requirements, and applicability does not test for them.
- Actions
- Coordinate pointer actionKeyboard input
- Observations
- ScreenshotAccessibility tree
- Session
- Turn based actions
- Reset
- Task initialize teardown
- Network
- None
- State persists per
- Episode
- Grounding
- Mixed
- Evaluation style
- Not recorded
- Environment summary
- Not published
Model requirements
Required conditions decide applicability. Relevant ones describe what the benchmark exercises and decide nothing.
Required · decides applicability
Relevant · informational
CTXDEX models
51 of the 58 active, preview, experimental models meet this benchmark’s recorded requirements, at some scope. Applicable means the requirements are met, not that the model was evaluated.
View all 51 applicable models →- Applicable · full
- 51
- Applicable · components
- 0
- Applicable · scenarios
- 0
- Conditionally applicable
- 0
- Not recorded
- 7
Counted over 58 models in the default lifecycle scope (active, preview, experimental).
Every required condition, for the whole benchmark, is recorded as supported. Each line is one recorded condition and why it counts.
Every one of the 1 required conditions is recorded as supported.
MODALITY:INPUT:TEXTthe catalogue records SUPPORTED for TEXT (input)
Every one of the 1 required conditions is recorded as supported.
MODALITY:INPUT:TEXTthe catalogue records SUPPORTED for TEXT (input)
Applicability/relevance ordering only; never a performance ranking.
Scale
- 62Standard evaluation subsetTotal · Exact
- 92TaskTotal · Exact
- 62TaskStandard 62-task evaluation subset · Exact
Data and access
Coverage
- Languages, regions
None recorded
- Coverage summary
- Not published
Limitations
None recorded
Lineage
- Family
- FamilyMiniWoB
- Related
- Other definitions in family
- MiniWoB 2017 SupersededMiniWoB++ maintained Active
- Changes
None recorded
Sources
- https://github.com/google-research/android_world ↗Official repository · Benchmark official
- https://arxiv.org/abs/2405.14573 ↗Research paper · Original creator
Freshness
- Content version
- B2-1.0
- Last reviewed
- 2026-09-23
- Refresh model
- Unknown
- Time sensitivity
- Unknown
- Benchmark data
- c40cccac878af5d0
13 contract fields are empty for every benchmark in this release and are not shown: applicability groups, conditional requirements, feature requirements, model relevance domains, required capabilities, openness summary, reference artifacts, interaction protocols, tool protocols, benchmark last major refresh at, short name, target expertise level, target population.