How to Use Featurebase (And Where It Stops Short for App Reviews)

To use Featurebase, you set up a feedback board where users post and upvote ideas, drag those posts across a roadmap as their status changes, and announce what you ship in a changelog — all under your own domain and embeddable inside your app. That's the whole loop: collect, prioritize, ship, tell people. It's a clean tool and this guide walks the real setup, not a feature list.

One honest caveat up front, because it's the reason a lot of people land here confused: Featurebase organizes feedback you collect from your own product. It does not read or reply to your App Store and Google Play reviews — those live in a separate system it never touches. We'll cover the full Featurebase workflow first, then exactly where that gap sits and what fills it. Featurebase is a trademark of its owner; ReplyArgus is not affiliated with or endorsed by it.

Featurebase is a feedback-and-changelog platform in the same family as Canny or Nolt. The pitch is simple: give your users one place to request features, vote on each other's ideas, watch your roadmap, and read what changed. You get a hosted portal (yourbrand.featurebase.app or a custom domain), embeddable widgets, and a back office where your team triages everything.

The core pieces are a feedback board, a roadmap, a changelog, and an optional help center. As of 2026 there's a genuinely usable free plan (unlimited posts, a basic roadmap, a changelog), and paid tiers that unlock the AI features, a custom domain, analytics, and the full integration suite. Commonly cited numbers put the Growth tier around $49/mo and Business around $149/mo (with SSO and advanced controls), but confirm the current ladder at featurebase.app/pricing before you budget. Vendor pricing moves.

The setup is fast, under an hour to a live portal. Here's the order that avoids rework:

The setup is the easy part. These are the habits that make the tool actually pay off instead of becoming a graveyard of ignored requests:

Here's the gap that trips people up. Featurebase is built for feedback you invite — posts through your widget, your portal, your Intercom conversations. But the largest, most public stream of feedback for any mobile app doesn't come through those channels. It comes through App Store and Google Play reviews, and Featurebase has no connection to either. It can't pull those reviews onto a board, and it flat-out cannot post a public developer reply back to a store review. That's not a knock; it's simply not what the tool is built to do.

Why does that matter? Store reviews aren't a passive suggestion box; they're a ranking and conversion input you can move by answering. Google's I/O 2019 data showed apps average +0.7 stars after developers start responding to reviews, and Hassan et al.'s study of 4.5 million reviews found users were roughly 6× more likely to raise their rating after a reply (4.4% vs 0.7%). A tidy Featurebase roadmap does nothing for the one-star review sitting unanswered on your store page, visible to every prospect reading before they download. We ran those numbers in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating).

There's a second half to the gap: those reviews are also product feedback, often your best, because they're unprompted and specific. 'The PDF export crashes on iOS 18' is a roadmap item and a reply opportunity at once — but Featurebase never sees it unless a user retypes it into your portal, which they won't.

Notice what that reply does: it turns a two-star complaint into a recovery, points to a real roadmap decision, and invites the reviewer back — the exact loop Featurebase runs on its board, except performed where the rating actually lives. Doing this by hand across two stores, at volume, in whatever language the review is written in, is the part that doesn't scale.

This is the input Featurebase leaves open, and it's what [ReplyArgus](/features) is built for. It watches Apple App Store and Google Play in one inbox and drafts on-brand replies in the reviewer's own language — 100+ languages, both directions, so a Japanese review gets answered in Japanese without anyone on your team typing it (more on that in [reply to app reviews in any language](/blog/reply-to-app-reviews-in-any-language)). Every draft is grounded in your past approved replies plus an auto-ingested knowledge base from your store listing and marketing page, so it names the real version, the real fix, the real feature — not a plausible-sounding invention. Replies stay approve-by-default; you switch on rule-based auto-publish (by rating, keyword, language, or store) only where you trust it.

And it closes the same loop Featurebase does, just from the store side. Recurring review complaints cluster into a PM roadmap board you can export to Jira, Notion, Google Sheets, or DevRev. Those [integrations](/integrations) turn '40 reviews about crashing exports' into one tracked item. If you already run Featurebase for invited feedback, ReplyArgus handles the review stream it can't reach; if you're picking one tool for the store side specifically, that's the whole job it does.

Plenty of teams run both, because they solve different inputs. Featurebase owns the feedback your users opt into — the requests, the votes, the public roadmap they check before emailing support. A store-review tool owns the feedback they leave publicly on your store page, where a missed one-star reply costs you downloads. Neither replaces the other.

If you're comparing tools purely for the store side — monitoring, replying, and turning reviews into a roadmap — our [alternatives roundup](/alternatives) and [best app review management software for 2026](/blog/best-app-review-management-software-2026) line the options up side by side, and the [pricing page](/pricing) shows exactly where each tier draws its lines. ReplyArgus starts free for 100 replies a month and $29/mo on Indie for the knowledge base, the roadmap board, and full rule-based auto-publish.

Featurebase is a solid way to run the feedback your users hand you on purpose. Just don't mistake a full roadmap for a covered flank — the reviews on your store page are the feedback you didn't ask for and can't afford to ignore, and no feedback board reaches them. [Start free — no card](/signup) and watch Argus draft your first grounded, in-language store reply in minutes.

Featurebase is a trademark of its owner; ReplyArgus is not affiliated with or endorsed by it. Capabilities and pricing reflect public information as of mid-2026 and may have changed — confirm current details with the vendor before you buy.