Product →Examples →FAQ →All solutions →About →
Business problemsHow it worksRolesOrganizations
Scopeout for consumer apps

Retention, engagement and paying users. Every release.

D1, D7 and D30 retention, DAU/MAU and premium conversion, watched per app version. Push timing, onboarding and paywalls tested on the numbers that matter for a consumer product.

Retention · iOS 5.2 vs 5.1
D158%
D731%
D3014%
D7 vs 5.1−6 pts · finding opened

Built for the metrics a consumer app lives by

The loop is the same. The evidence, the tests and the numbers are tuned to millions of users and weekly releases.

Retention curves per version

D1, D7 and D30 by cohort and app version, so a release that hurts retention is caught the week it ships.

D7 retention · by app version
5.1 · 37%5.2 · 31%−6 pts · outside band

Onboarding and permissions, tested

First-session value, permission prompts and push opt-in as real variants, measured on day-one return.

A · 3 screens
B · value first
C · skip

Paywalls measured on upgrades

Paywall timing, plan order and feature previews tested on premium conversion with refund guardrails.

Paywall after first save · premium conversion
control · 2.1%variant · 3.4%+1.3 pts · promote

Built for consumer teams

App-store reviews · clustered · 2,400 this month
Login loops after update612
Too many notifications330
Crashes on export230
Love the new editor184
Top clusterconfirmed in 41 sessions

Review and rating clusters

App-store reviews clustered into product problems and confirmed in sessions.

Push at 7pm vs 9am · D7 return
9am · 22%7pm · 29%+7 pts · promote

Push timing and content

Re-engagement pushes tested on D7 return, not open rate.

Week-one actions that predict D30
Saved 3+ items3.4x
Enabled push2.1x
Followed a friend1.8x

Habit loops

The week-one actions that predict D30, turned into nudges on your system.

Release 5.2 · record
D7−6 pts · login loop
Fix5.2.1 · shipped Thu
D7 after fixrecovered to 36%
Reviewscluster closed

Release record

Every version with its retention effect and the findings it opened.

Start from a prompt.

Diagnose

“Why did D7 retention drop for the iOS cohort after 5.2? Check reviews, sessions and the release.”

Run this when my batch opens →
Test

“Propose three onboarding changes to lift D1 retention, ranked by expected lift.”

Run this when my batch opens →
Review

“Which push experiments moved DAU this month, and which hurt uninstalls?”

Run this when my batch opens →

Questions, answered.

Which analytics does it read?

Amplitude, Mixpanel, Firebase and your warehouse for events; App Store and Play reviews for the voice of users.

Can it ship to an app store?

Build opens the PR and Publish rolls out behind remote-config flags; the store release stays with your team.

How does it handle millions of users?

Tests split by flag, guardrails watch uninstalls and crashes, and rollouts go out in stages.

Stop running the business. Start directing it.

Join the waitlist

Private beta. We onboard teams in small batches. Or contact us.