Rating Prompt

Definition

An in-app dialog or notification that requests users to rate and review the app. Rating prompts are system-managed interfaces provided by Apple, Google, and Amazon that appear within the app without external redirection. These are the primary mechanism for generating new reviews organically.

Effective rating prompts can improve the average star rating by 0.3-0.8 stars over 6 months by timing the request when users are most satisfied and therefore likely to leave positive reviews. Conversely, poorly-timed or excessive prompts trigger rating fatigue and potentially worse ratings.

How It Works

Apple App Store

Apple provides SKStoreReviewController (iOS 10.3+), a system-managed rating dialog that displays natively within the app. Developers cannot customize the appearance of the dialog itself—Apple maintains complete control over the UI. The system strictly limits prompts to a maximum of 3 times per 365-day period per app.

When SKStoreReviewController is called, the system decides whether to display the prompt based on user engagement patterns and frequency criteria. There is no guarantee the dialog will appear every time it's requested. The system enforces the 3-per-year limit transparently, and review submission goes directly to the App Store without leaving the app.

Developers trigger the prompt via code at strategic moments (e.g., after completing a task), and the system decides whether the user should see it.

Google Play Store

Google Play provides the In-App Review API, which similarly displays a system-managed dialog without app-level customization. Like Apple, Google controls whether the prompt actually displays based on user engagement history and frequency rules. Google does not publish a hard limit on prompt frequency, but testing shows the system enforces a soft limit to prevent prompt fatigue.

The in-app review dialog appears as a material design bottom sheet. Reviews submitted through the in-app API appear directly on the Google Play Store product page. Timing and display frequency are controlled by Google's system, not the developer—even if you request a prompt, Google may defer or suppress it.

Amazon Appstore

Amazon Appstore offers an in-app review prompt similar to Apple and Google. The dialog is system-managed with limited customization. Amazon enforces frequency limits to prevent user frustration. Reviews submitted through the in-app prompt appear on the Amazon product page and are weighted in the overall rating.

Formulas & Metrics

Rating Improvement from Prompts:

• Well-timed prompts: +0.3 to +0.8 star improvement over 6 months
• Optimal timing: immediately after achievement or positive interaction
• Review rate from prompted users: 2-8% (varies by app category and user engagement)

Prompt Effectiveness:

Effective Rate = (Users who completed review) / (Users shown prompt) × 100

• Typical range: 2-5% for standard apps
• Category variation: games 3-7%, productivity 1-4%, social 2-6%

Fatigue Threshold:

• 1 prompt per 30 days: minimal fatigue
• 1 prompt per 14 days: noticeable fatigue impact
• >1 prompt per 7 days: significant rating decline risk

Best Practices

1. Time for Positive Moments: Request reviews immediately after a positive user action (completing a level, successfully creating content, finishing a task, unlocking an achievement). Never prompt after errors or crashes.

1. Respect Frequency Limits: Implement 30-90 day delays between prompts to a single user. Use version-level tracking (e.g., "first launch of version 5.0") to avoid double-prompting on updates.

1. Avoid Dark Patterns: Do NOT use pre-screening dialogs (e.g., "Do you like the app?" → "Yes" → review prompt). Do NOT gate access to features behind rating completion. Do NOT offer rewards for ratings. These patterns violate app store guidelines and trigger user resentment.

1. Monitor Conversion Data: Track the ratio of prompts shown to reviews completed. Declining ratios indicate prompt fatigue or poor timing.

1. A/B Test Timing: Experiment with prompt timing—some apps see better conversion prompting after 10 minutes of use, others after 5+ minutes. Test moment-of-success events vs. session-start timing.

1. Use Contextual Language: While you cannot customize the dialog itself, you can customize the code trigger location and surrounding UI text. Place prompts contextually to signal why you're asking.

1. Suppress for Known Detractors: If possible, suppress prompts for users exhibiting high-crash or low-engagement patterns. They're unlikely to leave positive reviews anyway.

1. Track and Iterate: Monitor rating velocity before and after prompt rollouts. If negative velocity increases, reduce prompt frequency.

Examples

Timing Example - Gaming App:

A mobile puzzle game discovers that prompting users after completing Level 10 (a natural milestone) yields a 5% review rate with 4.5+ star average. Prompting after Level 5 yields only 2% rate with 4.1 star average (users less engaged). Final optimization: prompt after Level 10, max 1x per 60 days = steady 0.4 star rating improvement over 6 months.

Dark Pattern Violation:

An app tries the pre-screening approach: "Love the app? [Absolutely] [Not Really]". 95% click Absolutely (obviously), then prompt for review. Users feel manipulated because the affirmative was soft-committed but doesn't represent genuine satisfaction. Rating drops 0.3 stars within weeks, and the pattern violates App Store guidelines.

Fatigue Impact:

Fitness app A prompts after every workout (user exercises 4x/week = 4 prompts/week). After month 1, review rate drops from 3% to 0.5%, and rating declines to 4.1 (from 4.5) as users perceive the prompt as aggressive harassment. Fitness app B prompts max 1x/month = steady 2.5% review rate, 4.6 rating.

Dependencies

Influences

• Star Rating — Primary mechanism for generating new reviews; well-placed prompts drive 0.3-0.8 star improvement
• Rating Distribution — Timing affects which star levels increase; positive-timed prompts boost 4-5 stars
• Download Velocity — Apps with rising ratings (driven by rating prompts) experience accelerated growth

Depends On

• In-App Events — Events within the app trigger rating prompts; positive events → higher ratings
• user engagement — Engaged users more likely to leave reviews; prompt timing correlates with engagement metrics
• Conversion Rate — Rating prompts must be timed to maximize conversion likelihood without inducing prompt fatigue

Platform Comparison

Related Terms

• Star Rating
• Ratings and Reviews
• Rating Distribution
• Review Management
• In-App Events
• Conversion Rate
• user engagement
• Quality Score

Sources & Further Reading

• Apple App Store Review Guidelines: rating prompts section
• Google Play In-App Review API documentation
• App Store Connect documentation
• Mobile UX research on prompt fatigue and optimal timing
• ASO case studies on prompt effectiveness (AppFigures, Sensor Tower)