← Back to Blog

Wiredash vs pick a feature: Which Flutter SDK?

Tom Reilly··10 min read
wiredashcomparisonsfeature-requestsflutterfeedback-sdk
Developer's desk with a laptop showing Flutter code and a phone displaying an in-app feedback board

You've built a Flutter app and you're ready to hear from users. Two SDKs keep coming up: Wiredash and pick a feature. Both ship as Flutter packages. Both drop into an existing app without a UI rewrite. Both live in the "feedback" category in most roundups.

But they're built for different jobs, and picking the wrong one means collecting data you can't act on.

Wiredash captures in-the-moment reactions: bug screenshots, NPS scores, CSAT ratings, custom surveys. pick a feature collects feature requests: users submit ideas, vote on what matters, and see a status workflow that shows what's actually getting built.

Wiredash vs pick a feature in one line: Wiredash is a Flutter feedback SDK built around bug capture, satisfaction surveys, and in-app analytics. pick a feature is a Flutter feature-request SDK with voting, comments, and a six-stage status workflow. Use Wiredash to understand how users experience your app right now. Use pick a feature to collect and prioritize what features they want built next.

Wiredash vs pick a feature: Two Different Tools

Both get lumped into the "Flutter feedback SDK" bucket, which is where the confusion starts. The actual overlap is thin.

Wiredash is reactive. It captures what users feel at a specific moment: a bug they hit, an NPS prompt after a key event, a satisfaction rating after they complete a flow. You trigger it, or users shake their phone to open the feedback sheet. You get structured qualitative data about the current state of your app.

pick a feature is forward-looking. Users open a feature board, browse what others have submitted, upvote what they care about, and add new ideas. You get a prioritized wishlist to inform your next sprint.

They don't conflict. Running both in the same Flutter app is common practice: Wiredash handles bug capture and satisfaction tracking, pick a feature handles roadmap input. But when you're choosing one tool to add first, knowing which problem is more urgent tells you where to start.

If you're also evaluating web-based tools alongside Flutter SDKs, the Canny vs pick a feature and Featurebase vs pick a feature comparisons cover the web-first category in detail.

What Wiredash Does

Wiredash's core product is an in-app feedback sheet that slides up when triggered. Users can draw on screenshots, annotate problem areas, and submit written notes without leaving your app.

Beyond bug capture, Wiredash includes:

  • NPS prompts fired at custom events (after purchase, after onboarding, after session 5)
  • CSAT rating flows
  • Custom multi-step surveys built in the dashboard
  • Usage analytics layered on top of qualitative feedback data

The free tier covers apps up to 100,000 MAU, which means most indie Flutter apps don't pay anything for a long time.

Wiredash is a mature Flutter SDK that wraps your widget tree and initializes with a project key. The feedback sheet triggers programmatically or via the built-in shake gesture. Its dashboard combines qualitative feedback with session data and retention metrics, giving you one place to see how users behave and what they say about the app. The analytics layer covers retention curves, user cohorts, and satisfaction scores over time. For apps still hunting product-market fit, this is genuinely useful: you can see where users drop off, which flows generate the most complaints, and whether NPS scores improve after a release. Where Wiredash ends is at feature prioritization. There's no voting system. When users write "please add dark mode" in a feedback submission, that comment sits in your inbox as an unstructured note. You'd have to manually count how many different users asked for the same thing. For developers who need to know what to build next and not just what's broken, Wiredash leaves that gap open.

What pick a feature Does

pick a feature is stripped back to one job: let users submit, vote on, and track feature requests from inside your Flutter app.

The SDK wires in with a few lines:

await PickAFeature.initialize(apiKey: 'your-key');

From there, you get three pre-built widgets: a full-screen board (PickAFeatureScreen), a dialog (PickAFeature.showDialog), and a bottom sheet (PickAFeature.showBottomSheet). All three let users browse approved requests, upvote ideas, leave comments, and submit new ones.

A few things stand out:

  • Anonymous by default. Users who haven't signed in still vote. pick a feature generates a device UUID stored in shared_preferences, so votes stay unique per device without requiring auth.
  • User identity attachment. If users are signed in, you attach an email, name, custom ID, and revenue tier. This tells you whether power users and free users are asking for different things.
  • Six-stage status workflow. Requests move from pending through under review, approved, in progress, planned, and completed. Only approved and completed requests show up in the SDK widget, so users see a clean board.
  • Demo mode. The widget runs with canned data before you connect to the API. Useful for screenshots, store previews, and CI builds.
  • Self-host option. Override apiBaseUrl to point the SDK at your own backend if you need control over where data lives.

Theming is baked into the SDK config: you set primary color, background color, text color, and border radius to match your app. The widget title, subtitle, placeholder text, and submit button copy are all customizable, so it doesn't read as a third-party tool bolted on at the last minute.

