Best Flutter Feedback SDKs in 2026

Flutter doesn't ship with a feedback system. There's no built-in way to let users submit feature requests, vote on ideas, or report bugs from inside your app. So every Flutter developer eventually builds something themselves or finds a package that handles it.

The problem is most feedback tools were designed for the web. Canny, UserVoice, Featurebase — solid products, but web-first. Dropping them into a Flutter app means wrapping their web UI yourself or redirecting users to a browser. Neither feels native.

This guide covers the best Flutter feedback SDKs in 2026: what each one does, who it's built for, and which scenario it actually fits.

The best Flutter feedback SDKs in 2026 are pick a feature (voting and status workflow), Wiredash (surveys and NPS), and Luciq (enterprise crash reports plus feature requests). Indie apps focused on roadmap decisions should start with pick a feature: free tier, no card needed. Analytics and satisfaction teams lean toward Wiredash. Enterprise mobile teams reach for Luciq.

What to Look for in a Flutter Feedback SDK

Not all Flutter feedback SDKs belong in the same category. Picking the wrong one means paying for features you'll never touch, or missing the capability that actually matters.

Flutter feedback SDKs fall into three categories based on what they collect. Feature-request SDKs like pick a feature let users submit and upvote ideas inside your app, with a status workflow that moves a request from pending to shipped. Bug-report SDKs like better_feedback and Wiredash attach screenshots and device info to crash reports. Full-suite SDKs like Luciq, formerly Instabug, bundle all three: crashes, sessions, and feature requests in one enterprise package. The right category depends on your team size and pain point. Indie apps typically need feature voting first; they're not drowning in bugs, they're figuring out what to build next. Larger teams with dedicated QA often benefit from a bug-report SDK first. Enterprise mobile teams usually want the full Luciq suite because they have the budget and the workflow. Choosing the wrong category means paying for features you'll never use, or missing the one capability that would have changed how you prioritize.

Two other things separate a good Flutter feedback SDK from a bad one: deep Flutter integration and a managed backend. Deep integration means widget-level drop-ins, theming that fits your design system, and consistent behavior across iOS, Android, web, and macOS. A managed backend means you're not spinning up a Firestore instance or provisioning your own server. Some packages (suggest_a_feature, for example) give you the UI but hand you the infrastructure problem. That's more work than most solo Flutter devs want.

Best Flutter Feedback SDKs Compared

pick a feature

pick a feature is a Flutter SDK plus cloud dashboard built specifically for the "what should we build next" workflow. Users submit feature requests, vote on existing ones, and leave comments. You moderate from a dashboard and move requests through a six-stage status pipeline: pending, under review, approved, in progress, planned, and completed. Only approved and completed items show in the SDK widget, so users see a clean, curated board.

Setup takes one line. Call PickAFeature.initialize(apiKey: 'your-key') before runApp, then surface the feature board using one of three drop-in widgets: a full-screen view, a dialog, or a bottom sheet.

The backend is fully managed: no Firestore, no custom server. You get moderation tools, multi-project support, email notifications, and analytics out of the box.

A few things make it practical for indie apps. Anonymous voting works without requiring sign-in: pick a feature generates a device UUID stored in shared_preferences for users who haven't authenticated. Demo mode serves canned data with no network calls, which makes testing and App Store screenshots cleaner. And an apiBaseUrl override lets you point the SDK at your own backend if your data policy requires it.

Pricing is built for solo developers and small teams. The free tier covers 1 project and 10 feature requests, no card required. Starter is $5/mo for 3 projects with unlimited requests. Unlimited is $15/mo for unlimited projects and advanced analytics. Compare that to Canny Pro at $79/mo or Featurebase at $29/seat/mo, and the gap is hard to miss.

For a direct comparison of pick a feature against another popular Flutter SDK, see our Wiredash vs pick a feature breakdown.

Wiredash

Wiredash is a well-established Flutter SDK focused on reactive feedback and user satisfaction measurement. Its core features are screenshot-annotated bug reports, NPS prompts, CSAT surveys, multi-step in-app questionnaires, and usage analytics.

Feature voting and status workflow aren't in Wiredash's scope. When a user submits "please add offline mode" through a Wiredash prompt, that note lands in your inbox as plain text. Other users can't signal agreement. There's no roadmap status to update.

Where Wiredash earns its place is satisfaction measurement. Run an NPS survey after onboarding, capture a bug with a screenshot without leaving the app, or measure CSAT at a key funnel step. The free tier covers up to 100k MAU, so most indie apps won't pay anything for a long time.

A common setup: Wiredash for bug capture and NPS measurement, pick a feature for the feature-request board. Our roundup of Wiredash alternatives covers the full landscape for Flutter developers who need both.

Luciq (formerly Instabug)

