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.

[Payum] Implement process flow concept for better payment predictability

The current payment flow is hard to predict and follow due to runtime execution and context-based decisions. The request is to introduce a process flow concept to clarify actions, their order, and provide a visual representation, moving beyond the single "purchase" process.

Original Source

@@makasim | 1 pts | 4/25/2017

Right now a lot of stuff is happening at runtime. The payment flow is hard to predict and follow. It is hard to say: 1. What actions were executed? 2. What was the order of those actions? 3. The decisions is heavily based on the context (payment details). 4. There is no a visual representation of the process. Do we need a redirect, or should we show a form. We do not know until we start executing the request. 5. Right now Payum support only one process and it is the purchase. Some gateways also support recurring payment but the implementation is not that good. The process flow could improve it. Recently we've been playing with [process virtual machines](https://github.com/formapro/pvm) and I realized that it could be a good fit for Payum. So I did a proof of concept. It shows how Paypal ExpressCheckout may look like. The code is here: https://github.com/formapro/pvm-demo/blob/master/src/AppBundle/Controller/PaypalController.php and the demo is here: https://pvm-demo.for

Discussion

Loading comments...