Appfigures vs RevenueCat charts: which covers a portfolio?

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

Appfigures and RevenueCat's built-in charts solve different problems: Appfigures tracks store-side performance — rankings, reviews, downloads, keyword position — across App Store and Play Console, while RevenueCat's dashboard tracks subscription revenue and churn for apps using its SDK. Neither one gives you a full picture of a multi-app portfolio on its own, and neither is trying to. If you run more than two or three mobile apps, you'll likely end up needing both, plus something to put their numbers next to each other.

What Appfigures actually shows you

Appfigures is built around app store visibility. Its core strengths:

• ASO and keyword tracking — rank history, keyword difficulty, competitor keyword overlap
• Reviews and ratings aggregated across App Store and Google Play, with sentiment tagging on paid plans
• Download and revenue estimates pulled directly from App Store Connect and Play Console reporting APIs
• Portfolio-level rollups across apps you own, which is genuinely useful once you're past 3-4 titles

Where it's thin: it doesn't know anything about your subscription mechanics. If you use RevenueCat for entitlement management, Appfigures sees Apple's or Google's reported revenue, not your actual MRR, trial conversion rate, or churn by cohort. Store revenue and subscription revenue are related but not the same number, for the same reason Stripe and RevenueCat MRR often disagree — reporting lag, refunds, proration, and currency conversion all create gaps between what the store reports and what actually renewed.

What RevenueCat's dashboard actually shows you

RevenueCat's charts are built around subscription lifecycle, not store visibility:

• MRR, trials, and churn broken down by product, offering, and cohort
• Conversion funnels from trial start to paid conversion
• Revenue by app if you have multiple RevenueCat projects, though comparing them side by side inside RevenueCat's own UI is limited — it's designed to go deep on one app's subscriber lifecycle, not to rank ten apps against each other
• Real subscriber events, which is the ground truth Appfigures' store-reported numbers approximate

What it doesn't do: rankings, reviews, keyword tracking, or anything about how people found your app in the first place. It also only knows about revenue that flows through its SDK — if part of your monetization is ads, web checkout, or a non-RevenueCat IAP flow, that revenue is invisible to it.

The actual overlap (and the gap)

Neither tool was built to answer "which of my 8 apps is actually worth my time this quarter" using one consistent unit of comparison. Appfigures ranks by store visibility metrics; RevenueCat ranks by subscription health metrics within one project at a time. If your apps use a mix of subscriptions, one-time IAP, ads, and a web version with Stripe, you're stitching numbers by hand regardless of which of the two you pick.

Where this actually bites multi-app founders

The problem shows up in two ways. First, comparing apps against each other: if App A is up 12% month over month in RevenueCat MRR and App B is up in Appfigures' download estimate, those aren't comparable numbers — you can't rank your portfolio on a mix of downloads and MRR. Second, reconciling reality: store dashboards, RevenueCat, and your bank account can all disagree in a given month, and figuring out why eats time you'd rather spend building. This is worth reading on: why daily numbers differ across analytics tools covers the mechanics of why Stripe, RevenueCat, and store reporting rarely match exactly, and it's not usually a bug.

Where a connector-based dashboard fits

Disclosure: SoleOS is a portfolio dashboard, and this post is written by the team that builds it — so weigh that accordingly. SoleOS connects to RevenueCat, Stripe, App Store Connect, and Google Play (among other connectors) and puts MRR, downloads, and growth rate for every app on one shared timeline, normalized so a $500 MRR jump in one app and a 200-download spike in another are shown in comparable units, not just raw numbers side by side. It also runs revenue projections using at least 21 days of history, which is something neither Appfigures nor RevenueCat's own dashboard does across a whole portfolio.

That said — if you have one or two apps and you're mostly optimizing ASO, Appfigures alone is probably enough; you don't need a portfolio layer for two apps. And if your entire monetization is inside RevenueCat with no web/Stripe component and you only care about subscriber lifecycle, its native dashboard already answers most of your questions without adding another tool. The case for something like SoleOS gets stronger specifically when you're mixing revenue sources (store + Stripe), mixing monetization models (subscription + ads + one-time), or trying to rank more than a handful of apps against each other on a consistent basis. You can see what that looks like with the live demo before deciding if it's worth adding to your stack.

Frequently asked questions

Can I use Appfigures and RevenueCat together without a third tool?

Yes, and many mobile-only founders do exactly this — Appfigures for store visibility and ASO decisions, RevenueCat for subscription health. The manual work is reconciling the two when you want a single "how is my portfolio doing" view, since neither exports into the other in a way that produces one combined number.

Does Appfigures' revenue number match what RevenueCat reports?

Not usually, and not because either is wrong. Appfigures reports store-side revenue (what Apple/Google report before RevenueCat's SDK-level tracking), while RevenueCat reports subscriber-level events with its own timing, proration handling, and currency logic. Treat Appfigures revenue as a directional store estimate and RevenueCat as closer to ground truth for subscriptions specifically.

Is RevenueCat's dashboard enough if I only have one app?

Probably, if that app's monetization is entirely subscriptions through RevenueCat's SDK. You lose visibility into ASO and reviews, which is where Appfigures (or the free tools in App Store Connect / Play Console) still earns a spot even for a single-app founder.

What if some of my apps use ads instead of subscriptions?

Neither Appfigures nor RevenueCat's dashboard covers ad revenue well — you'd need your ad network's own reporting (AdMob, etc.) as a third input. This is one of the more common gaps multi-app founders hit, since a portfolio of 5-10 apps rarely monetizes the same way across all of them.

How much history do I need before comparing apps meaningfully?

At minimum a few weeks of consistent data per app before month-over-month comparisons mean much — daily numbers alone are too noisy, especially for smaller apps. If you're trying to project growth rather than just look backward, more history helps the confidence interval narrow considerably.