What pick a feature doesn't do: no bug screenshots, no NPS prompts, no CSAT ratings, no session analytics. It's a feature-request tool and nothing else.

Wiredash vs pick a feature: Feature Comparison

Here's how the two tools compare on the things Flutter indie devs care about most:

FeatureWiredashpick a feature
Flutter SDKYesYes
Feature request votingNoYes
Status workflowNoYes (6 stages)
In-app feedback with screenshotsYesNo
NPS / CSAT surveysYesNo
Usage analyticsYesYes (request-level)
Anonymous user supportYesYes (device UUID)
Free tierUp to 100k MAU1 project, 10 requests
Entry paid planUsage-based$5/month flat
Self-host supportNoYes (apiBaseUrl override)

One thing the table doesn't capture: the feedback philosophy. Wiredash asks "how does your app feel right now?" pick a feature asks "what should your app do next?" Those are different conversations with your users, and both are worth having.

Pricing

Wiredash's free tier is unusually generous: 100,000 MAU at no cost. Most indie Flutter apps stay under that limit for months or years. Paid tiers scale with usage, so check wiredash.io for current pricing once you approach the ceiling.

pick a feature uses flat monthly pricing:

  • Free: 1 project, 10 feature requests, email notifications, basic analytics, no credit card required
  • Starter ($5/month or $50/year): 3 projects, unlimited requests, user comments, full analytics, no watermark
  • Unlimited ($15/month or $150/year): Unlimited projects and requests, advanced analytics, priority support

The Starter tier works out to less than a coffee per week. Compare that to Canny Pro at $79/month or Featurebase at $29/seat/month, both of which are web-only tools with no Flutter SDK. For Flutter-native feature request management, pick a feature's $5/month is the cheapest option in the space.

If your app has high MAU but you only need feature voting for an engaged subset of users, pick a feature's flat pricing is more predictable than usage-based models. If you need deep analytics for a rapidly growing app, Wiredash's free MAU tier may stretch further before hitting a wall.

Which One Should You Pick?

Use Wiredash when you want to understand how users feel about your app right now:

  • Bug reports and screenshot feedback are your priority
  • You need NPS or CSAT to track satisfaction trends across releases
  • You want session-level analytics alongside qualitative feedback
  • Your app is still finding product-market fit and you're chasing rough edges

Use pick a feature when you want to know what your users want built next:

  • You want a voting board so users can prioritize your backlog
  • You need a transparent status workflow so users see their requests aren't disappearing
  • You're an indie dev or bootstrapped founder who can't absorb Canny's $79/month
  • You want self-hosting headroom without rebuilding a feedback UI from scratch

One scenario where pick a feature wins clearly: you've shipped your app, you have an engaged user base, and you're planning the next quarter. Running a vote for two weeks surfaces which requests have real demand. Building the top-voted feature and marking it "completed" in the dashboard closes the loop with the users who asked for it. They see it arrived. That kind of follow-through builds more trust than a changelog email.

Running both tools in the same Flutter app is practical. They don't share SDK surface area, so there's no conflict. Initialize pick a feature for a roadmap tab, trigger Wiredash after key user flows. Each tool handles its job without getting in the other's way.

Frequently Asked Questions

Is pick a feature a Wiredash alternative?

Partially. Wiredash handles in-context feedback: screenshots, NPS, surveys, and usage analytics. pick a feature handles feature requests: voting, comments, and status tracking. They overlap in the broad "feedback" category but solve different core problems. They work better as complements than substitutes, and can run together in the same Flutter app.

Can I run both Wiredash and pick a feature in the same Flutter app?

Yes. Both SDKs initialize independently with their own API keys. A common setup: Wiredash for NPS surveys and bug capture after key flows, pick a feature for the feature-request board in your settings or roadmap tab. No conflicts.

Does Wiredash support feature request voting?

No. Wiredash focuses on in-app surveys, screenshot feedback, and analytics. There's no voting system or status workflow for managing feature requests. If that's what you need, pick a feature is the right tool.

Does pick a feature have user analytics?

Yes, but scoped to request data. The Free tier includes basic analytics. Starter ($5/month) adds full analytics. Unlimited ($15/month) adds advanced analytics. For session-level behavior, retention curves, and funnel data, Wiredash is the stronger choice.

Is pick a feature free for Flutter developers?

Yes. The Free tier gives you 1 project and 10 feature requests with no credit card required. Most indie apps stay free during early validation. Once you need more than 10 requests or multiple projects, Starter is $5/month.


If you're a Flutter developer who wants to know what features your users actually want, pick a feature gives you a voting board in minutes. Drop in the SDK, pick a widget layout, and users can start submitting and upvoting immediately. Try it free at pickafeature.com.