pick a featureInstabug Feature Requests: What Flutter Devs Need to Know
Many Flutter developers reach for Instabug when they want to start collecting user feedback. The SDK is widely used, has a Flutter package, and the phrase "feature requests" shows up in their product list. Whether it actually solves your problem depends on what that problem is.
If you need bug reporting, crash analytics, session replay, and feature requests bundled into one enterprise platform, Instabug (now marketed as Luciq) covers all of it. If you just want a simple way to let users vote on features inside your Flutter app, it's a lot more product than you actually need, and priced accordingly.
Instabug includes a feature request board as part of its mobile SDK suite, bundled with bug reporting, crash analytics, and session replay. The module lets users submit and upvote ideas in-app. For indie Flutter developers who only need feature voting, dedicated tools like pick a feature cover the same functionality for $0-$15/month instead.
What Instabug's Feature Request Module Includes
Instabug's feature request board (sometimes called the Ideas module, depending on the plan) lets users submit ideas, vote on existing ones, and check status updates from inside your app. The widget surfaces in your mobile UI so users don't have to leave the app to participate.
The module covers the fundamentals:
- In-app submission form with title and description fields
- Upvoting on existing requests (per device/account)
- Status labels visible to users
- Admin moderation and response tools in the dashboard
From a user-experience standpoint, it works. The interface is polished and the workflow is straightforward.
The context is what creates friction. Instabug's feature request module isn't a standalone product. You get it as part of the full Instabug/Luciq suite, which includes bug reporting with screenshot annotation, crash analytics, network request logging, session replay, and user surveys. That's a powerful combination for teams that genuinely need all of it. For a solo developer building a Flutter side project who just wants to track which features users want most, subscribing to an enterprise mobile observability platform to unlock a voting board is a hard sell.
Instabug has since rebranded its product suite under the Luciq name. The mobile SDK now markets under Luciq, though the underlying platform is the same team and technology. (There's a detailed breakdown of Luciq vs pick a feature if you want the full side-by-side comparison.)
The Pricing Gap Between Instabug and Dedicated Feature Request Tools
Instabug/Luciq doesn't publish pricing on their website. You contact sales, schedule a call, and get a custom quote: a reliable signal that you're looking at enterprise-level costs.
Based on publicly available information and user reports, entry-level Instabug plans run several hundred dollars per month. That price covers the full platform. There's no feature-request-only tier and no free plan beyond a trial period. For teams with multiple engineers where the combined crash reporting, bug tracking, and session replay gets used daily, the cost can be justified. The platform does a lot. But for an indie developer with a Flutter app at early revenue stages, paying hundreds per month to get a voting board isn't realistic. Pick a feature approaches pricing from the opposite direction. The free tier covers 1 project and 10 feature requests with no credit card required. Starter is $5/month for 3 projects with unlimited requests. Unlimited is $15/month for unlimited projects and requests. The free tier is a genuine, indefinite plan; many indie apps stay on it for the first 90 days while they validate whether feature voting drives enough engagement to justify upgrading.
That's $5/month versus several hundred dollars per month for the same core voting functionality. Most indie developers making that comparison don't need much deliberation.
Flutter SDK Setup: Instabug vs pick a feature
Both tools have a Flutter SDK, but the complexity of each setup reflects the scope of the product.
Instabug's Flutter integration requires configuring the full SDK at initialization: specifying which modules you want enabled (bug reporting, crash analytics, feature requests, surveys), and handling the broader setup that comes with a multi-feature platform. The documentation is thorough because there's genuinely a lot to configure.
Pick a feature's setup is pared down to the minimum:
await PickAFeature.initialize(apiKey: 'your_api_key');
That's the full initialization. After that, you drop in whichever widget fits your app's layout:
PickAFeatureScreenfor a full-screen viewPickAFeature.showDialog(context)for a dialog overlayPickAFeature.showBottomSheet(context)for a bottom sheet
Users can browse approved requests, vote, comment, and submit new ones without you writing additional UI code. Theming is one config object: pass your primary color, background color, and border radius, and the widget matches your app's look.
Anonymous users are handled automatically via a device UUID stored in shared_preferences. You don't have to force sign-in to collect useful voting data. If your app has user accounts, you can attach identity with PickAFeature.updateUser, passing email, name, custom ID, or revenue tier to segment feedback by user type.
For a step-by-step walkthrough of the full setup, the how to add feedback to your Flutter app guide covers initialization, widget placement, theming, and user identity in detail.
Both SDKs compile to iOS, Android, web, and macOS via Flutter. There's no React Native or native Swift/Kotlin SDK for either tool, so if you're building outside Flutter, you'll need a different option.
When Instabug Feature Requests Are Worth It
Instabug fits teams where bug reporting and crash analytics are the central concern and feature requests are a secondary workflow inside the same dashboard. If you're already paying for Instabug's crash analytics and want a voting board included without adding a second vendor, staying in one platform is reasonable.
It also fits teams at a scale where the full observability suite gets daily use. Engineers triaging crashes, replaying sessions, and reviewing network logs alongside feature request data can get real value from everything living in one place.
For that use case, the premium makes sense.
Pick a feature fits a different profile: Flutter developers who want feature voting specifically, without the broader mobile observability stack. The focused feature set, minimal setup, and indie-friendly pricing make it faster to deploy and easier to justify at early revenue stages.
Here's a quick breakdown by scenario:
| Scenario | Better fit |
|---|---|
| Enterprise Flutter app, bug reporting is primary | Instabug/Luciq |
| Flutter indie app, feature voting is primary | pick a feature |
| Need crash analytics and feature voting, budget fits | Instabug/Luciq |
| Solo dev, side project, limited monthly budget | pick a feature (free tier) |
| Need one-line Flutter setup, no backend overhead | pick a feature |
Features That Differ Between the Two
A few specifics worth knowing before choosing.
Status workflow. Pick a feature uses a 6-stage workflow: pending, under review, approved, in progress, planned, completed. Users only see approved and completed requests in the SDK widget; pending submissions stay hidden until you review them. That keeps the public board clean from day one.
Demo mode. Pick a feature has a built-in demo mode that serves canned data with no network calls. You can build, screenshot, and demo your app's feature request screen without a live API connection. For App Store screenshots and investor demos, this saves meaningful time.
Custom copy. Pick a feature lets you override every text label in the widget: the title, subtitle, placeholder text, submit button copy, and whether the optional email field appears. Instabug's feature request module has less flexibility on widget copy since it shares UI conventions with the broader platform.
Self-hosting. Pick a feature supports a custom apiBaseUrl if you want to point the SDK at your own backend. That's an unusual option for a SaaS feedback tool and gives you a data ownership exit path if you ever need one.
Frequently Asked Questions
Does Instabug have a free tier for feature requests?
Instabug offers a free trial, but the product is enterprise-priced without a permanent free plan. The feature request module is bundled with the full platform, so you can't access it independently on a free tier.
Is Instabug the same as Luciq?
Instabug rebranded its mobile SDK product suite under the Luciq name. It's the same company and platform, now positioned under the Luciq brand with a broader product scope than bug reporting alone.
Can I use Instabug just for feature requests in Flutter?
You can configure which modules are active in the SDK, but you're still on the full platform subscription. There's no feature-request-only pricing tier.
What's the most affordable way to add feature requests to a Flutter app?
Pick a feature has a free tier (1 project, 10 requests, no credit card required) and a $5/month Starter plan for unlimited requests. That's the lowest entry cost of any Flutter-native feature request tool with a managed cloud backend.
Does pick a feature require users to sign in to vote?
No. The SDK generates a device UUID for anonymous users stored in shared_preferences. You get voting data without forcing account creation. If users do sign in, attach their identity with PickAFeature.updateUser.
If you're building a Flutter app and want to collect feature requests without the overhead of an enterprise mobile platform, pick a feature is built for exactly that. Start free today, no credit card needed, and your first feature requests can come in the same day you ship the SDK.