- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper introduces MobileViews, a large-scale mobile GUI dataset collected from over 30K Android apps using SoC clusters, VLM-assisted traversal, and selective human intervention. The authors also construct MobileViewsIDM to evaluate the dataset for GUI transition understanding.
Critical strengths
- The scale and app diversity are strong. MobileViews contains over 1.2M screenshot–view hierarchy pairs from more than 30K apps and covers multiple screen resolutions.
- The downstream evaluation is reasonably broad. The authors evaluate three VLMs under multiple agent configurations and compare MobileViewsIDM against Rico and AndroidControl.
- The sample-size analysis in Figure 5 is useful because it shows that the gain is not explained only by having more training samples.
Critical weaknesses
- Figure 2(b) presents a relatively simple UI transition graph, but real mobile interaction graphs can be much more cyclic due to back/navigation actions and varying starting states. It would be helpful to clarify how the actual UTG is constructed and whether this figure is only a simplified illustration.
- Table 2 is intended to demonstrate the value of MobileViews as training data, rather than model superiority. The sample-size analysis in Figure 5 is useful, but the comparison still mixes dataset size, app diversity, and data quality. Can the authors better isolate which factor contributes most to the gain?
- The downstream evaluation mainly focuses on inverse dynamics prediction. While this is a reasonable use of the collected trajectories, it is still only one capability.
Questions for authors
- Are system UI elements such as time, battery, signal, and navigation bars retained in the raw screenshots? If so, are they considered in the dataset diversity analysis?
- How much human effort is required by the fallback stage, e.g., interventions per app or operator time per successful traversal?
3 comments
Thank you for the response. The UTG and system-bar clarifications resolve W1 and Q1, and the AndroidControl results are a useful addition. However, my main concern (W2) remains open: the analysis isolating app diversity from sample count is deferred to a future revision. Similarly, the AndroidControl evaluation shows that IDM training helps, but without Rico/AndroidControl-trained baselines it does not show that MobileViews is a better training source, and the gain shrinks to ~1.5pt at full scale. I appreciate the effort and continue to view the paper positively, so I will keep my score at 3.
Thank you for taking the time to read our response and follow up. We sincerely appreciate your positive assessment of MobileViews, especially your recognition of its scale and app diversity. Your questions about the UTG, GUI deduplication, and human intervention have also helped us improve the clarity of our paper. We are glad that our clarifications addressed your earlier concerns about the UTG and system bars.
We also appreciate your suggestions for further evaluation. We will do our best to include an analysis of app diversity at matched sample counts and additional AndroidControl results from checkpoints trained on different datasets in the next revision. We hope to further explore the potential of MobileViews as an open-source resource for mobile GUI research. Thank you again for your time, positive feedback, and continued support of our work.
Response to Reviewer GLF7
We thank the reivewer for the thoughtful reviewers. We respond to the concerns as follows.
W1: Distinguishing between an actual UTG and the demonstrated one in Figure 2(b)
Figure 2(b) shows a simplified version of the complete UTG we collected for the “Mood Tracker” app. The complete UTG contains 213 unique GUI states and 312 directed edges. As the reviewer said, an app’s complete UTG contains more cycles than the figure shows because both forward actions (e.g., click and scroll) and backward actions (e.g., navigate_back) can lead to previously visited states.
W2: Contribution to model performance gains
We agree with the reviewer that Table 2 shows the overall benefit of MobileViewsIDM, yet Figure 5 shows that MobileViewsIDM can achieve higher IDM accuracy with fewer training samples compared to other datasets. This suggests that training-set size alone does not explain the gains. Broader app coverage is one plausible contributor. For example, PhoneWorld [1] found that training on more apps improved AndroidWorld performance, while ProCUA-SFT [2] found that balancing training trajectories across app combinations raised performance on OSWorld. In the next revision, we will analyze how IDM accuracy changes with the number of distinct training apps while holding the sample count fixed.
[1] Liu, et al. “PhoneWorld: From Real-App Trajectories to Dynamic and Verifiable Environments for Phone-Use Agents.” arXiv preprint arXiv:2605.29486, 2026. [2] Jung, et al. “ProCUA-SFT Technical Report.” arXiv preprint arXiv:2606.17321, 2026.
W3: IDM is only one evaluated capability
We have additionally evaluated the trained checkpoints of different data scales on GUI interaction tasks. Please refer to Common Response #3.
Q1: Details on dataset diversity analysis
The collected GUI screenshots are as-is in MobileViews, without removing system UI elements. For the dataset diversity analysis, we compute a 64-bit perceptual hash for each full screenshot and treat two screenshots as visually similar if the Hamming distance between their hashes is at most 5. Under this criterion, screenshots that differ only in their system UI bars are typically classified as visually similar. We selected this heuristic threshold after a separate check performed before deduplication, in which 3,197 of 3,198 same-app screenshot pairs that differed only in the status bar met the similarity criterion.
Q2: Human intervention effort
Please refer to Common Response #2.
We hope the above responses could address the reviewer’s concern, and we are willing to talk about any further feedback.