App Store reviews as social proof: how to use them honestly

You can use App Store reviews as social proof by quoting real reviews of your own app word for word, either with the reviewer's permission or without their name, and pairing each quote with the one claim it supports. Never edit a review's meaning, never stitch two reviews together and never invent one. Rules on using reviews in marketing vary by country and platform, so check the current guidance where you post.

Why do App Store reviews work as social proof?

Social proof is evidence that other people like the viewer already use something and found it worthwhile. In app marketing, your App Store reviews are the most direct source of it you have.

They help a post in three ways:

• They come from outside. Your copy says the app is good. A reviewer has no reason to.
• They use the viewer's words. Reviewers describe the problem the way your audience would, not the way your feature list does.
• They often name a moment. A reviewer who mentions the exact time or place they open your app has handed you a hook.

That last point matters more than it looks. Reviews are one of the best places to find the specific, everyday language that makes app copy stop sounding like an ad, even when you don't quote them directly.

Can you use App Store reviews in your marketing?

Many developers do, but there's no single rule that covers every case, and this post isn't legal advice. A few things are worth knowing:

• Reviewers wrote the words. A review is someone else's writing, published on Apple's platform. Rules on reusing it can depend on where you are and where you post.
• Advertising rules vary. Many countries have rules on testimonials and endorsements in marketing, including requirements that they're real, current and not misleading.
• Fake reviews are widely prohibited. Consumer protection rules in many places treat invented or misleading reviews and testimonials as deceptive.
• Apple has its own guidelines. Apple publishes rules for developers on ratings and reviews and on using App Store marketing materials. Check the current versions before you build a post around them.

If you're unsure, the cautious path is simple: quote only real reviews of your own app, ask permission where you can, remove identifying details where you can't, and don't change the meaning. When in doubt about a specific market, ask someone qualified there.

How to ask permission or anonymize a review

When you can ask

App Store Connect lets you post a public developer response to a review, but at the time of writing it doesn't give you a private way to contact the reviewer. So asking permission usually works only when the same person has reached you somewhere else:

• They emailed your support address about the same experience.
• They posted about your app publicly on social media.
• They sent feedback through a form inside your app.
• They're a beta tester or part of a community you run.

Keep the request short and easy to say no to. Tell them exactly which words you'd like to quote, where the post will appear and how they'll be credited (by first name, handle or not at all). Use the quote only if they say yes, and keep a record of that yes.

When you can't ask

A common, cautious approach is to anonymize:

1. Drop the reviewer's nickname. App Store nicknames are often real names or handles people use elsewhere.
2. Remove personal details inside the text. A child's name, an employer, a city or a health detail.
3. Attribute it generally. "From an App Store review" is honest and enough. You can add the month if it helps show the review is recent.
4. Keep the text otherwise word for word.

Anonymizing protects the reviewer. It doesn't make a quote more acceptable if it was never real, or if you changed what it says.

Rules for quoting App Store reviews honestly

1. Only your own app's real reviews. Never a competitor's, never a "composite", never one you wrote.
2. Word for word. If you shorten a review, mark the cut with an ellipsis (...).
3. Never change the meaning. Don't remove "not", "but", "used to" or "until the last update". A cut that flips the meaning is an invented review.
4. One review per quote. Don't stitch the best half of one review onto the best half of another.
5. Leave the words alone. Fixing an obvious typo is a judgment call; changing a word that carries meaning is not.
6. Don't cherry-pick misleadingly. If most recent reviews mention a problem you haven't fixed, a single glowing quote gives a false picture.
7. Keep it current. A review praising a feature you've since removed is no longer true. Retire it.
8. Never pay or reward for reviews. Apple's guidelines don't allow developers to manipulate ratings or reviews, and rewarded reviews make every quote you use less trustworthy.

Which reviews make the best posts?

Most reviews say something like "Great app, love it". That's nice to read and useless in a post. Look for reviews that do one of these:

• Name a specific moment. When, where or how they use the app.
• Describe a before and after. What their week looked like without it and with it.
• Mention an unexpected use. Something you didn't design for but they found.
• Answer a doubt. A reviewer who expected it to be complicated and found it wasn't.
• Mention a feature by what it does. Not its name in your app, but the effect it has.

