What 600 Product Feedback Requests Asked Reviewers to Check
User Flow and UI/UX Design were the leading specific topics in VCL’s published feedback-request sample. These are review requests, not confirmed defects.
Updated November 1, 2026. This article uses dataset v10, with a November 1 cutoff and measurements recorded through October 31. This is a new frozen edition; changes in sample membership, recorded classifications and measurement timing are not within-project growth.
“General feedback” was the largest topic in VCL’s published request sample. Among specific topics, User Flow led with 94 requests, followed by UI/UX Design with 68.
Those two categories together accounted for 162 of the 600 requests in the shown topics, or 27.0%. The leading specific requests concerned how people move through a product and its interface. App Logic & Rules followed with 64 requests (10.7%).
The topics selected for review
| Primary request topic | Requests | Share of 600 requests in shown topics |
|---|---|---|
| General feedback | 111 | 18.5% |
| User Flow | 94 | 15.7% |
| UI/UX Design | 68 | 11.3% |
| App Logic & Rules | 64 | 10.7% |
| Polish & Feel | 57 | 9.5% |
| Onboarding & First-Run | 53 | 8.8% |
| SEO & Discovery | 41 | 6.8% |
| Conversion | 24 | 4.0% |
| Feature Ideas | 20 | 3.3% |
| Copy & Messaging | 19 | 3.2% |
| Security & Privacy | 13 | 2.2% |
| Performance | 12 | 2.0% |
| Accessibility | 11 | 1.8% |
| Mobile Experience | 8 | 1.3% |
| Bug Testing | 5 | 0.8% |
Each request has one primary topic, but a project may have several requests. These are not 600 distinct builders, and the percentages do not use all 1,502 projects in the report as their denominator.
Requests are not a defect inventory
A builder asking about onboarding may be testing a concern, seeking confirmation or following a suggested prompt. The categories are not confirmed defects, and VCL’s suggested defaults influence the selections. Small counts for security or accessibility do not establish that builders ignored those issues or that their products were safe or accessible.
The publication rules also matter. A topic needs at least five requests from five projects to appear. Smaller groups and their combined remainder are withheld, so 600 is the total for the published topics—not all requests. Active and archived requests qualify, but requests created or updated after the cutoff are excluded because their earlier state cannot be reconstructed.
This table captures selected review topics in a VCL snapshot. It does not measure whether reviewers answered the questions, whether builders found the responses useful or whether the products subsequently improved.
Data and source. State of Vibe Coding 2026, Dataset v10: feedback topics, cutoff November 1, 2026 at 00:00 UTC. See the edition’s methodology for request eligibility and privacy rules.
Read the full State of Vibe Coding report for the project, tool and public-web measurements that accompany this feedback snapshot.