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.

[Mockphine] Add route passthrough and strict 404 options

User wants to mock blocked backend routes while allowing passthrough for ready routes and strict 404 behavior for disabled routes in Mockphine, a local mock API server app.

Original Source

@u/cuongnt3010 | 0 pts | 3/14/2026

I kept running into the same local dev problem: 90% of the backend was usable, but one unfinished or unstable route would break the whole UI flow or make QA hard to reproduce consistently. I tried MSW, Mockoon, Postman mock servers, and custom scripts. They all helped, but I kept wanting a faster workflow for one specific situation: \- mock the blocked route \- passthrough the routes that are already ready \- turn a route off entirely when I want strict 404 behavior \- see exactly what served the response \- simulate delay/failure without rebuilding the setup That frustration is what pushed me to build Mockphine, a macOS app for running a local mock API server with per-route mock / passthrough / disabled modes, strict 404 or passthrough fallback, and a Live View that shows served-by, status, and duration. Not claiming this is the only way to solve it. I’m mostly curious how other frontend teams here handle the "backend is mostly ready, but the last 1-2 routes keep blocking local work" problem. Are you using MSW in-app, Mockoon/Postman, proxy scripts, or something else?

Discussion

Loading comments...