When I first started collecting user feedback seriously, I made the same mistake most indie devs make: I treated App Store reviews as my only feedback channel. If users wanted to tell me something, that's where they'd do it. Right?
Then I added a feedback form to my app and discovered something that changed how I think about feedback entirely: the people who leave App Store reviews and the people who submit direct feedback are completely different audiences, telling you completely different things.
What App Store reviews tell you
Reviews are public, permanent, and emotional. People leave them when they feel strongly — either love or hate. The signal is genuine but filtered through frustration, delight, or impulse.
Reviews are great for understanding your public perception, tracking sentiment over time, catching post-update regressions (complaints come in waves after bad updates), and seeing how you compare to competitors (users often name alternatives in 1-star reviews).
But reviews have blind spots. They're bimodal — you get 5-stars and 1-stars, but the nuanced middle is underrepresented. In my analysis of 10,000 reviews, the 5-star reviews were almost useless for product decisions. "Great app!" doesn't tell you what's working. The actionable stuff lived in 2-3 star reviews, which are the minority.
Reviews also have a huge selection bias. The users who leave reviews are a tiny fraction of your user base — typically under 1%. And they skew toward extremes. Your silent majority, the 99% who quietly use your app every day, never shows up in reviews.
What in-app feedback tells you
Direct feedback through a form, a "Send Feedback" button, or a QR code reaches a completely different audience. These are users engaged enough with your app to actively seek out a feedback channel, but not frustrated enough to go nuclear in the App Store.
The quality difference is dramatic. When I added a feedback form to my apps, I found that direct submissions generated 4x more actionable bug reports than App Store reviews. Form submissions included specific steps to reproduce, device information, and coherent problem descriptions. Reviews said "it crashes sometimes."
Direct feedback also captures feature requests from your power users — the people who love your app enough to ask for more, but wouldn't bother writing a public review about a missing feature. These requests are gold for roadmap planning.
The two channels reveal different problems
Here's a real example. Last year, one of my apps had a bug where background sync would fail on certain network configurations. In App Store reviews, the complaints looked like: "Sync doesn't work. 1 star." and "Lost my data, this app is garbage."
From the feedback form, I got: "Background sync seems to fail when I'm on corporate Wi-Fi with a proxy. Works fine on home Wi-Fi and cellular. Running iOS 18.1 on iPhone 15 Pro."
Same bug. Completely different level of usefulness. The review told me users were angry. The form submission told me how to fix it.
If I'd only had reviews, I'd know I had a sync problem but would have spent days reproducing it. With the direct feedback, I had a fix shipped in 48 hours.
When reviews are the better signal
Reviews win in a few specific scenarios.
Public trust and conversion. Your App Store rating directly impacts downloads. No amount of internal feedback data matters if your public rating drops below 4.0. Reviews are your public reputation — they need active management.
Competitive intelligence. You can read your competitors' reviews. You can't read their feedback form submissions. Competitor reviews tell you what their users want and aren't getting — which is your opportunity.
Post-update regressions. When you ship a bad update, reviews spike within 24-48 hours. It's the fastest public signal that something went wrong. Your feedback form might catch it too, but the volume and urgency of review spikes is unmatched.
ASO impact. Review volume and rating directly affect App Store search rankings. More reviews (even mixed) = better visibility. This is a growth lever that direct feedback doesn't touch.
When direct feedback is the better signal
Direct feedback wins for day-to-day product decisions.
Bug reports. Form submissions with structured fields (device, OS, steps to reproduce) are infinitely more useful than "it crashed."
Feature prioritization. Users who take the time to submit a detailed feature request through a form are telling you what they'd pay for. Review-based feature requests are often angry demands — "Why doesn't this do X?!" — which overweight the loud minority.
Onboarding problems. Users confused by your app rarely leave reviews. They just quietly delete it. A well-placed "Having trouble? Tell us" button during onboarding catches the users you'd otherwise lose silently.
Private issues. Some feedback is sensitive — account problems, billing questions, data concerns. Users won't (and shouldn't) put these in public reviews. A direct channel handles them safely.
The consolidation argument
Here's the real problem: if reviews live in App Store Connect and direct feedback lives in your email or a Google Sheet, you're managing two disconnected systems. Patterns that span both channels become invisible.
Three users report a sync bug via your feedback form. Two others leave 1-star reviews about the same bug. If you're looking at each channel separately, you see two minor problems. In a single inbox, you see five reports of the same issue — and it jumps to the top of your priority list.
This is why we built AppTriage with both channels in the same inbox. Not because either channel is better, but because the combination reveals things neither shows alone.
The practical setup
If you're starting from zero, here's what I'd set up today.
For reviews: Connect the App Store Connect API to pull reviews automatically. Reply to everything under 4 stars within 24 hours.
For direct feedback: Add a "Send Feedback" link to your app's settings screen. Use a simple web form with fields for: feedback type (bug, feature request, other), message, and optional email. That's it. Don't over-engineer the form.
For both: Put them in the same system. Tag everything. Review weekly. Look for patterns that cross channels.
You'll be surprised how quickly the combined view changes your roadmap.
Collect both in one place. AppTriage's in-app feedback form captures direct messages, while the review tracker auto-imports App Store and Google Play reviews. One inbox, two feedback channels. Try free.