How can my app generate revenue beyond direct sales?

Most app founders think about revenue the wrong way. They build the product, launch it, and then ask how they can make money from it, as if monetisation is something you layer on afterwards, like paint. The result is usually a product that feels like it has adverts stapled to it, or a paywall that confuses users who never saw a reason to pay. Revenue does not bolt on. It grows from inside the product, from decisions made long before the first user opens the app.

Revenue does not bolt on, it grows from decisions made inside the product, long before the first user opens the app.

The question founders should be asking is not "what revenue model should I use?" but "what does my product do for people, and which revenue model follows naturally from that?" Those are different questions, and the gap between them explains a lot of failed monetisation attempts. A fitness app that rewards daily habits earns the right to charge differently from a gaming app that rewards social competition. The model has to fit the product's core loop, or users feel the friction immediately.

This article covers the main revenue models available to app developers, explains why each one works under specific conditions, and describes the behavioural and design choices that determine whether any of them actually generate income. The goal is to give you a clear picture of where revenue comes from and what your product needs to do to earn it.

The main revenue models available to app developers

App revenue generally comes from one of five sources: subscriptions, in-app purchases, advertising, affiliate or partnership arrangements, and data licensing. Most successful apps draw from more than one. The choice between them is shaped by what the product actually does, who uses it, and how often they return.

Each model places different demands on the product. Subscriptions require consistent, demonstrable value. In-app purchases require a product loop that creates desire for more. Advertising requires volume. Affiliate revenue requires purchase moments that feel natural inside the experience. None of them work in isolation from the product's core purpose, and choosing the right one starts with understanding what your users actually come back for.

Why bolting on monetisation after launch rarely works

Adding a revenue model after launch feels practical. The thinking goes: build the audience, then monetise. The problem is that users form habits around a product as they first experience it. Introduce a paywall or ad break after they have settled into a free, uninterrupted experience, and it feels like a withdrawal of something they had already been given. That perception is very hard to recover from.

We saw this play out on the social football platform we worked on. The product launched without a sustainable revenue structure, and when the user base failed to reach the scale needed for subscriptions to be viable, the team had to introduce advertising. Features they had publicly said they would not add were suddenly on the roadmap. Users who had downloaded the app based on those earlier promises felt misled. The advertising revenue helped short-term, but the trust damage created a longer-term problem for the product's commercial health.

The deeper issue is that monetisation shapes design decisions. A product built from the start around a subscription model prioritises returning value, regular engagement, and demonstrable progress. A product retrofitted with subscriptions after launch is often missing those foundations. The revenue layer has nowhere solid to sit.

Before you finalise your product's core feature set, map out which revenue model you intend to use and check that the user journey supports it. A subscription model needs a habit loop. An affiliate model needs a natural purchase moment. Build the product to fit the model, not the other way around.

How retention determines whether any revenue model is viable

Every revenue model depends on users staying. A subscription cannot be renewed by someone who left. An in-app purchase cannot be made by a user who deleted the app after three days. Affiliate revenue requires a user who is engaged enough to follow a recommendation. Retention is the condition that makes every other factor possible.

On average, 77 per cent of apps lose their daily active users within the first three days of download, according to data Simon regularly references in product reviews. Even well-designed products typically see a 40 to 50 per cent drop in retention after the same period. That gap between 77 per cent and 40 to 50 per cent is not a rounding error. It represents the commercial difference between a product that can support a revenue model and one that cannot.

Retention is the condition that makes every other factor commercially possible.

We saw this directly on the art-based auction game we worked on. Early retention sat in the mid-sixties to low seventies percentage range, which is strong. As the quantity of available games declined, usage became sporadic rather than consistent, and retention dropped to around 30 to 35 per cent. At that point, the monetisation model was under real pressure because the users needed to sustain it were not returning reliably enough. When the team eventually addressed the core content supply problem, retention climbed back to the mid-sixties to low seventies, but the trust that had eroded during the low period took considerably longer to rebuild.

Track retention by cohort from day one, not as an aggregate. Knowing that 65 per cent of users are still active after 30 days tells you very little if 90 per cent of those users joined in the last week. Cohort data shows you whether the product is genuinely holding people, or whether new acquisitions are masking churn.

Subscriptions: when they work and when they collapse

