What's the best way to get user feedback on an app?

Pair a lightweight in-product widget (one question, one text field) with 3–5 recorded user interviews per month. The widget catches volume, the interviews catch depth. Anything more elaborate is usually founder theatre.

Should I use NPS surveys?

For early-stage products, no. NPS becomes useful around 500+ active users where the sample size stabilizes. Before that, qualitative feedback beats the score.

How do I get users to leave feedback?

Ask at the moment of value — right after an activation event, not on page load. Keep it to one question. Reply personally to every response for the first 200. That reply is what generates the next feedback.

// guide · user feedback

Get Feedback From My App

In-product widgets, cohort interviews, session replay, and NPS — the tactics that produce actionable feedback instead of noise, ranked by what actually ships changes.

The feedback stack (in order of ROI)

1-to-1 interviews. Nothing beats a 20-minute recorded call. Aim for 3–5 per month. Ask about last week, not the future.
In-product micro-widget. One question ("what's missing?") pinned to the moment of value. Anonymous is fine — depth matters more than name.
Session replay. Watch 10 recorded sessions a week. You'll spot rage-clicks and confused flows no survey catches.
Support inbox. Every support ticket is unfiltered feedback. Tag them by theme monthly.
Public roadmap / upvote board. Great for scale, dangerous early — you can end up building the loudest 3 users' wishlist.

How to ask so people answer

Trigger the ask at the moment of value — right after they completed the thing your app is for.
One question. Short. Specific. "What almost stopped you today?" beats "How was your experience?"
Reply personally to every answer for the first 200. That reply is what generates the next round.
Never require login to answer. Friction kills honesty.

Turn feedback into shipped changes (fast)

Feedback that doesn't lead to a shipped change is a slow trust-killer. If a user tells you something's broken, they should see a fix or a public no within 30 days.

Publish it. A visible changelog turns feedback into a compounding trust asset. Users who see their own quote in a release note become evangelists.

FAQ

What's the best way to get user feedback on an app?: Pair a lightweight in-product widget (one question, one text field) with 3–5 recorded user interviews per month. The widget catches volume, the interviews catch depth. Anything more elaborate is usually founder theatre.
Should I use NPS surveys?: For early-stage products, no. NPS becomes useful around 500+ active users where the sample size stabilizes. Before that, qualitative feedback beats the score.
How do I get users to leave feedback?: Ask at the moment of value — right after an activation event, not on page load. Keep it to one question. Reply personally to every response for the first 200. That reply is what generates the next feedback.

Publish a changelog on rankraw

Every shipped feature becomes a mini-launch. Free for every product on the board.

submit your product →how ranking works

Related playbooks

Beta Testing Your App

Recruit testers, ship weekly, learn fast.

App Testing in a Sandbox

Let visitors try your product before they sign up.

Evaluate My App

A no-BS rubric for judging early-stage apps.

What is Vibe Coding?

The 2026 guide to ship-by-prompt AI tools.

→ not sure where to start? pick by intent

Get the indie-founder playbook

One short email a week — the launch tactics, sandbox tricks, and distribution plays we see actually working on rankraw. No spam. Unsubscribe anytime.