Product Development
How to Monetise an App: Six Models and What the App Stores Take
Pick the model first. There is no single best way to monetise an app. The right model depends on what your app does and how often people use it. Subscriptions suit apps people open every week, in-app purchases suit one-off upgrades, and a fee on each transaction suits a marketplace. The app stores then take a share of whatever is sold inside the app, so the model you pick also decides how much of each pound you keep.
This guide covers the six models, with a clear view of when each one fits. It then sets out what Apple and Google charge in November 2026, what the UK competition regulator has changed so far, and how to choose before you build. If you are weighing an app build too, start with what an app costs in the UK, then come back here.
Key takeaways
- Six models cover most apps: subscriptions, in-app purchases, paid downloads, ads and sponsorship, transaction fees, and premium accounts.
- Apple requires its own billing for digital goods in UK apps. Google lets UK developers offer another billing option alongside Google Play Billing, but its service fee still applies.
- Physical goods and real-world services are paid for outside the stores, with card payments.
- The UK regulator has designated both companies but, as far as we found, had not yet imposed a rule on linking to outside payments.
- Choose the model before you design the screens, because it shapes what the first version needs to do.
How do apps make money?
Apps make money in six ways, and most successful ones lean on one or two. The table shows how each earns and what kind of app it suits.
| Model | How you earn | Suits |
|---|---|---|
| Subscription | Recurring fee | Weekly-use tools |
| In-app purchase | One-off extras | Games, content |
| Paid download | Price at install | Single-purpose tools |
| Ads, sponsors | Advertisers pay | Large free audience |
| Transaction fee | Cut of each sale | Marketplaces |
| Premium account | Paid tier | Free app, power users |
Three of these (subscriptions, in-app purchases and paid downloads) usually run through Apple’s and Google’s billing, and pay the store a share. Advertising and transaction fees mostly sit outside it. The sections below take each in turn.
Subscriptions and premium accounts
A subscription charges users a regular fee for ongoing access. It works when the app keeps delivering value: new content, a service that runs in the background, or a tool people rely on weekly. Apple describes auto-renewable subscriptions as access to services or periodically updated content, with users charged on a recurring basis until they cancel (Apple Developer).
Premium accounts are a close relative. The app is free to use, and a paid tier adds more: higher limits, extra features, or team access. On a phone, that paid tier is normally sold as a subscription or an in-app purchase. If you sell the app only directly to organisations for their employees or students, Apple lets those users access previously purchased content or subscriptions. Sales to consumers must still use in-app purchase (App Review Guidelines, 3.1.3(c)).
The trade-off is churn. People subscribe when the value is obvious and cancel when it is not, so a subscription needs a reason to be opened again next week. Two of our own builds show the model in practice. Udokk is a platform where healthcare professionals publish video and earn from it, and we later built its subscription monetisation. Cherry is a dating app for iOS and Android with premium subscriptions and a coaching section, which we built and continue to run and grow.
In-app purchases and paid downloads
An in-app purchase sells something once: a game level, an extra pack, the full version. A paid download charges at install. Both suit apps with a clear, finite value, and neither needs a reason for users to come back every month.
Apple’s wording is direct. To sell features or functionality within your app, such as subscriptions, in-game currencies, game levels or premium content, you must use in-app purchase. Apps may not use their own mechanisms, such as licence keys or QR codes (App Review Guidelines, 3.1.1). Google’s policy is similar: apps that charge for downloads or in-app features must use Google Play’s billing system, unless an exception applies (Play Console Help).
A paid download is the hardest to sell. Apple notes that the cost to download might make users weigh the app’s value more carefully, and that successful paid apps are often positioned as premium experiences (Apple Developer). For most first versions, a free download with a paid upgrade gives people a chance to try before they commit.
Ads and sponsorship
Advertising makes sense when you expect a large audience that will not pay. You show ads from an ad network or sell sponsorship directly, and the advertiser pays instead of the user. It tends to suit utilities, games and content apps, and it fits poorly with a small, specialist audience.
We are not giving you a revenue figure here. What an ad earns varies widely by country, audience, ad format and season, and any single number would mislead. Model it with a small live test before you plan around it.
Two practical points. Apple expects ads to be appropriate and relevant, and warns that low-quality or obtrusive ads reduce engagement and retention. Any third-party ad software must also follow Apple’s rules on data use and sharing (Apple Developer). And ads cost you something the other models do not: screen space and attention. For a product people pay to use, they usually undercut the experience you are trying to sell.
Transaction fees: when you can skip the stores
If your app connects buyers and sellers, or takes payment for something that happens in the real world, you can take a fee on each transaction. A marketplace keeps a percentage of each sale. A booking app takes a small fee per booking. Because money moves between users, the app is not selling its own digital features.
Apple’s guidelines draw the line in two places. Apps that let people buy physical goods or services consumed outside the app must use payment methods other than in-app purchase, such as Apple Pay or card entry. Apps that enable real-time one-to-one services between two people, such as tutoring, medical consultations or fitness training, may also use other methods (App Review Guidelines, 3.1.3(d) and 3.1.3(e)). Google’s policy goes further: its billing system must not be used when payment is primarily for physical goods or physical services (Play Console Help).
In practice that means a card processor, and the choice between card payments and direct debit matters for margin. Our comparison of Stripe and GoCardless covers it, and our payment integration work covers the build. Marketplaces also have to plan how to pay sellers out, which is a bigger job than taking a card.
What Apple and Google take
Store fees apply to digital sales in the app. On Google Play the service fee applies whether the sale uses Google Play Billing, alternative billing or an external web link. The rates below are as published at the time of writing (November 2026) and they change, so check the linked pages before you finalise a financial model.
Apple
Apple’s App Store Small Business Program gives a reduced commission rate of 15% on paid apps and in-app purchases. Developers qualify if they made up to 1 million USD in proceeds in the prior calendar year across all their apps, and new developers qualify too. If a participating developer passes the 1 million USD threshold in the current calendar year, the standard commission rate applies to future sales (Apple Developer). Outside the programme, Apple’s standard commission is 30% (Apple Developer Program License Agreement, Schedule 2, section 3.4).
Subscriptions have their own rule. In a subscriber’s first year of service you receive 70% of the subscription price at each billing cycle, minus applicable taxes, and after one year of paid service that rises to 85%. If you are enrolled in the Small Business Program, you receive 85% at each billing cycle regardless of how long the subscriber has stayed (Apple Developer).
Google Play
On 30 June 2026 Google changed its fees in the UK, the EEA and the US. Fees now depend on whether the user’s install is “new” or “existing” relative to that date, and Google Play Billing adds a separate 5% billing fee (Play Console Help). The standard rows for the UK, as we read them, are:
| Transaction | New installs | Existing installs |
|---|---|---|
| Subscriptions | 10% + 5% | 10% + 5% |
| One-off in-app | 20% + 5% | 25% + 5% |
Lower rates apply in two cases. On a developer’s first 1 million USD of annual earnings, the service fee is 10% on both kinds of purchase, plus the billing fee where it applies. Google’s Apps Experience and Games Level Up programmes opened in the UK on 30 September 2026. Members pay 15% on one-off purchases from new installs and 20% from existing installs, with subscriptions still at 10%, each plus the billing fee where it applies (Play Console Help). The 5% billing fee applies when a user buys an in-app digital service or feature through Google Play Billing (Play Console Help).
Put side by side, a subscription keeps more of each payment than a one-off purchase on Google Play, and Apple’s subscription rate also improves after the first year. That is one more reason the stores’ own pricing nudges apps towards subscriptions.
What the UK regulator has changed
In October 2025 the Competition and Markets Authority (CMA) confirmed that legal tests had been met to designate both Apple and Google with strategic market status in mobile platforms. The CMA said this was not a finding of wrongdoing and did not introduce any immediate requirements. It lets the CMA consider proportionate, targeted interventions (GOV.UK).
On 1 April 2026 the CMA published final commitments from each company on app review, app ranking and use of data, and from Apple on requests for interoperable access (Apple case page, Google case page). More relevant to your revenue, on 30 June 2026 the CMA consulted on a steering requirement. Its draft would remove restrictions that currently prevent UK app developers from steering customers to pay outside the stores. The CMA said it would decide whether to impose new requirements later this year (GOV.UK).
On iPhone, web-to-app billing in the UK is still something to watch while you plan around store billing. Apple’s guidelines still bar buttons and external links to other ways to pay, except in the United States storefront and regions covered by its link entitlements (App Review Guidelines, 3.1.1(a)). We found no published final steering rule when we checked. Google already allows more. Since 30 June 2026 its billing choice programme has let developers serving UK users offer alternative billing or an external web link alongside Google Play Billing. The service fee still applies, but the 5% billing fee does not (Play Console Help, Android Developers Blog). Design your pricing so that it works if store billing stays, and improves if the rules loosen. This is not legal advice.
Choosing a model before you build
Start from what the app does, then work out who pays and how often. Recurring value points to a subscription. A finite product points to a one-off purchase. People paying each other points to a transaction fee. A large free audience points to ads. If two apply, a free tier with a paid upgrade is the usual hybrid.
Then decide what the first version must prove. A monetisation model is a hypothesis about what people will pay for, and it is cheaper to test it on a small build than a full one. Our guide to how to build an MVP covers how to scope that test, and our MVP development work starts with a usable prototype from £1,500.
The practical next step is to write your model on one page: who pays, for what, how often and through which route. If it is a digital good sold on a phone, assume the store’s share in your numbers. If you would like a second pair of eyes, our app development team can help you choose a model and plan the payments before any code is written. App builds start from £5,000, with scope and price fixed and agreed before work starts.
Frequently asked questions
How do apps make money?
Apps earn through six main routes: subscriptions, in-app purchases, paid downloads, advertising and sponsorship, transaction fees, and premium accounts that add extra features. Which one fits depends on what the app does. A tool people use every week suits a subscription, a marketplace suits a fee on each sale, and a free utility with a big audience may suit advertising. Many apps combine two.
What is the best way to monetise an app?
There is no single best model, and the right one follows from what your app does and how often people use it. Recurring value suits subscriptions. One-off value suits a paid download or an in-app purchase. If money changes hands between users, take a fee on each transaction. Decide this before you design the screens, because it shapes the whole product.
How much do Apple and Google take from app sales?
Apple's standard commission is 30%, and its Small Business Program cuts that to 15% for developers with up to 1 million USD in proceeds in the prior calendar year. Auto-renewable subscriptions pay out 70% in the first year and 85% after. Google Play's UK fees, from 30 June 2026, are 10% plus a 5% billing fee on subscriptions, with higher standard rates on one-off digital purchases.
Can I avoid app store fees?
Only in part. Apple requires in-app purchase for digital goods such as subscriptions and paid features. Since 30 June 2026 Google has let UK developers offer their own billing or a link to their website alongside Google Play Billing, which drops the 5% billing fee but not the service fee. Physical goods and real-world services, such as a delivery, are paid for with card payments instead. The UK regulator had not yet decided on its proposed steering rule when we checked.
Should I charge for my app or make it free?
Free with a paid upgrade lets people try the app before they commit, which a paid download does not. A paid download suits a single-purpose tool people already know they want. Whichever you pick, test it on a small group first. Our MVP guide covers how to scope a first version that tests what people will pay for.
Working out how your app will earn?
Book a free 30-minute consultation and we'll help you choose a model and plan the payments before you build.