ASO August 22, 2026 · 4 min read

Should You Reset Your App Store Ratings with Your iOS 26 Update?

The 'Reset App Summary' checkbox returns with every major iOS cycle — but with iPhone 17 launch traffic weeks away and iOS 26 bringing a new visual identity to millions of apps, the 2026 calculus is more nuanced than usual.

By the AppsOps news desk · August 22, 2026

Every time developers submit a major app update, App Store Connect offers a quiet checkbox: "Reset App Summary." With iPhone 17 launch traffic weeks away and iOS 26 delivering the most sweeping visual overhaul since iOS 7, that decision carries more weight than usual this cycle. Here's how to think through it without defaulting to habit.

What the Rating Reset Actually Does

When you submit a new version and check "Reset App Summary," your existing star ratings and review count are archived — they don't disappear from Apple's systems, but they stop counting toward your current App Store listing. New visitors see a blank slate until your updated version accumulates fresh ratings.

This is effectively a one-way door. Once the update goes live with the reset applied, the counter starts from zero. There is no rollback option.

When Resetting Makes Sense

Three scenarios where a reset is genuinely the right call:

Your current average is a drag below 3.8. If years of reviews about a broken feature, a now-fixed pricing grievance, or a UI that bore no resemblance to your screenshots have driven you below 3.8 stars, resetting alongside a real overhaul is defensible. Apps shouldn't carry ancient structural baggage forever.
You've made a major product change. iOS 26 is prompting genuine redesigns — Liquid Glass navigation elements, updated layout patterns, completely new screenshot sets. If your app looks and works materially differently from what reviewers were rating, old reviews may actively mislead incoming users about what they're downloading.
Your monetization model changed. If you moved from one-time purchase to subscription, or restructured your paywall significantly, reviews referencing the old model confuse prospects at the worst moment — right when they're evaluating whether to convert.

When to Protect Your Ratings

Conversely, if you've built a 4.5-star average with 10,000+ ratings across two or three years, resetting erases social proof that is genuinely difficult to rebuild. New users — especially in competitive categories — use rating count and average as a proxy for trustworthiness before reading a single review.

There's also a conversion rate argument. App Store search-result cards display your average prominently. Dropping from 4.5★ (12k ratings) to a blank during the highest-traffic month of the year — iPhone 17 launch week triggers an enormous new-device-setup flood — is a real risk that may outweigh any benefit from shedding mixed reviews.

Scenario	Reset?
Below 3.8 average, major redesign	Yes
4.0–4.4, meaningful new features	Consider — assess review content
4.5+ with 5k+ ratings	No — protect that credibility
Monetization model change	Usually yes
Routine compatibility update	No

The iOS 26 Timing Wrinkle

Here's what makes August–September 2026 different from past cycles. iOS 26 brings a new visual language to a large share of apps simultaneously. Apps that haven't fully adopted Liquid Glass aesthetics may start accumulating reviews calling out the "outdated look" or "doesn't feel like iOS 26" — even if the app works flawlessly. If your iOS 26 update is genuinely substantial in scope, a clean rating slate right as iPhone 17 brings its biggest new-user cohort of the year is an appealing proposition.

On the other hand, if your update is primarily a compatibility pass with minimal feature or visual changes, there's no upside to resetting a healthy rating average. The Liquid Glass concern only applies if your updated build looks materially different from what your existing reviewers rated.

Review Velocity After a Reset

One factor that's often underweighted: if you reset, you need an active review-request strategy firing from day one of the new version. Apps sitting at zero ratings in search results feel risky to new users, especially in productivity, finance, or health categories where trust is the purchase trigger.

Build in a post-update review prompt via StoreKit's requestReview API, triggered by positive engagement signals — not app launch. A prompt shown after a user completes your onboarding flow, finishes their first meaningful session, or hits a positive outcome in-app will rebuild your rating base far faster than a cold on-open prompt. Reports suggest well-timed prompts convert at 3–5× the rate of generic launch-gate prompts.

Ratings Across Storefronts

One nuance that catches multi-territory apps off guard: App Store ratings are per-storefront. Resetting in the US does not automatically wipe your rating summary in Japan, Germany, Brazil, or South Korea. Each storefront has its own rating count and average, and the reset applies wherever you choose to apply it during submission.

If you're running a localized listing across multiple markets — which for most growth-stage apps means all 39 App Store territories — check each storefront's current average before deciding. A 4.6 in Japan is worth protecting even if your US store is sitting at 3.7. The decision can be market-specific. And if you're resetting in a market and relaunching your listing, that's also the right moment to refresh your localized screenshots — new ratings build faster when the listing looks right for each locale.

Bottom Line

Don't reset by default, and don't protect by default. Run the actual numbers: your current per-storefront averages, the scope of change in your iOS 26 build, and the traffic window you're submitting into. For iOS 26 builds, the calculus leans toward resetting if you're below 4.0 with a genuine overhaul, and toward protecting if you're above 4.3 with thousands of ratings. The late-August submission window — before iOS 26 GM drops — is your last realistic chance to make this call deliberately rather than reactively.

Sources and further reading