Social Proof in App Store Screenshots: Ratings, Reviews and Awards

Quick answer: On the App Store, you can show ratings, review quotes, press mentions and awards in screenshots if every claim is true, current and verifiable, you have the right to use any logos, and nothing implies Apple endorses your app. Google Play is stricter: its preview asset guidance says to avoid ratings, rankings, testimonials, accolades and awards in screenshots and the feature graphic.

Social proof answers the shopper's question "can I trust this app?". Each type carries a different burden of proof. The examples below show the format only; use your own real figures.

A useful test: if a reviewer asked "where does this come from?", could you link to the source in one minute? If not, leave the claim out.

Apple has no guideline that bans ratings or awards in screenshots, but several rules shape how you can use them:

• Guideline 2.3 (Accurate Metadata): screenshots must accurately reflect the app's core experience, and Apple asks you to keep them up to date with new versions. A rating badge from two years ago, or an award you no longer hold, works against that.
• Guideline 2.3.3: screenshots should show the app in use. A screen that is only a wall of quotes with no UI is weaker, and riskier, than a quote placed next to real UI.
• Guideline 2.3.7: metadata shouldn't be packed with irrelevant phrases, and subtitles must not make unverifiable product claims. Treat "the best app ever" in a screenshot the same way.
• Guideline 5.2.1: don't use protected third-party material such as trademarks without permission. That covers press logos and award marks.
• Guideline 5.2.4: don't suggest or imply that Apple endorses your app. Apple applies the Editors' Choice badge itself, so the cautious approach is to leave Apple badges and the App Store logo out of your screenshots.

Apple's own product page advice suggests that if you mention an accolade, you put it at the end of your description or in your promotional text. That's a strong hint: lead your screenshots with the product, and give recognition a supporting role. The screenshot guidelines explainer covers the rest of Section 2.3, and the promotional text guide shows how to rotate accolades without a new screenshot set.

Google Play draws a firmer line. Its Metadata policy prohibits text or images in the app title, icon or developer name that indicate store performance or ranking (such as "#1" or "App of the year"), price or promotional information, or Google Play programs. It also doesn't allow unattributed or anonymous user testimonials in the app description.

For screenshots and the feature graphic, Google's preview asset guidance asks you to avoid any content that reflects or suggests Google Play performance, ranking, user testimonials, accolades or awards. For the feature graphic it specifically names words like "Best", "#1", "Top", "New", "Free" and "Million Downloads".

In practice, keep star rows, review cards and laurels out of your Play screenshots and feature graphic, and put real, attributed recognition in your full description instead. Google Play screenshot best practices covers what to show instead.

1. Use your real, current numbers. Take the average from App Store Connect for the storefront the screenshot targets, and round down, not up.
2. Say what the number means. "4.7 average from US ratings" says more than a bare "4.7". If you cite a count, phrase it as a floor that is true today, such as "50,000+".
3. Quote real reviews accurately. You can shorten a quote, but don't change its meaning or merge two reviews into one. Keep a record of the original.
4. Get permission for press logos. A publication's logo is its trademark. Without permission, use the quote and the publication name in plain text, or leave it out.
5. Name awards exactly. Use the official award name and year as the awarding body states them, and avoid recreating Apple or Google artwork.
6. Keep it supporting, not dominant. A laurel or star row works as an accent on a screen that also shows UI, or as one dedicated screen later in the set.
7. Localize claims carefully. A rating or press quote that holds in the US may not apply in Germany or Japan. Use region-appropriate proof, or drop the claim in that localization.

Your first screenshot has one job: show what the app does. Social proof answers a later question, so it usually earns its place in the middle or at the end of the set, or as a small accent on the first screen when it's strong and specific.

Remember that both stores already show your live star rating on the product page. A rating badge in a screenshot repeats information shoppers can see, so it's only worth the space when it adds context: a review count, a specific quote or a real award.

Social proof ages faster than anything else in your screenshots. Add a short check to every release:

• Re-check your average rating and counts in App Store Connect and Play Console.
• Remove awards that are no longer meaningful, and always show the year.
• Confirm press quotes still match the live article.
• Update every localization, not only English.
• Re-read Apple's Guideline 2.3 and Google's preview asset guidance before a major refresh.

On the App Store, screenshot changes are typically submitted along with a new app version, so plan updates into your release cycle. If you need to refresh trust signals between releases, promotional text is the flexible place for them. Building the underlying reviews takes work too; see how to get more app reviews and how App Store ratings work.