RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Home Score] Build Stage 1 Preference Intake Form

Develop the Stage 1 preference intake form, designed to be completed in under 3 minutes. The form should be divided into two sections: 12 factors for neighborhood preferences (e.g., area type, school quality, commute) and 12 factors for physical house preferences.

Original Source

@@gshriivanth | 0 pts | 2/28/2026

## Overview Build the Stage 1 preference intake form. Must be completable in under 3 minutes. Divided into two sections: neighborhood preferences (12 factors) and physical house preferences (12 factors). ## Depends On - #12 (frontend setup) ## Neighborhood Preference Inputs | # | Factor | Component | Options | |---|---|---|---| | 1 | Area Type | Radio group | Urban / Suburban / Rural | | 2 | Public School Quality | Slider | Low / Medium / High | | 3 | Commute Destination | Text input + Slider | Address field; max commute 15/30/45/60+ min | | 4 | Safety / Crime Level | Slider | Low / Medium / High priority | | 5 | Walkability & Amenities | Slider | Low / Medium / High | | 6 | Public Transit Access | Radio group | Not needed / Helpful / Essential | | 7 | Family-Friendliness | Radio group | Single / Couple / Family with kids / Empty nester | | 8 | Nightlife & Dining | Slider | Low / Medium / High | | 9 | Green Space & Parks | Slider | Low / Medium / High | | 10 | Neighborhood Stability

Discussion

Loading comments...