Skip reviews that mention competitors by name, criticize other people, or praise something that's no longer true.

Formats for turning reviews into posts

Two cautions for the formats above. Don't recreate the App Store's interface with edited text, because a fake screenshot of a review looks like a real one. A quote card in your own design is clearer and more honest. And if a voice-over reads a review aloud, label it on screen ("from an App Store review") so nobody mistakes the voice for the reviewer's own.

For review carousels, the carousel playbook for apps covers slide structure and the last slide. The "You asked, we built" format is one of the most convincing, because it shows you listen. It pairs well with posts about your app updates.

Pair each review with the claim it supports

A review on its own is a compliment. A review next to a specific claim is evidence. Decide the claim first, then find the review that backs it.

1. Write the claim. One sentence your listing supports, such as "setup takes a couple of minutes".
2. Search your reviews for it. Look for reviewers who mention that exact effect in their own words.
3. Pick the most specific one. A review that names the moment beats one that just agrees.
4. Show the feature. Put a real screenshot of the relevant screen beside or after the quote.
5. Let the post make one point. One claim, one review, one screenshot, one call to action.

Here's how that looks for a fictional meal planner:

The second column describes a type of review on purpose. The quote itself has to come from your real reviews, in the reviewer's words.

How to mention your star rating honestly

A star rating is social proof in one number, but it's easy to stretch.

• Use the number on your listing at the time you post. Don't round 4.6 up to "almost 5 stars".
• Say when. Ratings change, and an old post with an old rating can become untrue. "Rated 4.6 on the App Store at the time of posting" is safe.
• Remember ratings can differ by country. If you post to an audience in one country, the rating they see in their App Store may not match yours.
• Mind small numbers. A perfect score from a handful of ratings isn't much proof, and viewers who check will notice.

ReelMyApp reads your listing, including its rating, and never invents reviews, rankings or user counts. If you want a real review in a carousel, that's a deliberate step you take: rewrite a slide's headline or supporting line with the exact quote, then redraw the slide. That keeps every word of the quote yours to check. For the wider workflow of building posts from your listing, see how to turn your App Store or Google Play listing into short videos.

Common mistakes with review-based posts

• Editing for punch. Turning "pretty good once I figured it out" into "pretty good" changes the review.
• Stitching quotes. Two halves of different reviews presented as one.
• Fake review screenshots. A mockup of the App Store's review UI with your own text in it.
• Quoting very old reviews. Especially about a version that no longer exists.
• Asking for reviews in exchange for something. It breaks trust in every review, including the honest ones.
• Using names without consent. Even a nickname can identify someone.

Key takeaways

• Quote only real reviews of your own app, word for word, with permission or without identifying details.
• Never invent, stitch or reword a review in a way that changes its meaning.
• Choose reviews that name a specific moment or a before and after, not general praise.
• Pair each review with one claim from your listing and a real screenshot that shows it.
• State your star rating exactly as listed, with when it's from.
• Rules on reviews and testimonials vary, so check the current rules where you post.

Frequently asked questions

Can I use App Store reviews in my social media posts?

Many developers quote their own app's reviews, but rules on using customer words in marketing vary by country and platform. Quote word for word, ask permission or remove identifying details, and check the current rules where you post if you're unsure.

Do I need permission to quote an App Store review?

Asking is the safest and most respectful option when you can reach the reviewer. When you can't, a common approach is to quote the text without the reviewer's nickname or any personal details. This isn't legal advice, so check the rules that apply to you.

Can I shorten or edit a review before quoting it?

You can shorten it, marked with an ellipsis, as long as the meaning doesn't change. Never remove words like not, but or used to, and never combine two reviews into one quote.

Can I use AI to write reviews or testimonials for my app?

No. A review or testimonial you wrote yourself, by hand or with AI, is a fake review. Consumer protection rules in many countries prohibit them, and they break the trust the post is trying to build.

Should I mention my app's star rating in posts?

Only the real rating, as shown on your listing when you post, without rounding up. Ratings change over time and can differ by country, so note when and where the number is from.