Star rating is the third most important ASO factor after title and screenshots. Drops from 4.5 to 4.0 can cut conversion 20-40%. The fix has three parts: address what low-star reviews tell you, respond professionally to negative reviews, and prompt happy users at the right moment to balance the rating distribution. See the App Audit hub for the broader programme.
Don't dismiss them. Categorise: - Crashes / bugs (technical — fix in next release) - Missing features (roadmap input) - Pricing complaints (positioning, not bug) - Account / billing issues (support process problem) - Onboarding confusion (UX problem) - Marketing mismatch (your store listing oversells) Each category needs a different response: - Bugs: fix and respond to reviewers explaining the fix shipped - Features: roadmap acknowledgment - Pricing: re-evaluate positioning, perhaps tier additions - Billing: improve support flow - Onboarding: improve in-app first-run experience - Mismatch: adjust marketing or improve fit
Pattern that works: - Acknowledge the specific issue - Explain what's being done - Provide a support contact - Update the response when fix ships Tone: - Empathetic, not defensive - Specific, not boilerplate - Brief (2-4 sentences typical) Example: "Sorry the sync issue caused data loss for you. We've identified the cause in version 2.3.1 — fix shipped. Please email support@acme.com with your account ID and we'll restore data from backup." Apple and Play both let you respond. Don't ignore — silence signals neglect to other users reading reviews.
iOS SKStoreReviewController and Android Play Core in-app review API both throttle prompts. Apple allows ~3 per year per user. Use them carefully:
Bad timing (low yield, often negative): - First app launch - Right after error or crash - During free trial signup - Immediately after onboarding Good timing (high yield, positive): - After user completes meaningful goal (closed a deal, saved a file, hit a streak) - After 3rd or 4th session (engagement signal) - After successful transaction completion - After positive in-app feedback signal (NPS, thumbs up) - Never during error states
Ask in-app first: "How likely to recommend Acme?" 1-10 Score 9-10 (promoters): show review prompt Score 7-8 (passives): ask "what would make it 10?" Score 0-6 (detractors): "what went wrong?" → support flow This raises the average store rating because you only prompt satisfied users for store reviews. Detractors get a private support channel where you can fix issues before they leave negative reviews publicly. Important: this is selective routing, not gating. Users can always leave reviews voluntarily.
Old reviews don't auto-expire. Recovery requires NEW reviews diluting old: Current rating: 3.8 Goal: 4.4 If you have 1,000 lifetime reviews averaging 3.8 (3,800 stars): Need new reviews averaging 4.7+ stars to drift up At 100 new 4.7-star reviews per month: - Month 3: ~4.0 - Month 6: ~4.2 - Month 12: ~4.4 The math is unforgiving. Rating recovery is slow. Best to prevent low ratings via UX/bug work than to recover.
Apple allows resetting your rating with each major version update. Use carefully — you reset GOOD ratings too. Worth resetting only if: - Old rating was very low (< 3.5) - Major version is genuinely substantially different - You're confident the new version will earn higher ratings - You can drive prompt volume in first 30 days post-launch Reset wrongly = lose hard-won 4.5-star history.