- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper proposes PQ Score, a reference-free metric for UI-to-Code difficulty based on round-trip consistency. PQ Score is the normalized tree edit distance between the DOM tag trees of P and Q. Using this metric, the authors build the ABPQ pipeline, which filters 4.77M crawled UI screenshots through hierarchical PQ filtering, VLM-based quality control, and manual review. The result is ABPQ-FULL (500 samples) and ABPQ-HARD (200 samples), with reference HTML kept for evaluation. Experiments on proprietary and open-source models show lower scores on ABPQ than on Design2Code, Design2Code-HARD, and Vision2Web for most metrics. The authors also analyze correlations between PQ Score and existing automatic metrics and human judgments.
Critical strengths
- Timely problem. Existing UI–HTML benchmarks constructed from open webpages may have data leakage issues.
- New dataset. The paper proposes a new UI2Code dataset for future research.
Critical weaknesses
-
Unclear motivation. The paper’s main argument for scalability is that the pipeline needs only screenshots, but the authors crawl about 7M UI–HTML pairs and keep the HTML as the reference. If the underlying code is already available, why not directly analyze the source HTML? The screenshot-only setting is described, but it would be better to construct it this way from scratch.
-
The proposed PQ score metric lacks rigor. is unclear whether PQ Score is meant to be a filtering tool or an evaluation metric? If it is proposed as a better metric, it should show either (a) better discriminability or (b) better alignment with human judgment. The current evidence supports neither: a) Table 4 shows a strong correlation between PQ score and existing metrics b) Table 5 shows only moderate alignment with human rankings, even worse than some existing metrics
-
The problem scope in static pages may limit realistic application. The benchmark covers only static screenshots. Modern frontend development depends heavily on interactivity and dynamic state. Many of the user tasks listed in Table 9 (e.g., Interactive Use, Shopping, Booking, Gameplay) are interactive by nature, yet only their static appearance is evaluated.
Questions for authors
- Why does the benchmark not involve dynamic webpages?
- The construction process includes many filtering steps from the original 4M to 500. This limited filtering process may introduce bias in the benchmark. How do you ensure the filtering is representative and doesn't lose information from the current web landscape?
- In terms of the benchmark statistics, I'm not sure whether domain coverage, page type, and user task are representative enough for indicating website complexity. The usual metrics are DOM depth, node count, and CSS complexity, etc. (such as in design2code)
- Can you explain why the PQ score is a better metric than existing ones?