FeedbackKit vs UserVoice: In-App Voting or an Enterprise Portal

UserVoice is built for large B2B companies: branded feedback portals, a web widget, account revenue from Salesforce, and links into Jira and Azure DevOps. FeedbackKit is built for app teams who want the feature-request board inside their iOS, Android or cross-platform app. Both cover ideas, votes, comments and statuses, and differ on most of what sits around them.

We make FeedbackKit, so read this with that in mind. Every UserVoice fact below comes from UserVoice's own website and help center, and from its own GitHub repositories, checked on 17 October 2026, and is linked where it is used. The side-by-side table lives on our FeedbackKit vs UserVoice compare page. This post goes further than the table.

The short version

• UserVoice is an enterprise feedback platform. Its homepage describes branded portals, in-app, Slack and Chrome-extension capture, AI analysis, CRM data from Salesforce and HubSpot, and Jira and Azure DevOps connections. It publishes no prices.
• FeedbackKit is in-app feedback and feature voting for app teams, with native SDKs for Swift, Kotlin, Flutter and React Native, native admin apps for iPhone, iPad and Mac, and published prices that start with a free plan.
• If you sell to large accounts and your engineers live in Jira, UserVoice is the better fit. If your users are in a native app and you want requests ranked by the MRR your app already knows, FeedbackKit is.

Getting feedback in

UserVoice: portals, a web widget and staff capture

UserVoice's main surface is a branded web portal where customers post ideas, vote, comment and subscribe to status changes. To collect ideas inside a product, its widget guide describes a Post Idea widget you paste into a website before the closing body tag. When someone types an idea, the widget shows matching ideas, so they can join an existing one rather than post a duplicate. The widget is on Discovery Pro and Discovery Premium, the plan names UserVoice uses in its help center. Staff can also log feedback for customers from Slack, a Chrome extension and support tools, and developers get an Admin API.

On mobile, UserVoice once had native SDKs. Its iOS SDK and Android SDK repositories on GitHub are archived and were last updated in July 2019, and the current site does not mention a mobile SDK.

FeedbackKit: native SDKs

FeedbackKit starts inside your app. There are SDKs for Swift and SwiftUI (iOS, macOS and visionOS), Kotlin with Jetpack Compose (Android), Flutter and React Native, and each of these ships ready-made screens: a request list, a submit form, a detail view with comments, and vote buttons. The JavaScript SDK is a headless client for the web and ships no screens. There is also a Vapor SDK for server-side Swift and a REST API. FeedbackKit sends no outgoing webhooks.

An honest caveat from our side: the Swift SDK needs iOS 26, macOS 26 or visionOS 26 or later, with no watchOS or tvOS. If you support older iOS versions, it is not an option for you yet. SDK docs: Swift, Kotlin, Flutter, React Native, JavaScript.

For your website, FeedbackKit can show a project's roadmap and its board of requests on your own website through an iframe, and it has a feedback form page you can embed the same way. The board shows open requests in status columns with their vote counts, and visitors can vote on it when you turn voting on. Embeds are on every plan, in light or dark. There is no changelog for your users, and no hosted roadmap site on your own domain.

Here is how that looks in FeedbackKit, with sample data from a fictional hiking app:

Managing feedback

UserVoice gives admins a lot of control over workflow. Its status article lists five default public statuses, running from Under Review through Started to Completed and Declined, plus separate internal statuses. Admins can rename them, add their own, and set whether each status allows votes, comments, both or neither, on Discovery Pro and Premium. Roadmaps are internal by default, and sharing one publicly needs Discovery Premium. The homepage also lists an AI agent for plain-language questions, AI themes and trends, and impact reports.

FeedbackKit has six built-in statuses on every plan: Pending, Approved, In Progress, TestFlight, Completed and Rejected. On Pro and up you choose which ones a project uses, and there are no custom statuses. A new request starts with its submitter's vote, and voting stops at Completed and Rejected. You can merge duplicate requests, and each voter is counted once on the request you keep. A rejected request can carry a reason, which goes into the status email. You work from the web dashboard or the native admin apps for iPhone, iPad and Mac. Your team gets email for new requests on every plan, and push for new requests and new comments in the FeedbackKit app. New-comment email to the team needs Pro.

Revenue behind each request

Both tools can weigh a request by what its supporters pay you, and they get there differently.

In UserVoice, you send user and account traits such as spend or plan. The widget's identify call can pass them on Discovery Pro and Premium, and the API and CSV import are other routes. Segmenting voters by those traits is on Discovery Premium. The Salesforce connector, also on Discovery Premium, maps an account revenue field so you can see ideas by the total revenue of supporting accounts. That suits a company whose revenue lives in Salesforce at account level.

In FeedbackKit, your app passes each user's MRR through the SDK, on every plan, and requests can be sorted by the total MRR of the users behind them. That suits an app whose revenue comes from in-app subscriptions, where the app already knows what each user pays.

Here is how triage looks in FeedbackKit, with the same sample hiking app:

Integrations

The UserVoice column is from its integrations page and help center, as of 17 October 2026.

The tracker link works differently on each side. UserVoice's Jira article says you can link or create Jira issues from ideas on Discovery Premium, and each tool shows the linked item's status, but a status change in one does not change the other. FeedbackKit creates and links tickets in nine trackers with status sync, on Pro and up. They differ after that: GitHub has no comment sync, and GitHub, Linear, Trello and Basecamp have no vote-count sync. The full matrix is on the integrations page. FeedbackKit has no Jira, Azure DevOps, Zapier, Make, Microsoft Teams or Discord integration, and every FeedbackKit integration needs Pro.

Closing the loop

UserVoice's homepage lists status subscriptions on its portals, notifications to supporters when items ship, and one-to-one and one-to-many customer messages. When an admin changes an idea's public status, they can write a status message for its supporters.

In FeedbackKit, the status email follows two rules. The person who submitted a request is emailed on every plan when the new status is on the project's list, which starts as Approved, In Progress, Completed and Rejected. Choosing that list needs Pro, and emailing voters who opted in needs Team. Your app's users get status email, never push. The details are in our post on status emails.

Pricing

UserVoice does not publish prices. Its pricing page says a plan is "based on feedback volume, tools leveraged and the integrations you connect, never by seat", and the route in is a call with its team. FeedbackKit's prices are on our pricing page. Both checked on 17 October 2026.

FeedbackKit's yearly billing saves about 17%, with no limit on voters on any plan. Past the Free cap of 10, new items are saved and left off the board. See also UserVoice pricing, UserVoice alternatives and Canny vs UserVoice.

So which one

Choose UserVoice if you sell to large B2B accounts and want feedback weighed by Salesforce account revenue and segments. Choose it if your engineers work in Jira or Azure DevOps, or your company runs on Microsoft Teams, or if you need enterprise controls such as SAML SSO and SCIM, branded portals and a sales-led contract. It is a mature product for that world.

Choose FeedbackKit if your product is a native iOS, macOS, Android, Flutter or React Native app and you want voting and comments in native UI inside it. Choose it if you want requests ranked by the MRR your app passes, on every plan, with no CRM connector to set up, if your team plans work in GitHub, Linear, Notion, ClickUp, Monday.com, Trello, Airtable, Asana or Basecamp, or if you want published prices and a free plan to start on.

The quickest test is to put the SDK into a test build and watch a few people use it. Start free and see how it fits.