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), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Oppia] Add debounce to search input to prevent search triggering on every keystroke

Currently, the search functionality triggers on every key press while typing in the search bar in Language selection on translation page. This causes multiple rapid search requests as the user types. Introduce a debounce mechanism so that the search request is triggered only after the user pauses typing for a short duration (e.g., 300–500 ms).

Original Source

@@AmiyaPiyush1 | 0 pts | 3/12/2026

### Is your feature request related to a problem? Please describe. Currently, the search functionality triggers on every key press while typing in the search bar in Language selection on translation page. This causes multiple rapid search requests as the user types. ### Describe the solution (or solutions) you'd like Introduce a debounce mechanism so that the search request is triggered only after the user pauses typing for a short duration (e.g., 300–500 ms). This will ensure that the search runs only after the user finishes typing a word or pauses briefly. ### Describe alternatives you've considered and rejected NA ### Additional context https://github.com/user-attachments/assets/b4e4c36c-cd08-4b45-9c74-203e317f0024

Discussion

Loading comments...