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.

[Uber] Delay ride request notifications during active trips

Driver received new ride requests while still on an active trip, leading to distraction and a minor accident. Suggests delaying or muting these notifications until the current trip is closer to completion to improve safety.

Original Source

@Saiyed Abdal | 263 pts

Today I noticed a small but potentially serious product flaw on Uber I was in an Uber ride. About 15 minutes were still left, yet the driver kept receiving ride request notification sounds to accept the next trip. Those repeated alerts pulled his attention to the phone while we were stuck in traffic. He briefly looked down. Didn’t see the car in front, didn’t brake And lightly hit the vehicle in front. Thankfully, nothing serious happened. But this made me pause. When a system optimises aggressively for utilisation, it may unintentionally compromise safety. This isn’t about blaming drivers. This is about process design. A simple question for product teams: Should ride-acceptance nudges be muted or delayed until the current trip is within a safer completion window? Tiny UX decisions compound into real-world consequences. Sometimes, optimisation needs restraint.

Discussion

Loading comments...