DEV Community

ReviewFold
ReviewFold

Posted on Originally published at reviewfold.com

What 200 app reviews didn't say

A developer in r/AppBusiness did something braver than most: he rebuilt his Bible app around a single insight. His claim was that the language in apps like his — Amen buttons, "your faith is growing" pop-ups — tells doubters they don't belong yet. So he rewrote the app for people who aren't sure.

Then, in the same post, he listed what he still needed to know. One item was three words: "Reviews?"

So I pulled 200 of them.

What I actually read

The 50 newest US App Store reviews for four apps in that category: YouVersion Bible, Hallow, Glorify, Abide. 200 reviews, 15 of them rated 1 or 2 stars.

Here is what those 15 are complaining about, sorted by subject:

What the review is about Count What it sounds like
Money 8 paywall, trial charged early, "free" then locked
Content or doctrine 4 a verse removed, kids' content discontinued, "too childish"
Bugs and UX 2 lost streaks, can't find a book
A mis-tap on the star rating 1 five stars of praise, filed under two

Eight of fifteen are about money. That is the finding I would act on, and I'll come back to it.

But the first thing worth saying is what isn't in the table. Zero of the 15 mention feeling judged, excluded, or talked down to. Not one says the app assumes you already believe. The closest thing runs the other way — a one-star review calling a meditation app demonic for not being biblical enough, and another asking why a verse had been removed: "Is because this is a hallow bible??? Empty of Jesus?"

Silence is not a result

If doubters were leaving the big apps because the wording excluded them, that complaint should be somewhere in 200 reviews of the four biggest apps in the category. It isn't there. That is real information, and it would be easy to stop and tell him his insight was wrong.

I don't think that's what it means, and the reason matters more than the conclusion.

There are two explanations that produce exactly this data:

He's wrong. People don't leave these apps over the copy. They leave over the subscription. The rewrite was aimed at a door nobody was standing at.

He's right and nobody wrote it down. Someone who feels judged by an app usually deletes it. They don't open the review screen and type "I felt unwelcome" — that requires more investment in the app than they had. The people who do write reviews are the ones committed enough to be disappointed by something specific: a charge, a missing verse, a lost streak.

Both explanations fit fifteen complaints perfectly. The reviews cannot tell them apart. That isn't a flaw in the reviews; it's what reviews are.

So the honest position is narrower than either: the claim is unverified, not disproven. It might be the most important thing about his product, and it might be a story he told himself after the fact, and 200 reviews of other people's apps will never decide it.

There is a version of this that does decide it, and it's already on his list. Onboarding. If doubters arrive and then leave, that shows up in first-session drop-off by entry point. If they never arrive, it shows up in install-to-first-open. Reviews are simply the wrong instrument for a question about people who already installed.

The three questions that got merged into one list

This is the part I'd underline, because the post itself blurred it.

"Retention by onboarding answer? Reviews?" reads like three items on one to-do list. They aren't the same kind of question and they don't take the same instrument:

Question What answers it What it can't tell you
Why do strangers never arrive? Reviews of the apps they chose instead Anything about the people who did arrive
Why do the ones who arrive leave? Onboarding and first-session data Anything about people who never installed
Would this wording push a doubter away? Neither. You need a test with doubters in it —

Reviews explain the demand side before you have demand. They are the only one of the three you can read today, with zero users. But they answer the first row, not the third — and his rewrite was about the third.

That's the trap: reviews are available, so they get asked everything.

What the eight money complaints do say

Back to the part that isn't ambiguous. Eight of fifteen complaints in this category are about being charged, and they are specific:

"why do all these companys charge money for time and more understanding about god" — 2 stars, Abide

"It's sad another app that advertises as being free then after you download it everything has a lock on it." — 1 star, Abide

"I used to use this app every day, and it was free and really well done, but now you have to pay" — 2 stars, Glorify

That is not a hunch about what might resonate. It's a complaint eight people took the trouble to type, in a category where the total pool of complaints I saw was fifteen. And it points at a claim with an unusual property: it can be checked before install. "Free, no subscription, nothing locked" is verifiable on a store listing in four seconds — which is exactly what a positioning claim has to survive.

His instinct about the copy might also be right. But the copy fix is a maybe, and the pricing gap is documented. If he only has time for one, the second one is the one with evidence behind it.

Three limits on all of this

The four samples cover very different periods. Same 50 reviews per app, wildly different windows: YouVersion's were all posted on a single day, Abide's spanned two and a half months. Counting the same number of reviews gave me four different time slices, so "8 of 15" is not a rate — it's a description of what was visible on 12 November. If you repeat this, fix the window first and count second.

One storefront, one sort order. US App Store, "most recent," and Apple's public review feed is patchy enough that any sample from it needs a date attached. This is a sample of what the feed returned, not a census of the category.

The bucket labels are mine. Deciding that "advertising" counts as a money complaint and "too childish" as a content complaint is a judgment call; a different reader would move one or two of the fifteen. The reviews are quoted above so you can disagree with my priority ordering without having to trust my labels.

The general shape

The useful habit here isn't "read the negative reviews." Most people who tell you that stop at the counting.

It's asking, for any claim you're about to build a product on: what would I expect to see in the public record if this were true, and is it there? Sometimes the answer is yes and you get eight people complaining about money. Sometimes the answer is no, and you learn that your evidence is a memory of a conversation rather than a finding — which is still worth knowing before you rebuild the app around it.

Two hundred reviews can't tell you whether a doubter feels judged. They can tell you that nobody wrote it down, and that eight people wrote down something else instead. The second one is actionable today.

If you want the mirror image of this exercise — deliberately looking for what reviews do contain rather than what's missing — that's a different and easier read: finding product strengths in app reviews.


Disclosure: I work on ReviewFold, which analyzes app reviews. The counts and quotes above come from Apple's public US App Store review feed, pulled on 12 November 2026 (50 newest reviews for each of four apps, US storefront, most-recent sort). AI assistance was used for editing; the review counts and the quotes were read from the feed directly.

Top comments (0)