Luciq is an enterprise mobile SDK bundling crash reporting, session replay, bug reports, and feature requests in one package. It's built for large mobile teams with dedicated QA workflows and budget to match.

The feature-request component exists and works. Teams choose Luciq for crash reporting and session replay; the feature-request module comes along for the ride. Pricing is sales-led, which puts it outside the range most indie developers consider.

For bootstrapped Flutter teams, Luciq is usually overkill. For teams at 10+ people who already had an Instabug relationship before the rebrand, it may already be in the stack.

suggest_a_feature

suggest_a_feature is a Flutter package that provides feature-request board UI backed by your own Firestore database. You bring the backend; the package brings the widgets.

For teams already running Firebase and comfortable with Firestore security rules and collection management, it's viable. The tradeoff is full infrastructure ownership: hosting costs, database rules, moderation logic, and ongoing maintenance fall on you. There's no hosted dashboard.

For indie apps that don't want to run their own backend, the managed-backend options remove that overhead entirely.

better_feedback

better_feedback is a Flutter package for screenshot-annotation bug reports. Users draw on the current screen, add a text note, and submit. The output is a screenshot with markup and device metadata attached.

It's a bug-reporting tool, not a feature-request tool. It doesn't handle voting, status workflows, or feature management. It pairs well with a simple email handler or your own issue tracker. If bug reports are your primary feedback channel and you want the lightest possible package with no backend, better_feedback fits.

Setting Up pick a feature in Your Flutter App

If you're ready to wire in pick a feature, the process is quick:

1. Add the package to pubspec.yaml:

   dependencies:
     pickafeature: ^1.0.0
   

2. Initialize in main.dart before runApp:

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

3. Show the feature board from any button, menu, or tab:

   // Bottom sheet (most common for settings screens)
   PickAFeature.showBottomSheet(context);
   
   // Dialog
   PickAFeature.showDialog(context);
   
   // Full-screen route
   Navigator.push(context, MaterialPageRoute(builder: (_) => PickAFeatureScreen()));
   

4. Optionally identify the current user so votes tie to your user IDs:

   await PickAFeature.updateUser(
     email: '[email protected]',
     name: 'Jane Doe',
     userId: 'usr_123',
   );
   

Your API key comes from the project dashboard at pickafeature.com. Total setup time for a fresh project: about 5 minutes.

How to Choose the Right Flutter Feedback SDK

The decision comes down to what your users are sending and what you need to do with it.

pick a feature fits indie developers and small teams who want users to vote on what to build next, with a fully managed backend and no infrastructure work.

Wiredash fits teams who need NPS, CSAT, in-app surveys, or screenshot-annotated bug reports alongside usage analytics.

Luciq fits enterprise mobile teams with dedicated QA, existing Instabug history, and a budget for a full-suite product.

suggest_a_feature fits teams already on Firebase who want full data control and are comfortable maintaining their own backend.

better_feedback fits apps where bug reports matter more than feature prioritization, and you want a lightweight package with no cloud dependency.

No single SDK wins across every scenario. Flutter's feedback SDK ecosystem is still young, and each tool carved out a specific lane. The most common mistake is reaching for a full-suite tool when you only need one thing.

Frequently Asked Questions

What's the best Flutter feedback SDK for feature voting?

pick a feature is the only Flutter SDK built primarily for feature-request voting with a managed cloud backend. It includes drop-in widgets, upvoting, comments, and a six-stage status workflow. Free tier covers 1 project and 10 requests. Starter is $5/mo for 3 projects with unlimited requests.

Does Wiredash do feature voting?

No. Wiredash focuses on bug capture with annotated screenshots, NPS prompts, CSAT ratings, and usage analytics. There's no voting system or status workflow for feature requests. If you need feature prioritization, use pick a feature alongside Wiredash; they initialize independently with no conflicts.

Which Flutter feedback SDKs work on iOS, Android, and web?

pick a feature, Wiredash, and Luciq all compile across iOS, Android, web, and macOS because they're built on Flutter primitives. Native Swift or Kotlin SDKs aren't required. Screenshot-annotation packages like better_feedback may have limited web support, so check the pub.dev compatibility matrix first.

How long does it take to add pick a feature to a Flutter app?

About 5 minutes. Call PickAFeature.initialize with your API key in main.dart, then trigger PickAFeature.showBottomSheet from any button. The widget handles everything else. If you want to identify users by email or custom ID, one additional updateUser call covers it.

Is there a React Native version of pick a feature?

Not yet. pick a feature is Flutter-only at the moment. A React Native SDK is confirmed on the roadmap but no release date has been announced. The Flutter package is available on pub.dev as pickafeature.

---

If you're building a Flutter app and want to know what your users actually want to see next, pick a feature gives you a drop-in voting board with zero backend work. The free tier covers most indie apps through early validation. Try it free at pickafeature.com: 1 project, 10 requests, no card needed.