Product
Six questions. A clearer view of your app.
Appfox is an app intelligence platform for research and day-to-day decisions. The beta navigation brings together Dashboard, Customers, Market, Keywords, and Settings. The six areas below explain the questions it helps you answer, including what is still planned.
01 · TodayToday:What needs my attention?
A ranked list of significant findings with evidence, freshness, coverage, and a next action. Sections for critical, important, opportunities, recent changes, and resolved outcomes. Zero findings is a valid state, and it is distinguished from not enough data and from a failed sync.
02 · MarketMarket:Who is out there, and what is changing?
Choose the market you want to understand, review direct and adjacent competitors, and open a research brief. Compare collected listings, prices, ratings, and reviews. Saved observations let you see changes over time; coverage depends on the store, market, and collection history.
03 · CustomersCustomers:What are people telling us?
Open Customers to see recurring praise, friction, and requests in collected reviews. Follow a theme into the review browser and filter by market, sentiment, rating, or reason. Check the sampled and classified review counts before treating a theme as representative of all your users.
04 · My AppMy App:How is my app doing, across sources?
Your app in one place: public store identity, listing history, customer evidence, and release context. RevenueCat metrics are planned and unavailable in the current beta. The aim is to connect the evidence around your app, with the source and scope clear.
05 · ActionsActions:What did we decide, and did it help?
Keep a decision close to the research that led to it. Research briefs let you record a decision and follow up on suggested actions. Write down what you will test and how you will judge the result. A change in reviews or rank is evidence to investigate, not proof that your release caused it.
06 · IntegrationsIntegrations:What does Appfox read, and can it write?
The beta uses public store data. Private connections, including RevenueCat, are planned. Connection cards are designed to show what is read, permissions, sync status, usage limits, and a disconnect control. Private integrations are intended to be read-only.
Not every changedeserves a notification.
Each signal has a detection threshold, a minimum sample size, a cooldown, and a separate notification threshold. Alerts are driven by significance, not by events.
Where it goes
History only
Low
A small, expected movement worth keeping for later comparison.
Where it goes
Activity feed
Interesting
A real change that does not need a decision today.
Where it goes
Today and digest
Important
A change with enough evidence to deserve a look this week.
Where it goes
Push or email candidate
Critical
A change that is likely costing you customers or money right now.
Concise by default.Deep when you ask.
Every finding opens the same way. You read the action first and drill into the evidence only as far as you need.
- 01
Recommendation
One sentence you could act on today.
- 02
Why it matters
The metric, review, release, or competitor movement behind it.
- 03
Evidence summary
Counts, windows, denominators, and confidence.
- 04
Raw evidence
The original reviews, listings, and metric observations.
- 05
Historical data
The same facts over time, so you can judge the trend yourself.
Private beta
Build your next release with a clearer picture.
Research your idea, understand your reviews, and follow your competitors. Request an invitation to the Appfox private beta.
Invitations are sent by email.