- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper presents PhoneCLI, a framework that compiles the navigation structure of mobile apps into deterministic callable commands. It first explores an app offline to build a semantically annotated screen graph, then converts navigation paths into replayable action sequences. At runtime, an LLM selects and verifies a command, which is executed without additional VLM calls, and tasks not covered by the compiled commands fall back to the standard GUI agent.
Critical strengths
1.Stable and repetitive navigation can be compiled into deterministic commands, which is a natural fit for mobile workflows with fixed navigation paths, such as system settings. This avoids repeatedly invoking the VLM for the same navigation steps.
2.PhoneCLI is model-agnostic and can be attached to different GUI-agent backbones without retraining them.
Critical weaknesses
The scalability of the command catalog remains unclear. The paper already observes a substantial performance drop when the map budget increases from 50 to 100 screens, due to increased routing ambiguity. Since real applications can contain far more screens and navigation paths than the explored depth-3, 50-screen maps, it is unclear how PhoneCLI would scale to substantially larger apps.
Questions for authors
Could the authors clarify how the “guaranteed floor” claim is consistent with the error analysis, where PhoneCLI loses 10 tasks that are solved by the VLM-only baseline due to routing or command-selection errors?
Reminder: Please Review Author Rebuttals and Participate in Discussions
Dear Reviewers,
Thank you for your time on the reviews. The authors have now submitted their rebuttals, and I encourage you to read their responses and participate in the discussion.
Please consider whether the rebuttals address your concerns and, where clarification is still needed, engage with the authors through the discussion forum. I also encourage you to exchange perspectives with your fellow reviewers and update your review or rating if appropriate.
Your participation will help ensure a thorough and fair evaluation of each paper. Thank you again for your time and effort.
Best regards,
AC