- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper presents GUI-Drop, a training-free method that prunes visual tokens for GUI agents. It keeps more tokens where the screen changed. At 20% of tokens, it clearly beats other pruning methods on AndroidWorld.
Critical strengths
(1) The gains over training-free baselines are large at low budgets. At 20% retention, UI-Voyager reaches 59.5% on AndroidWorld, versus 43.1% for the best baseline.
(2) The design fits GUI agents, and the cost report is honest. It uses screen changes and previous-action attention. It reports prefill, decode, and total time, not only FLOPs.
Critical weaknesses
(1) The end-to-end gain is small and costs accuracy. At 40% retention, per-step time only falls from 6.31 s to 5.78 s (1.09x), because prefill is about 11% of step time and decoding dominates. UI-Voyager also drops from 80.2% to 75.9% on AndroidWorld, and latency is measured only with eager attention.
(2) The state-transition component is weakly supported. Removing cross-step relevance or dynamic priority costs only 1.4 and 1.0 points, measured offline on AndroidControl, not on AndroidWorld. AndroidWorld results come from a single run over 116 tasks, so the 46.6% versus 43.1% gain over unpruned Qwen3-VL-8B is about four tasks.
Questions for authors
(1) Can you report AndroidWorld success over at least three runs with variance, and run the component ablation on AndroidWorld? A split by transition size would show when the transition signal helps.
(2) How does GUI-Drop compare with a lower-resolution screenshot of the same token count, and what is the per-step latency with FlashAttention 2? Were the 0.996 similarity threshold and the dynamic weight of 2.5 tuned on AndroidWorld tasks?