# Cherry Analytics: Solana dApp Store review analysis

> Cherry Analytics reads Solana dApp Store reviews: sentiment, feature requests, wallet-enriched segments, custom dashboards, and the step back to users.


Cherry Analytics is Cherry's review intelligence product for Solana app teams: AI analysis of Solana dApp Store reviews that returns sentiment, extracted feature requests, wallet-enriched user segments and a dashboard built around the questions one team asks about its own app. Cherry is a wallet-to-wallet messenger and community app for crypto, with a web app at chat.cherry.fun, iOS and Android apps, and a listing on the Solana dApp Store for the Seeker phone. The analysis exists because the messaging does: the wallets that write store reviews are addressable in chat, so a finding can end in a conversation. This page covers what the review set holds, what the dashboard reports, what it cannot tell you, and how a team gets one.

## What Cherry Analytics does

It reads the public review stream of the Solana dApp Store and returns the parts a builder can act on this week.

- Scale: 361K+ reviews across 610 Solana apps as of September 2026. The set grows by roughly 10,000 reviews a week, so treat any printed count as a floor.
- Six panels: "AI Sentiment Analysis", "Wallet Data Enrichment", "ICP Identification", "Feature Requests", "Trend Detection" and "Customer Segments".
- A dashboard per product, built around the growth questions one team brings.
- A public leaderboard of top-rated Solana apps, ranked on reviews and sentiment, which any team can read before it asks for anything.
- Price: free, and the promise is narrow: "turn reviews into product intelligence".

Sentiment scoring and feature extraction are common in app review analysis. Attaching on-chain wallet data to the people who wrote the reviews is possible here because the reviews sit on a wallet-native app store.

## How it works

The pipeline runs in four moves, and the dashboard is the fourth.

| Step | What happens | The question it answers |
|---|---|---|
| Collect | Reviews for tracked Solana dApp Store apps are pulled into one set, yours and the rest of the store | What is the store saying, this month and last |
| Classify | Every review is labelled positive, negative or neutral, with the reasoning kept beside the label | How big is the problem, counted across the reviews |
| Extract | Feature requests are pulled out of free text and grouped by what they ask for | Which missing feature is asked for most often |
| Enrich | On-chain wallet data is attached to the feedback and grouped into segments and an ideal customer profile | Which kind of user is saying it, and what that segment is worth |

Two details matter more than the diagram. First, classification keeps its reasoning, so a bar in a chart opens into the reviews under it and a product decision can be checked against sentences real users wrote. Second, enrichment groups by wallet behaviour, including whale activity, so the same complaint counted twice gets weighted once by volume and once by the value of the wallets behind it. A team that ships for traders usually finds those two orderings disagree.

Trend detection watches sentiment shift over time. The useful read is a named pain point: after you ship, sentiment on it either moves or it does not, and the review text says which.

## From a review to a conversation

Cherry's framing for this is to close the loop: understand what users want, identify who they are, then reach them through wallet-native messaging.

The last step is the one a store console cannot do. A review on the Solana dApp Store comes from a wallet, and on Cherry a wallet is an address you can talk to. Three routes exist, in rising order of effort:

1. Claim a public room for your app and answer in it. Builders who ship a [mini app inside Cherry chats](https://cherry.fun/learn/features/mini-apps/) get a room with the app, and users who follow it can be reached with push notifications later.
2. Run a campaign. [Airdrop campaigns](https://cherry.fun/learn/features/airdrops-and-quests/) check an on-chain condition you define, so a reward can be aimed at holders, at a collection, or at wallets that pass your own check.
3. [Message a wallet directly](https://cherry.fun/learn/features/dm-a-wallet-address/). This is the narrow route and it has rules: a first message from a stranger lands in the recipient's Requests folder with no notification, and declining is silent. Paying the delivery fee, 0.01 SOL by default as of September 2026, gets the message delivered with a notification. [Message requests and paid DMs](https://cherry.fun/learn/features/message-requests-and-paid-dm/) covers both paths.

The Solana dApp Store ships on the Seeker phone, and that audience is already on Cherry: the [Seeker Club](https://cherry.fun/learn/guides/seeker-club/), gated on holding a `.skr` domain, held more than 8,600 members in September 2026.

[Seeker Club on Cherry](https://chat.cherry.fun/@seekerclub)

## What a store review console does not show

A publisher console shows your listing: your stars, your reviews, a reply box. Cherry Analytics differs on four mechanisms, none of which is a matter of presentation.

- Scope. The set covers 610 Solana apps as of September 2026, so a complaint about your onboarding can be read against how the rest of the store handles the same step.
- Structure. Store reviews arrive as a star and a sentence. Classification and extraction convert a year of sentences into counts of named issues, which is the form a roadmap argument needs.
- Wallet context. A store console shows you the review, not the wallet behind it. Attaching balances and activity to the account that wrote it is what turns a review into a segment, and it only works on a store whose users sign in with wallets.
- The reply. A console reply is public text under a review. On Cherry the wallet is reachable in a room, a campaign, or a direct message, which turns the finding into a conversation.

## Who uses it and for what

Three shapes of team use the same dashboard differently.

A product team arriving at roadmap planning uses the feature request counts. The argument in the room stops being "three people asked for portfolio tracking" and becomes a number of requests with the review text attached, ordered against every other request.

A growth team uses the segments before it spends anything. Knowing which wallet tier rates the app highest tells a campaign who to target, and the same answer feeds the eligibility check on a campaign or the audience for a Seeker-first launch.

A founder before a launch uses the rest of the store. The complaints under competing apps in the same category are public, dated, and written by the users being fought over, which is cheaper research than a survey nobody answers. The full distribution plan lives in [how to get users for a Solana dApp](https://cherry.fun/learn/guides/distribute-a-solana-dapp/).

## Limits and honest caveats

- No store listing, no data. The analysis reads Solana dApp Store reviews, so a web-only dApp has nothing in the set. Those teams get more from [embedded chat](https://cherry.fun/learn/features/embeddable-chat/) inside the product, where the same complaints arrive in writing.
- Reviewers are a slice. People who rate an app on a phone store skew toward mobile Seeker owners and toward the two moments that produce reviews, delight and anger. The quiet majority is missing from every review set.
- Labels are model output. Sentiment and feature extraction come from AI classification, which is why each label keeps its reasoning; read the reviews under a number before shipping against it.
- Wallet enrichment reports balances, activity and segments. It is not identity, and Cherry does not hand over contact details.
- Setup goes through the team. Dashboards are built with Cherry rather than configured in a self-serve screen, unlike the embeds, keys and bots in [Cherry Portal](https://cherry.fun/learn/guides/cherry-portal-for-developers/).
- Analysis is not support. Nothing here replies to a review or files a ticket; the reply is the messaging step above, and it is a decision a human makes.

## How to start

1. Confirm your app is published on the Solana dApp Store. Publishing runs through Solana Mobile's dApp store publishing tools, and only listed apps collect the reviews this reads.
2. Open [cherry.fun/dapps-analytics](https://cherry.fun/dapps-analytics) and find your app in the leaderboard. The public view is enough to see the rating, the review count and where the app sits among Solana apps.
3. Write down the two or three questions you want answered. Which pain point costs the most users, which requested feature comes from the highest-value wallets, and what changed since the last release are the ones teams ask most.
4. Message the Cherry team with the app name and those questions. The page's own instruction is short: "Message us to get started with your custom analytics dashboard".
5. Decide the connect step before the first findings land: a room for the app, a campaign, or direct messages. Each one is a different amount of work and they compound.

Message the Cherry team at [t.me/cherrydotfun](https://t.me/cherrydotfun) with your app name to get a dashboard, and create the project you will need for rooms, bots and embeds at [portal.cherry.fun](https://portal.cherry.fun).

## FAQ

### What is Cherry Analytics?

Cherry Analytics is Cherry's review intelligence product for Solana app teams. It runs AI analysis over Solana dApp Store reviews and returns sentiment, extracted feature requests, wallet-enriched user segments and a dashboard built around the questions one team asks about its own app.

### What does Cherry Analytics cost?

It is free. A team messages the Cherry team, says which app it publishes and what it wants to learn, and gets a dashboard back.

### Where do the reviews come from?

They are the ratings and written reviews people leave on the Solana dApp Store, the app store that ships on the Solana Seeker phone. The set held 361K+ reviews across 610 Solana apps as of September 2026 and grows by roughly 10,000 reviews a week.

### Can Cherry Analytics cover an app that is not on the Solana dApp Store?

No. The analysis reads dApp Store reviews, so an app with no store listing has nothing to read. A web-only dApp gets more from a chat room inside its product, where users say the same things in writing.

### What is wallet enrichment in app review analysis?

Wallet enrichment attaches on-chain data to the wallets behind the feedback, so reviews can be grouped by wallet tier and activity. It answers which kind of user is complaining, which is the difference between a loud minority and the segment that holds the most value.

### How do I reach the users behind a review?

Through Cherry, because a wallet is an address you can talk to: claim a public room for your app, run an airdrop campaign that checks an on-chain condition, or message a wallet directly. A first message from a stranger lands in the recipient's Requests folder with no notification unless the sender pays the delivery fee.

## Sources

- [Cherry Analytics](https://cherry.fun/dapps-analytics)
- [Solana Mobile: publishing to the Solana dApp Store](https://docs.solanamobile.com/dapp-store/intro)
- [Seeker Club on Cherry](https://chat.cherry.fun/@seekerclub)
- [Cherry Portal for developers](https://portal.cherry.fun)
- [Cherry on Telegram](https://t.me/cherrydotfun)