How to Price a Mobile App: Paid, Freemium, Subscription, In-App Purchases or Ads
Many app teams decide on pricing late, after the product is built. That is backwards. The way you charge decides what you build, whom you attract, how you market and how long you wait for cash. A meditation app sold by subscription and a game funded by ads are different businesses, even if the code looks similar.
Here are the five main models, what each one needs to work and where each one fails.
| Model | How it works | Best for | Main risk |
|---|---|---|---|
| Paid | User pays once before download | Niche tools with clear, specific value | Users cannot judge the value before paying |
| Freemium | Free core, paid advanced features or higher limits | Apps where heavy users clearly need more | Free tier too good or too limited |
| Subscription | Recurring weekly, monthly or yearly payment | Apps that deliver new value every period | Cancellations once the value is used up |
| In-app purchases | Free app, paid items or one-off unlocks inside | Games and apps with repeated small needs | Pushy prompts damage trust and reviews |
| Advertising | Free app, revenue from ads shown to users | Large audiences with frequent sessions | Small audience, poor experience, privacy limits |
1. Paid: pay once to download
The user pays before installing. The model is simple to explain and puts no pressure on you to sell anything inside the app.
It works when the app solves a clear, specific problem for a professional or enthusiast audience that already knows what it wants: a specialised calculator, a tool for a niche hobby, a utility with no free equivalent.
It fails when users cannot judge the value before paying. In crowded categories with free alternatives, a price tag stops most people at the store page. You also get paid only once, while servers, updates and support cost money every month.
2. Freemium
The core app is free; advanced features, more storage or the removal of limits are paid. The free version is your marketing.
It works when the free tier is genuinely useful and the paid tier is clearly better for people who use the app seriously. The upgrade should be triggered by usage: the user hits a limit at the exact moment they need more.
It fails when the free version is so good that nobody upgrades, or so limited that nobody stays. Drawing that line is the hard part. Plan to test it several times; the first line you draw is rarely the right one.
3. Subscription
Users pay weekly, monthly or yearly for continued access. Revenue is recurring and easier to forecast, which is why investors and finance teams like this model.
It works when the app delivers new value regularly: fresh content, an ongoing service, data that keeps updating, cloud sync across devices. Users should feel they get something new in every period they pay for.
It fails when the value is delivered once. If someone gets everything they need in the first week, they will cancel. A subscription also shifts your focus from acquisition to retention: onboarding, reminders, new features and win-back offers matter as much as the download. Offer a free trial only if your onboarding shows the value within the trial period.
4. In-app purchases
The app is free and users buy things inside it: consumables such as credits, coins or extra lives, or one-off unlocks such as a filter pack or a set of premium templates.
It works when users have repeated, small moments of need. Games are the classic case, but photo editors, dating apps and design tools use it too.
It fails when purchases feel like a trap. Aggressive prompts and confusing virtual currencies damage reviews and trust, and some practices, such as paid loot boxes and purchases by children, are restricted in a number of countries. Be transparent about what the user gets for the money.
5. Advertising
The app is free and you earn from ads shown to users: banners, full-screen ads between actions, rewarded video (the user watches an ad to get a bonus) and native ads.
It works when you have a large audience with frequent sessions and a low willingness to pay: casual games, simple utilities, content apps.
It fails when the audience is small or the ads ruin the experience. Ads also make you dependent on the ad market and on privacy rules. Apple's App Tracking Transparency framework, for example, requires apps to ask permission before tracking users across other companies' apps and websites, which has made targeting and measurement harder. Ad revenue per user also varies widely by country, so in smaller markets ads alone rarely cover the costs.
Hybrid models are the norm
Few successful apps rely on one model only. Common combinations: free with ads plus a paid subscription that removes them; freemium plus one-off purchases; a subscription with a lifetime option for loyal users. Start with one primary model and add a second once you understand how your users behave.
Do not forget the platform's cut
Apple's App Store and Google Play take a commission on paid downloads, in-app purchases and subscriptions sold through their billing systems. The rate depends on the product type, your revenue level, the country and the current platform rules, which have been changing because of regulation in several markets. Check the current terms of each store before you build your financial model, not after.
How to choose: five questions
- How often does the user get new value? Daily or weekly value supports a subscription; one-time value supports a single price or a one-off unlock.
- Can the user see the value before paying? If not, give them a free tier or a trial.
- How big is the realistic audience? Small, high-value audiences pay; large, casual audiences are better monetised with ads or small purchases.
- What does the user compare you to? Sometimes it is not another app but a paper notebook, a spreadsheet or a phone call to a specialist.
- Where is the audience? Willingness to pay and preferred payment methods differ by country. Both stores let you set prices per country; use that, and test real prices in each market instead of converting one price into local currency.
Test, do not guess
Pricing is a hypothesis. Launch with a model you can explain in one sentence. Measure conversion from free to paid, retention after the first month and revenue per user. Then change one thing at a time: the price, the limit of the free tier, the length of the trial. Store tools and third-party subscription platforms let you run these tests without rebuilding the app.
In my experience, the teams that struggle most are not the ones that chose the "wrong" model, but the ones that never measured whether their model was working.
The takeaway
Choose the model that matches how often your users get value, not the one that looks best in a pitch deck. Write it down before development starts, because the paywall, the onboarding and the analytics all have to be built around it.