Subscriptions are the most predictable revenue model for apps that deliver consistent, ongoing value. According to RevenueCat's 2024 State of Subscription Apps report, subscriptions generate between 40 and 44 per cent of app revenue across the products they track. That share reflects how central subscriptions have become to the app economy, but it does not mean they suit every product.

Subscriptions collapse when the product does not deliver fresh value on a schedule that matches the billing cycle. A user who pays monthly will ask, consciously or not, whether the past month justified the charge. If the answer is no, they cancel. The products that hold subscribers longest are the ones where the user has built a habit around the product itself, so the cost feels like part of a routine rather than a transaction.

Where subscriptions tend to fail

The social football platform we worked on abandoned its subscription model because it launched iOS-only, targeting a younger audience that skewed heavily towards Android. The addressable user base on day one was a fraction of what it needed to be for subscriptions to generate viable revenue. Platform decisions made before launch directly constrained the monetisation model available after it. A subscription model requires volume. Without it, the unit economics do not work, and the team had to pivot to advertising instead.

Building for subscriptions also means treating the product as a long-term investment rather than something that should repay its development costs quickly. Founders who expect to recover production expenses within a few months through subscription revenue are applying the wrong mental model. Consumer subscription revenue compounds over time through retention and word of mouth, not through pricing that reflects what it cost to build.

In-app purchases and the shift away from pay-to-win

In-app purchases once meant one thing: a wall you could not pass without paying. Games were designed so that progress stalled at a specific point, and the only way forward was a purchase. That approach has largely disappeared, replaced by models where purchases feel like genuine choices rather than forced exits. The shift happened because users became resistant to manipulation, and app stores began applying pressure on developers whose review scores reflected it.

The better version of in-app purchases rewards engagement rather than exploiting impatience. Cosmetic upgrades, additional content, or tools that expand what a user can do, rather than remove a barrier they have been artificially placed behind, feel fair. Users buy them because they want to, not because they are stuck.

Earned engagement as the new model

The fitness app for weight loss we worked on shifted its entire approach to engagement from outcome-based rewards to behavioural ones. Instead of celebrating hitting a target weight, the product rewarded showing up, being better than yesterday, and taking small steps consistently. That shift changed what users valued about the product. And when in-app purchase opportunities were placed inside a product loop built on consistent engagement, they felt like natural extensions of a journey the user was already invested in, rather than interruptions designed to extract money.

Before adding any in-app purchase, ask what the user has already done in the product to get to that point. If the answer is "not very much", the purchase moment is too early and will feel premature. The more invested a user is in the product's core loop, the more naturally a relevant purchase sits inside it.

Affiliate and partnership revenue built into the product experience

Affiliate revenue works when the product has a natural moment where a user would benefit from something external, and the partnership brings that thing to them without breaking the experience. The key word is natural. An affiliate link that appears because a developer needed revenue, rather than because the user needed something, is felt immediately and damages trust.

On a proof-of-concept project we ran for a company building an app to share memories with audio attached, we initially looked at integrating with Spotify to allow users to attach short audio clips. Spotify's API was not robust enough for clips, and requiring a Spotify account created friction that eroded the experience. We switched to Deezer, which had a stronger API, supported clips without requiring users to be logged in, and gave access to a catalogue larger than Spotify's.

The key benefit beyond the technical one was commercial: when a user wanted to hear a full track rather than a clip, there was a natural upsell to a Deezer subscription, and the app earned affiliate referral revenue from that transition. The purchase moment was a genuine extension of what the user was already trying to do.

That example illustrates the principle well. The affiliate arrangement was not a revenue strategy grafted onto a product. It emerged from solving a real user need, and the revenue followed from the solution rather than preceding it.

Advertising as a revenue stream and what it costs you

Advertising is the revenue model of last resort for most products, not because it cannot generate income, but because it almost always costs something in user experience. A banner ad in a meditation app is not a neutral addition. It sends a signal about how the product values the user's attention, and that signal compounds over time.

The products where advertising works are those where the free experience is so high in volume that the friction of ads is a reasonable trade-off, and users understand the deal. Social media feeds and content aggregators fit that pattern. Products that deliver a focused, high-attention experience do not.

When advertising becomes the only option

On the social football platform, advertising was introduced because subscriptions were no longer viable after the user base failed to reach the necessary scale. The team had not planned for it, had publicly positioned against it, and introduced it under financial pressure rather than product logic. The result was a product that felt like it had changed its values, because it had.

