How to check App Store sales and revenue on iPhone
App Store Connect is excellent for managing an app. It is not always the fastest way to answer a simpler question: did anything sell, and do I need to do something about it?
If you publish an iPhone app, you probably know the routine. Open App Store Connect, find the right app, wait for the report, check the date range, then repeat it for the other apps in your portfolio. When you are at a desk, that is manageable. When you are away from your Mac, it is surprisingly easy to postpone the check altogether.
The answer is not to turn every phone check into a finance department. It is to separate two jobs: App Store Connect remains the source of record, while a small mobile view answers the quick operational questions.
What App Store Connect tells you
App Store Connect brings a lot together: app versions, TestFlight, reviews, agreements, analytics, sales, and payments. That breadth is exactly why it is useful. It is also why a quick revenue check can require more navigation than expected.
The financial area contains several related concepts. Sales describe transactions. Proceeds describe what the developer is attributed under Apple’s rules. Payments describe money paid according to Apple’s fiscal schedule. These values should not be casually treated as the same thing.
A useful mobile summary keeps the labels visible and leaves the detailed report one tap away. The goal is clarity, not a second accounting system.
The four questions worth answering on a phone
Show new sales, proceeds, refunds, or subscription events since the last check.
A portfolio view should identify the app or product, not just display one unexplained total.
Today’s number needs context: the last seven days and month-to-date are usually enough.
Surface unusual changes, reviews, or a new event so the next action is obvious.
Why a live number can be misleading
App Store revenue is affected by reporting windows, fiscal periods, currencies, refunds, and delayed updates. A quiet screen does not automatically mean a quiet business. It may mean the report has not caught up yet.
This is why a responsible app should show when it last synced, what the amount represents, and which source it came from. If a figure is an estimate, call it an estimate. If it is proceeds rather than gross sales, say so beside the number.
The interface should reduce uncertainty, not hide it behind a large green total.
A simple daily routine for indie developers
- Check the pulse once. Look at today, seven days, and month-to-date.
- Open the event only when something changed. Identify the app, type of event, currency, and timestamp.
- Write one line of context. Note whether a launch post, review, update, or search result might explain the movement.
- Choose one action. Reply to a customer, improve the store listing, ship a fix, or leave the number alone.
- Reconcile in App Store Connect. Do the detailed financial check on a regular schedule rather than refreshing all day.
This routine is intentionally boring. The purpose of a mobile view is to help you return to the work that creates the next sale.
What to look for in an App Store revenue app
- Clear definitions: sales, proceeds, payments, and refunds are not blended together.
- Portfolio support: you can see which app moved without changing accounts repeatedly.
- Freshness: the last sync time is visible.
- Read-only behaviour: checking revenue should not grant permission to change products or releases.
- Useful alerts: notifications point to an event worth opening, rather than creating noise.
- A path back to the source: detailed reports remain available when you need to reconcile.
A small mobile-first experiment
We built Dispatch Kun around this narrower job: see App Store Connect sales, revenue, subscriptions, submissions, reviews, and alerts from an iPhone. It is meant for the in-between moments when opening the full administration console is too much friction.
It does not replace App Store Connect and it does not pretend that a phone view is an accounting ledger. It simply keeps the useful pulse close, so a developer can notice what changed and decide whether a response is needed.