What percent of mobile apps show an in-app rating-request screen?

12.7% of tracked apps (103 of 809) show an in-app rating-request screen [1]. A stricter canonical count puts dedicated app-rating screens at just 22 apps [2], so somewhere between ~3% and ~13% of tracked apps have a captured rating prompt. Either way it's a minority pattern, and it's notably absent in Shopping (0 of 44) and Medical (0 of 20) [3].

103 of ~800 tracked apps (12.7%) show a rating-request screen; the strict canonical count is 22 apps — Lazyweb Research, July 2026.

Lazyweb Research · n=809 · Published 2026-07-07

retentionnotificationsux-patternsmobileexperiments

The finding

The broad tag match finds rating prompts in 103 apps (12.7%), while the stricter 'app rating' canonical category appears in just 22 apps [1][2]. By vertical, numerators are small and some are zero [3]:

VerticalApps w/ ratingDenom
Health & Fitness1056
Travel641
Productivity664
Finance547
News546
Shopping044
Medical020

How to apply it

Rating prompts are a minority surface, and where they appear they cluster in utilities, wellness, travel, and news (named examples: AccuWeather, Calm, Expedia, CBS News) [1]. The zeroes in Shopping and Medical are informative: commerce and health apps often skip the prompt, likely to avoid interrupting a purchase or a sensitive moment. Time the prompt after a clear success (a completed workout, a delivered order) rather than on launch, and gate the OS review sheet behind a soft in-app ask.

Caveats

Two figures bracket the truth: 12.7% (broad tags, 103 apps) and 22 apps (strict canonical) [1][2]. Per-vertical numerators are tiny (0-10), so publish absolute counts and avoid headline percentages below 8 apps [3]. Rating prompts are transient and easily missed in capture — a lower bound.

The numbers

StatComputed from
12.7% (103 of 809)prevalence_rating_request: 103/809
22 apps with app-rating canonical screencanonical_category_census.app_rating_screens (22)
Health & Fitness 10/56, Shopping 0/44, Medical 0/20rating_request_by_category
Methodology. Universe: 809 apps with >=1 captured screen. Method: COUNT(DISTINCT company_name) matching rating tags (broad) plus strict canonical app-rating count; per-vertical splits n>=20. July 2026. Caveat: transient, capture-limited; small numerators.

Sources & citations

  1. [1] Lazyweb Research analysis of 809 mobile apps (809 mobile apps with >=1 captured screen; 751 with tag data; median 41 screens/app), July 2026. Prevalence = COUNT(DISTINCT company_name) over LLM synonym tags; denominator is 809 tracked apps (reported conservatively over all apps-with-screens, not the 62,376-row companies table). Lower bound: only reflects screens Lazyweb captured (median 41/app).

Source: Lazyweb Research — proprietary analysis of real, in-market app screens. Cite as Lazyweb Research, 2026-07-07.

Related questions

Explore the underlying screens, flows, and A/B tests inside Lazyweb. More research