Comparison

A UserVoice alternative that still ships a mobile SDK

UserVoice built iOS and Android SDKs, and then archived both of them on 25 July 2019. If your users are in a mobile app, that is the fact the rest of this page is about.

Last checked against UserVoice's public site and repositories: 3 September 2026.

What happened to UserVoice on mobile

UserVoice shipped an iOS SDK in 2012 and an Android SDK shortly after. Both were real native integrations: a support and feedback surface you could open from inside your app.

Both repositories were archived by UserVoice on 25 July 2019 and are read-only. The README on each says the same thing:

• “⛔ [DEPRECATED] This repository is no longer actively maintained. You may fork the project but we are no longer accepting pull requests or new issues.”

You can still fork them. You would be adopting an unmaintained dependency, written against an iOS and Android that no longer exist, into an app you have to ship through review. For most teams that is not a real option.

What that leaves you with

A hosted UserVoice portal, and a link to it from somewhere in your app. Which means the four drop-off points every portal has: the context switch out of the app, finding the link, getting an account, and describing from memory a bug that was on screen a minute ago. The long version of that argument is here.

For a B2B product where feedback arrives through account managers and support tickets, that is fine — arguably correct, because the portal is where the account team already works. For a consumer mobile app it means the only users you hear from are the ones persistent enough to complete a signup flow on a different device context. That is a sample filtered by stubbornness, not by importance.

The pricing wall

UserVoice does not publish prices. Its plans page says pricing is based on feedback volume, the tools you use, and the integrations you connect, never by seat — and to see a number you talk to sales. The free trial is 30 days and starts with a demo booking.

That is a normal enterprise motion and it is not a criticism on its own. It is a practical problem if you are one developer with an Android app deciding on a Tuesday evening whether this is worth trying. There is no self-serve path and no free tier to poke at.

fedo's Starter tier is free, covers one app with unlimited users, and needs no call. It shows a “Powered by fedo” badge; that is the trade.

What fedo does instead

• A maintained mobile SDK. com.getfedo:sdk-android on Maven Central. FeedbacksScreen() is a Compose composable that renders the list, detail, editor, voting, and comments inside your own navigation.
• No account to participate. Call the screen without setUserID and the SDK mints an anonymous user; when that person later signs in, their posts, votes, and comments migrate across. How that works.
• Prioritisation by vote count. Not segments, not ARR weighting — a list sorted by how many people asked. Less powerful than UserVoice, and enough for a team without a sales org.

The four-call Android integration.

fedo vs UserVoice, side by side

UserVoice details from uservoice.com/plans and the archived iOS and Android repositories, checked 3 September 2026.

Where UserVoice is still the better tool

These are not close calls. If any of them describe you, UserVoice wins:

• You have a sales team and named accounts. UserVoice can weight a request by the revenue behind it. fedo counts votes, and a vote from your largest customer counts the same as anyone else's.
• Feedback arrives through support, not through the app. UserVoice is built to ingest from Zendesk, Salesforce, and account managers. fedo only sees what users type into your app.
• You need SSO, audit trails, or procurement-grade compliance. fedo has none of these and is not close.
• Your product is a web app. fedo has no web SDK at all.
• You need iOS today. fedo's iOS, Flutter, and React Native SDKs are in development, not published.
• You need a vendor with a track record. UserVoice has more than a decade of it. fedo is in early access with no public customer list.

What switching actually looks like

There is no UserVoice importer, and for most teams this is not a switch at all — it is adding a mobile channel that UserVoice stopped serving in 2019.

1. Add the Android SDK behind a menu item. It does not disturb your portal.
2. Leave UserVoice running for whatever it is already good at — support ingestion, the web audience, the enterprise reporting.
3. Compare one release cycle of in-app submissions against portal submissions from mobile users.
4. Decide from that. Running both is a legitimate end state, not a failure to choose.

Common questions

Does UserVoice have a mobile SDK?

Not a maintained one. UserVoice published iOS and Android SDKs and archived both repositories on 25 July 2019. Each README states the project is no longer actively maintained and that pull requests and issues are not accepted. Forking is possible; relying on it in a shipping app is a decision to maintain an abandoned dependency yourself.

How much does UserVoice cost?

UserVoice does not publish prices. Its plans page says pricing is based on feedback volume, the tools used, and the integrations connected, and is never charged per seat. Trials run 30 days and begin with a demo booking.

Is fedo a full replacement for UserVoice?

No. UserVoice is an enterprise voice-of-customer platform with CRM ingestion, segmentation, revenue-weighted prioritisation, and SSO. fedo is an in-app feedback and voting SDK. If you use the enterprise half of UserVoice, fedo replaces none of it. If you use UserVoice mainly as a feature request board and your users are in a mobile app, it covers that.

What is the best UserVoice alternative for mobile apps?

Depends what you need. Gleap is the most complete mobile option — native SDKs on iOS, Android, Flutter, and React Native, plus live chat and AI support, from $49/month with no free plan. Canny is the closest like-for-like feedback board, though its mobile path is a WebView that requires SSO — comparison here. Features.Vote is Apple platforms only. fedo is the focused, free-tier option, and is Android-only today.

Other comparisons

• fedo vs Canny — the feedback portal whose mobile path is a WebView.
• fedo vs Gleap — the support suite where the roadmap is one module.
• All comparisons — the hub, plus tools without a write-up yet.
• In-app feedback beats a feedback portal — the argument underneath all three.