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.

[Baby Buddy] Add API coverage for site settings

User requests API coverage for the "Site Settings" page (/settings/) to allow programmatic control over settings, for example, muting a device's speaker during certain times.

Original Source

@@skjdghsdjgsdj | 0 pts | 9/20/2024

It would be helpful if there was API coverage for the "Site Settings" at `/settings/`: <img width="591" alt="Screenshot 2024-09-20 at 10 54 17 AM" src="https://github.com/user-attachments/assets/d81eac6e-a2b9-4d86-8ea2-db32102f099a"> My use case: my [BabyPod](https://github.com/skjdghsdjgsdj/babypod-software) device, which interfaces with Baby Buddy, has a piezo speaker for beeps and tones. I'd like to mute the speaker during certain times of day, and what makes sense to me is "mute the speaker outside of nap times" so it's quiet during the night for normal sleep periods. If I could make an API call to Baby Buddy to ask it what is considered a nap timeframe vs. sleep, then Baby Buddy can authoritatively define those times. In my particular case, just read coverage for `/settings/` is all I need, but perhaps there are cases for write coverage as well.

Discussion

Loading comments...