What it means
An operating system is the base software that controls a device and allows apps to run on it. Android is an open source version of that base software, so handset manufacturers can take it, adapt it and ship it on hardware they design themselves.
The result is a very wide spread of devices, from budget handsets to premium phones, all running broadly the same app platform. For finance teams the platform matters because money arrives through it.
App store billing takes a commission before the cash reaches your bank account, so the revenue your product team celebrates is not the revenue that lands in your accounts. Any forecast that ignores the commission, the payment timing and the refund rate will overstate cash.
In practice companies split their user numbers, revenue and marketing spend by platform, because Android and its main rival behave differently on price, refunds and churn. Build costs are usually treated as either an expense or a capitalised intangible asset that is then amortised over the useful life of the app.
The choice affects reported profit in the year of the build, so it is worth agreeing with your auditor before the invoices arrive. There are two nuances worth knowing.
Android users are spread across many countries and price points, so average revenue per user is often lower than on other platforms while total volume is higher, which changes how you judge a campaign. The spread of device models also raises testing and support cost, and commission rates differ by store, by developer size and over time, so they should be checked rather than assumed.
In practice
Real-world examples.
Example
A consumer lender in a market where most customers use mid-range Android handsets builds its loan application journey for Android first. Finance models the cost of supporting 40 device models and agrees a $180,000 annual testing budget. The decision is justified because 80% of new borrowers arrive through that platform.
Example
A streaming business reports $900,000 of gross app store revenue in a quarter and books net revenue after commission. The finance lead reconciles the store payout statement to the revenue ledger each month so the commission is visible as a cost of sale rather than hidden in a net figure.
Example
A grocery retailer capitalises $400,000 of development cost for its loyalty app and amortises it over four years at $100,000 a year. When the team proposes a rebuild after two years, the remaining $200,000 of unamortised cost has to be written off, which the board must approve.
Formula
Calculation
Net platform revenue = Android users x average revenue per user x (1 - store commission rate). Suppose a subscription app has 50,000 monthly active users and 60% of them are on Android, giving 30,000 Android users. Average revenue per user is $2.50 a month, so gross monthly Android revenue is 30,000 x $2.50 = $75,000. Applying an illustrative store commission of 15%, the commission is $11,250 and net revenue is $75,000 - $11,250 = $63,750 a month, or $765,000 a year. Commission rates vary by store and by scheme, so the percentage must be taken from the current agreement rather than memory.Case study
Seen in the real world.
Kesterling Mobility is an illustrative, fictional payments business selling a tap to pay app to small traders. Its early forecast assumed $1,200,000 of annual subscription income, taken straight from the product team's pricing model.
When the first full quarter closed, the finance lead found that store commission, failed payments and refunds together removed about 19% of the gross figure, leaving materially less cash than budgeted. The team rebuilt the model to show gross billings, commission, refunds and net cash as separate lines, and set a monthly reconciliation against the store payout report.
The result in this illustrative case was not more revenue but fewer surprises. Marketing spend was then judged against net revenue per user, which stopped the business paying to acquire customers it could not serve profitably.
Watch out
Common mistakes.
- Treating gross app store billings as revenue and forgetting the commission, which flatters both margin and cash forecasts.
- Assuming Android and other mobile platforms behave the same on pricing, refunds and churn, then setting one blended target for both.
- Capitalising every hour of development cost without testing whether the app will really generate income over the amortisation period.
Questions
People also ask.
Does the platform choice change how we recognise revenue?
No, the accounting principle is the same, but the store acts as an agent or principal depending on the contract, so check whether you report gross with a commission cost or net.
Why is average revenue per user usually lower on Android?
Because the installed base covers far more price points and countries, so the mix includes many lower spending users alongside high spenders.
Should app development cost sit in operating expenses or as an asset?
It depends on whether the build creates a separately identifiable asset with a measurable future benefit; routine maintenance is an expense, a major new build may qualify as an intangible asset.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%