Users who had chosen the platform partly because it was clean and focused now encountered the kind of experience they had been avoiding elsewhere. That is a recoverable situation but a very difficult one, and the effort it takes to recover trust is almost always greater than the effort it would have taken to build the right model from the start.

How gamification drives the engagement that makes monetisation possible

Gamification is the mechanism that creates the sustained engagement that makes monetisation viable. A product that users find compelling enough to return to daily, week after week, is a product that can support a subscription, justify an in-app purchase, or place an affiliate recommendation with enough context for it to land well. A product that users open once and forget cannot support any of those things.

The gamification approaches that sustain engagement over time reward behaviour rather than achievement. Showing up, making progress relative to yesterday, completing a sequence, building a streak, these are actions that keep users inside a product's loop regardless of whether they have hit a particular outcome. The fitness app we worked on shifted from rewarding weight loss milestones to rewarding daily engagement and small improvements. That shift made the product stickier because users who were not yet hitting their goals still had a reason to return. The gamification served the retention, and the retention served the revenue.

Behavioural data from within the product can also tell you which users are close to churning, based on patterns like slowing dwell time, reduced return frequency, or consistent task abandonment. Identifying those patterns early means you can adjust the experience before a user leaves, which protects the retention that underpins every revenue model.

Why platform and audience decisions made at launch constrain your revenue options later

The platform you launch on, the audience you reach on day one, and the expectations you set in your app store listing are not just marketing decisions. They determine which revenue models you can realistically deploy, often for years.

The social football platform launched iOS-only. The target audience was younger and skewed significantly towards Android. That single decision meant day-one adoption was roughly half what it might have been with a cross-platform launch. A subscription model needs a user base large enough to generate meaningful recurring revenue. The platform decision made that base unachievable in the short term, which forced a pivot to advertising and effectively rewrote the product's commercial strategy under pressure rather than by design.

App store listings and early churn

The app store listing sets expectations before a user even downloads the product. If the listing accurately describes what the app does and who it is for, the users who download it are already self-selected as the right audience. They open the product with correct expectations, which means early abandonment driven by disappointment falls significantly. That matters commercially because reducing early churn is one of the most direct ways to improve the unit economics of any revenue model. Users who stay past the first few days are far more likely to convert to paying customers than users who arrive through a misleading listing and leave frustrated.

Choosing the right model for your app

The right revenue model is not the most popular one or the one that sounds most sophisticated. It is the one that fits what your product does, who uses it, and how often they return. Getting that match right starts with being honest about those three things before you build, not after you launch.

A product that delivers daily value to a consistent user base is a subscription candidate. A product with a strong social or creative loop, where users invest time and identity, can support in-app purchases. A product that creates natural moments where users want to buy something outside the app can earn affiliate revenue without breaking the experience. A product that depends entirely on volume and accepts a lower-quality user experience as the trade-off can sustain advertising.

Questions to ask before committing

1. How often does a typical user return to the product, and why?
2. What would a user lose if they stopped using the product today?
3. Is there a natural moment in the experience where a user would benefit from something outside the app?
4. What platform are you launching on, and does that audience match the revenue model's requirements?
5. Can your app store listing attract users who will understand and accept the monetisation approach before they download?

These questions do not produce a formula. They produce clarity about what the product is and is not suited for. That clarity is worth more than any list of revenue models, because a model chosen without it tends to be replaced within a year under financial pressure, with all the trust damage that comes with it.

Conclusion

Revenue beyond direct sales is a consequence of building a product that people return to, trust, and find genuinely useful on a regular basis. The model you choose matters, but the product conditions that support it matter more. Subscriptions need retention. In-app purchases need invested users. Affiliate revenue needs natural buying moments. Advertising needs volume and a user base that accepts the trade-off. None of them work in a product that users abandon after a few days.

The founders and teams who get this right tend to make the same decision early: they choose a revenue model before they finalise the product design, and then they build the user experience to support it. They launch on the platforms where their audience actually is. They write app store listings that attract the right users rather than the most users. And they treat retention as the number that everything else depends on, because it is.

Building consumer app revenue takes time. The compounding effect of strong retention, honest engagement, and a model that fits the product is real, but it does not show up in week two. Founders who treat the first year as an investment rather than a payback period are the ones who tend to still be iterating in year three, with a product that has earned genuine commercial momentum.

If you are working through which revenue model fits your product, or trying to diagnose why your current approach is not converting, let's talk about your app's revenue strategy.

Frequently Asked Questions