Built a Simple Feature Request Widget – Thoughts?

Hey fellow devs,

I’ve been working on a lightweight SaaS called FeaturAsk, a simple way for website owners to collect feature requests and let users vote on them. It started as a small tool for my own projects, but I realized others might find it useful too. The idea is to give website owners an easy-to-embed widget where visitors can submit and upvote ideas, with all backend management handled in a clean dashboard.

:small_blue_diamond: What It Does:

  • Feature Request Widget – Embed a customizable request box on your site in minutes.
  • Voting System – Visitors upvote the most important requests.
  • Fully Customizable – Change colors and fonts to match your brand.
  • No-Code Setup – Generate HTML, copy, and paste—done.
  • Dashboard for Owners – Monitor, manage, and respond to requests.
  • 7-Day Free Trial – No risk, test it and see if it fits your needs.

:handshake: Why I’m Posting Here:

This is my second proper SaaS launch, and I know there’s always room for improvement. If you run a website, blog, online store, or any kind of service that takes user feedback, I’d love to hear your thoughts.

:light_bulb: Is this something you’d use? What features would make it better? Any feedback on UX or functionality?

:link: Check it out here: https://featurask.com or https://featurask.replit.app

Would love to hear what you think—whether it’s about the concept, execution, or what could be improved!

4 Likes

Nicely done @andrianventures!

Just tested FeaturAsk. Excellently built and designed!

I’ve considered building an app, not like this one, in a different category/focus, which would also require an embed on a website.

I’d be curious to hear if you had to take any unique approaches to get the embed feature to work?

Thanks, Mark! Glad you liked FeaturAsk!

For the embed feature, there were definitely some unique challenges. One key focus was preventing misuse and bot activity. I implemented several safeguards, including Redis for rate limiting, an optional reCAPTCHA, and invisible honeypot fields. Since reCAPTCHA needs to work on the client’s website but is tied to my domain, I solved this by handling it within a secure popup.

Additionally, I restricted API access to only the assigned webpage, which users can update anytime in their settings. There are a few more optimizations under the hood, but these were the main ones to keep things secure and efficient.

Are you planning to include an embed feature in your project? Happy to share more insights!

1 Like