A public feedback board you can share with one link

What a hosted feedback board does

Think of it as a suggestion box with a scoreboard. Visitors see two tabs, planned and completed, listing the requests you have accepted. Each one shows a title, a description, a vote count, and comments. A visitor taps the arrow to upvote, taps again to take it back, and can open a request to read or add comments. A "Suggest a feature" button opens a short form: title, description, and an optional email so you can follow up. The whole board appears in the visitor's language, with Spanish, Portuguese, French, German, Italian, Japanese, Korean, Chinese, Russian and Turkish built in, or in the one language you pick.

On your side, every new suggestion lands in a private queue. It is not visible on the board until you approve it, which is what keeps spam, duplicates, and support questions off the public page. Approve it, and it appears under planned; ship it, move the card to completed, and it moves to the other tab. Visitors who come back see the progress without anyone writing an update post.

Hosted boards are what Canny, Featurebase, and Nolt sell as their core product, at $79, $59, and $29 a month respectively. The difference here is price and scope: pick a feature is free for one project and 10 requests, $5 a month after that, and the board is the same one your app renders through the Flutter SDK or web widget, so mobile and web votes add up in one place.

Set it up in two minutes

1. Create a free account and add a project. The name becomes the board's title and its URL slug, for example pickafeature.com/b/fasting-tracker.
2. Open the Projects page. Each project card shows its board link with copy and open buttons. Click the pencil to change the slug to something shorter.
3. Seed the board with three or four requests you already know about, so the first visitor does not land on an empty page. Submit them through the board itself, then approve them in the dashboard and set their status.
4. Share the link. Website footer, in-app settings, the bottom of your release notes, your Discord's pinned message, or a reply to the next person who emails you an idea.

There is no code in any of those steps. If you later want the board inside your product instead of on its own page, the sections below cover that, and the board you set up today carries over unchanged.

Where a shareable board works best

• Website footer or help center. A "Feature requests" link next to "Contact" turns support email into public, voteable requests that other users can pile onto.
• Launch and update posts. End every release note with "what next? vote here". It is the highest-intent moment to ask.
• Social and communities. One link in a tweet or a Reddit reply beats collecting replies by hand and losing them in a thread.
• Inside native apps. iOS, Android, React Native, and Kotlin Multiplatform apps open the board in an in-app browser with a few lines of code. The iOS, Android, React Native, and KMP guides show the exact snippets.
• Early validation. Before you build the product, a board with the features you are considering tells you which ones people would actually use.

Embed the board on your own site

When you want the board to live on your domain, for example at yoursite.com/feedback, embed the web widget in inline mode. It renders the same board inside any element on your page, in a Shadow DOM so your CSS and ours never interfere:

<div id="feedback-board"></div>

<script
  src="https://pickafeature.com/sdk/v1/pickafeature.js"
  data-api-key="YOUR_PROJECT_KEY"
  data-container="#feedback-board"
  defer
></script>

Drop data-container and the same script gives you a floating "Feedback" button and a popup instead, which is the usual choice for a SaaS dashboard. If your site has accounts, call PickAFeature.identify after login so a user's votes follow them between devices. All options are in the web widget docs.

Running a board that people keep coming back to

The boards that work are the ones that visibly move. A few habits make the difference. Approve or decline new requests within a day or two, so submitters see their idea appear. Reply in the comments when you need detail; a two-line question from the founder gets answered far more often than a support form. Update statuses the moment work starts, not when it ships, because "in progress" is the update people care about most.

Merge duplicates aggressively. Two requests for the same thing split the votes and make both look less popular than the idea really is. In the dashboard you drag one card onto the other, choose which title and description to keep or combine them, and votes carry over with each person counted once. The feature request management guide goes deeper on triage and saying no.

How pick a feature compares for a hosted board

pick a feature is priced for developers paying out of pocket: free for one project and 10 feature requests, $5 a month for three projects with unlimited requests, $15 a month for unlimited projects. No per-seat charges, no per-tracked-user tiers, and the free plan is permanent rather than a trial.

Every plan includes the hosted board, the embeddable web widget, the Flutter SDK, a kanban dashboard with duplicate merging, email notifications, and per-platform analytics. Custom domains and a separate public roadmap page are not available yet; the board lives at pickafeature.com/b/your-slug and shows planned and completed work. If a custom domain is the thing you need, tell us, and it goes on our own board.

Frequently asked questions