GapQuery

That's a sharp observation. Review velocity is exactly the signal that catches traction before keyword tools do, and the cross-ecosystem version (Chrome Web Store gap that Shopify already solved, etc.) is where the most non-obvious opportunities hide. We capture daily snapshots of app and category metrics, so the underlying data is there, and one of the cross-ecosystem pattern modes already uses velocity disparity under the hood. But you're right that there's no clean "ranked by review velocity" top-level filter yet. That's a good way to expose what's already in the data. Putting it on the build list.

You're correctly intuiting how it works. The build/skip/maybe verdict comes out of a 6-area research pass (market validation, competition, revenue, technical feasibility, keywords, GTM) and the prompt does weight "demand evidence" (review counts, install proxies, complaints in existing reviews) over "this category looks empty." Disruption targets are the strongest input because reviewers are already paying for something broken. Pure category-gap detection is the weakest input precisely because false positives hide there: empty categories are often empty for a reason. Surfacing that distinction more clearly in the verdict output is on the list.

Agreed. We have a public ideas page at /ideas that browses the actual database (no signup), but the landing page itself doesn't pull a sample onto it or link to it prominently enough. Adding 2 or 3 example cards above the fold would do more work than the static feature list does today. Doing this week.