Founders prepare the revenue dashboard and the P&L and assume diligence will stay there. Experienced app buyers also read the store. Not your listing copy — the record behind it: how Apple and Google have treated the app, how users have rated it over time, and where its downloads actually come from inside each store. Much of that record is public or a few clicks from an export, and it tells a buyer things the financials cannot. Here is what they are looking at.
1. Rejections, warnings and policy strikes
A buyer will ask to see the app's history in App Store Connect and the Google Play Console: rejected builds, policy warnings, features you were made to remove, any notices against the developer account. One rejection that was fixed and resubmitted is normal. A pattern of rejections around the same issue — subscription disclosures, data collection, content rules — tells the buyer the business model sits close to a line the platform may redraw. That is a risk they will price, and it is far easier to explain with the history in hand than after they find it on their own.
2. The ratings trend, not the average
A 4.6 earned four years ago and a 4.6 earned last quarter are different assets. Buyers look at ratings by version and by period, because a decline after recent releases points to product or stability problems the revenue has not caught up with yet. If a bad release dragged ratings down and you fixed it, show the recovery. The story of what went wrong and how quickly you responded is worth more to a buyer than a clean-looking average.
3. Where downloads come from inside the store
Organic installs are not all the same. An app that ranks for a spread of search terms has a durable discovery engine. An app that depends on one keyword, one category ranking, or a feature placement from two years ago has a single point of failure. Buyers will want the source and search-term breakdown from the consoles, and they will ask what happened to installs the last time a ranking slipped. Knowing your own answer, with the data exported, keeps them from assuming the worst.
4. Refunds and billing complaints
Refund rates and billing-related reviews are a read on how the subscription is sold. A high refund rate, or a steady stream of "I didn't know I'd be charged" reviews, signals an aggressive paywall or trial design. That is a platform-policy risk, and a hint that some of the revenue might not survive a more conservative owner. If refunds are low and billing complaints are rare, say so with the numbers from the consoles rather than leaving the buyer to estimate.
5. What the reviews say about the business being handed over
Buyers read the reviews themselves, and they read them for operating signals: recurring bug reports, support complaints that went unanswered, feature requests the roadmap ignored, users asking for a platform you have not built. Those comments tell a buyer how much support load comes with the app and where the next dollars of growth might be. A founder who has answered reviews consistently, and can point to fixes shipped in response, is showing a business that is being run, not just kept alive.
The takeaway
Your store record is diligence material whether or not it goes in the data room — a buyer can see much of it without asking. Export it, read it the way a buyer will, and be ready to explain the rejections, the rating trend, and any dependence on a single source of installs. An app whose store history is understood and explained reads as lower risk than one whose history the buyer had to discover.
