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.

RequestHunt

Loading request...

[Figma] Improve asset export workflow | RequestHunt

[Figma] Improve asset export workflow

| | , , ,

by @u/Quick-Intention745 | 3/9/2026 | submitted by AutoCollector

[view original source]

User is struggling with exported SVGs being messy or Figma layouts not translating well to Flexbox/Grid. They are looking for specific plugins or handoff tools that can help streamline this process.

Original Source

@u/Quick-Intention745 | 0 pts | 3/9/2026

Hi everyone, I’m currently trying to bridge the gap between high-end visual design and technical implementation. My current toolkit is: Design/UI: Figma & Illustrator Motion/Video: After Effects & Premiere Pro Dev: HTML, CSS, and Python While I love the "Full-Stack Designer" path, I’m hitting a wall with mental context switching and time management. I feel like I’m constantly "re-learning" syntax or shortcuts every time I switch tools. I have a few specific questions for those of you who juggle both pixels and code: 1. The "Logic Shift" Problem How do you structure your deep-work sessions? I find that if I spend the morning in After Effects (keyframing and motion), my brain is completely fried for Python logic or CSS architecture in the afternoon. Do you split your week into "Design Days" and "Code Days"? 2. The Asset Pipeline (Figma -> CSS/SVG) For those of you using Illustrator and Figma, what’s your cleanest way to move assets into HTML/CSS? I’m struggling with exported SVGs being "messy" or Figma layouts not translating well to Flexbox/Grid. Are there specific plugins or handoff tools you swear by? 3. Where does Python fit in? I’m learning Python to automate repetitive tasks (or maybe for Generative Art/Data Viz). If you use Python in a design workflow, are you using it for Scripting in AE (ExtendScript/Python), or more for backend/data-heavy web projects? How do you keep your scripts organized alongside your design files? 4. Avoiding Burnout How do you maintain a "Master" level in all of these? I’m worried about becoming a "Jack of all trades, master of none." Should I pick one "Lead" tool and keep the others as "Support" tools? "Figma, Adobe, and Python: Is it possible to master all three without burning out?"

Discussion

Loading comments...