What 277 Product Feedback Requests Asked Reviewers to Check
App Logic & Rules and User Flow were the leading specific topics in VCL’s published feedback-request sample. These are review requests, not confirmed defects.
“General feedback” was the largest topic in VCL’s published request sample. Among specific topics, App Logic & Rules led with 48 requests, followed by User Flow with 45.
Those two categories together accounted for 93 of the 277 requests in the shown topics, or 33.6%. The leading specific requests concerned how a product works and how people move through it—not simply its visual polish.
The topics selected for review
| Primary request topic | Requests | Share of 277 requests in shown topics |
|---|---|---|
| General feedback | 67 | 24.2% |
| App Logic & Rules | 48 | 17.3% |
| User Flow | 45 | 16.2% |
| Polish & Feel | 26 | 9.4% |
| UI/UX Design | 23 | 8.3% |
| Onboarding & First-Run | 18 | 6.5% |
| SEO & Discovery | 18 | 6.5% |
| Feature Ideas | 10 | 3.6% |
| Conversion | 9 | 3.2% |
| Accessibility | 7 | 2.5% |
| Security & Privacy | 6 | 2.2% |
Each request has one primary topic, but a project may have several requests. These are not 277 distinct builders, and the percentages do not use all 1,254 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 277 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 v7: feedback topics, cutoff September 11, 2026 at 09:40:56 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.