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.

[VerdictCouncil Frontend] Connect Intake Form to Real Upload and Case Creation API

Wire the `AppealIntakePage.jsx` to make real API calls for case creation (`POST /cases/`) and document uploads (`POST /cases/{id}/documents`). This includes displaying inline per-file upload progress and error handling, while preserving demo mode behind a feature flag.

Original Source

@@douglasswm | 0 pts | 4d ago

## Context Wires `AppealIntakePage.jsx` to make real API calls: `POST /cases/` to create the case, then `POST /cases/{id}/documents` for each file, with per-file upload progress displayed inline. The demo mode path is preserved behind a feature flag. ## Requirements * Submission calls `POST /cases/` and receives a real `case_id` from the backend * Each file is streamed to `POST /cases/{id}/documents` with inline progress indicator * Upload errors are shown inline per file (not as a generic modal) * Demo case scenario (used for QA walkthroughs) routes through a feature flag, not the real upload path ## Acceptance criteria - [ ] Successful submission produces a real `case_id` from the backend (not a mock UUID) - [ ] Per-file upload progress is shown during the documents upload - [ ] File-level errors (e.g. unsupported type, size exceeded) are shown inline beside the file - [ ] Demo mode feature flag bypasses the real upload path - [ ] After successful upload, the UI transitions to t

Discussion

Loading comments...