Annual subscriptions vs lifetime purchase pricing on iOS: the revenue math and when to offer each

A practical breakdown of the break-even math, LTV implications, and strategic trade-offs between annual subscriptions and one-time lifetime purchase pricing for iOS apps — including when to combine both on the same paywall.

The lifetime purchase has made something of a comeback. After years of indie iOS developers migrating everything to subscriptions — drawn by recurring revenue and StoreKit 2's improved tooling — a meaningful cohort has rediscovered the one-time perpetual sale as a viable revenue lever. The question isn't whether subscriptions beat lifetime purchases in the abstract. It's whether your specific app, at this stage of growth, benefits from one model, the other, or both running in parallel.

This post works through the revenue math, the LTV implications, and the practical signals that should push you toward each option — or toward a combined paywall that uses both.

What "lifetime" actually means on the App Store

A definitional point that trips up many developers: Apple does not have a native "lifetime subscription" product type. What the App Store supports is a non-consumable in-app purchase — a one-time payment that unlocks features permanently on all of a user's devices and is restorable without charge. Developers label this a "lifetime deal" in their paywalls, but under the hood it is a non-consumable IAP, not a subscription product.

This distinction matters operationally. Non-consumables are eligible for Apple's 15% commission rate under the Small Business Program (if you qualify) — the same rate subscriptions earn in their second year. They do not appear in subscription analytics in App Store Connect; they show up in sales reports instead. And they are not subject to the renewal mechanics, grace periods, or billing retry logic that governs subscriptions. You can offer a lifetime deal alongside your subscription plans, inside the same paywall, using standard StoreKit 2 APIs, with each product type handled separately by your entitlement logic.

If you are using a subscription management SDK such as RevenueCat or Adapty, both support entitlements that can be granted via either a subscription or a non-consumable purchase — your in-app entitlement check remains the same, but the underlying product and verification path differ. For a primer on transaction verification, see our guide to App Store Server API transaction verification.

The revenue math: break-even and the retention curve

The central tension between subscriptions and lifetime purchases is timing. A subscription spreads revenue over months and years; a lifetime purchase front-loads it into a single transaction. The break-even calculation is straightforward: at what retention point does cumulative subscription revenue surpass the one-time lifetime amount?

The table above uses a 15% commission throughout. Outside the Small Business Program, at 30%, the figures shift: annual subscription net drops to $20.99/year, lifetime net drops to $55.99. The break-even ratio stays similar (~2.7 years), but the absolute proceeds are lower across the board.

The critical variable is your actual retention curve. If your average subscriber churns before the break-even point, the lifetime purchase is the higher-LTV outcome for that cohort — even though the monthly cash flow looks worse. Annual state-of-subscription reports from RevenueCat have consistently shown that median retention beyond the first renewal year is low in many app categories, which is precisely why developers who run the retention math often find lifetime pricing surprisingly attractive.

The implication: before setting a lifetime price, build a simple cohort retention model. Even a rough one — what fraction of trial converters are still active at 6, 12, 24 months — will tell you whether your median subscriber stays past the break-even or churns well before it. That single data point should anchor your decision more than any rule of thumb. See our cohort LTV model post for a worked example of this analysis.

When the subscription model wins

Subscriptions have three structural advantages: predictability, scalability, and pricing flexibility.

Predictability matters most for apps with ongoing infrastructure costs. AI inference calls, cloud sync, real-time features, and push notification pipelines all carry per-user costs that compound over time. A lifetime buyer who uses your app heavily for five years while paying once creates a hidden cost liability that grows with engagement. The subscription model matches your cost structure to your revenue: the user pays as long as they use the service.

Scalability favors subscriptions at the point where you have a reliable acquisition channel. If you are running Apple Search Ads campaigns, the subscription model lets you model a payback period (customer acquisition cost divided by monthly net revenue) and scale spend with confidence. A lifetime-purchase model makes that math murkier because the entire acquisition cost must be recovered in a single transaction — there is no partial recovery if the user churns before conversion.

Pricing flexibility is also tilted toward subscriptions. Apple's price increase mechanics allow you to raise prices for new subscribers while keeping existing ones on their current rate — a user-friendly approach that reduces churn risk during a price change. The grandfathering rules and the mechanics of communicating price changes are covered in detail in our post on Apple's subscription price grandfathering. With a non-consumable lifetime purchase, there is no grandfathering concept: you set a new price and all future buyers pay it, with no impact on prior purchasers. That is simpler to administer, but it also means you cannot run a targeted price increase the way you can with subscriptions.

When the lifetime purchase wins

Lifetime purchases have structural advantages in several scenarios that are easy to overlook if you start from a subscriptions-first mindset.

Offline and low-infrastructure apps — reference tools, local databases, utilities, offline-first productivity apps — have marginal per-user costs close to zero after the initial download. There is no ongoing cost liability, so the decision is purely about revenue timing and user psychology.

Price-sensitive markets are a case where lifetime pricing can outperform a subscription in absolute conversion rate. In markets with lower purchasing power, a modestly priced lifetime purchase may convert where a recurring subscription charge fails. Phiture's research on subscription conversion across markets suggests that "subscription aversion" — users actively avoiding recurring charges — is stronger in markets where credit card penetration is lower and disposable income is constrained. A one-time payment feels more like buying a product and less like taking on a financial commitment, which matters enormously in these markets. For territory-specific pricing context, see our territories reference.

Early-stage apps benefit from lifetime deals as both a cash-flow accelerator and a trust signal. For a new developer without an established track record, a subscription asks users to commit recurring payments to an unknown publisher. A lifetime option reduces the perceived risk: the user pays once and owns the unlock permanently. Early adopters who take this deal also tend to become vocal advocates, which has indirect marketing value.

Paywall anchoring is a more subtle use case. Some developers use a lifetime tier as the top rung of a three-option paywall — monthly, annual, lifetime — primarily to anchor the annual plan as the "sensible middle." Even if the lifetime option converts infrequently, its presence can lift annual plan conversion by making the annual look comparatively reasonable. This anchoring dynamic is covered in the context of broader paywall design in our post on App Store pricing psychology.

Structuring a paywall that includes both

Many high-performing apps offer subscription and lifetime options simultaneously. The most common structure is a three-tier paywall: monthly (highest per-period cost, lowest commitment), annual (the primary revenue target, typically discounted 50–60% versus monthly annualized), and lifetime (priced as a premium option for committed users).

The pricing ratio matters. If your lifetime is priced below 2× your annual, experienced buyers will recognize the underpricing and take it — and you leave long-term value on the table for users who would have subscribed for years anyway. If it exceeds 5× your annual, conversion collapses. The 2.5–4× range is where most successful implementations sit, with the specific number informed by your retention data and the competitive context of your category.

One operational note: because lifetime purchases are non-consumables rather than subscriptions, your analytics and reporting split. Subscription revenue and metrics appear in App Store Connect's subscription analytics; non-consumable revenue appears in sales reports. If you are building a unified revenue dashboard — for instance, via the App Store Connect Reports API — you will need to pull from both data sources and merge them at the entitlement level, not the product type level.

The legacy-user migration edge case

One nuanced scenario worth covering: lifetime purchases can serve as an upgrade path for apps transitioning from a paid-upfront model to subscriptions. If you have a legacy base of one-time purchasers who are entitled to the current version but not to new subscription-only features, a lifetime IAP at a loyalty discount gives them a meaningful upgrade option without forcing them into a recurring charge they may resent.

Apple has specific expectations around what existing paid-upfront purchasers retain access to when an app migrates to a subscription model. Before designing a migration that combines paid legacy access with a new lifetime IAP, it is worth reviewing Apple's App Review guidelines on this topic carefully. The rules are designed to protect users from losing access they already paid for — understanding the boundaries helps you design a migration that is both commercially effective and compliant.

A decision framework

No single model wins unconditionally across all apps. The decision reduces to four variables:

1. Ongoing infrastructure cost per user — if material and growing with usage, subscriptions protect long-term margins.
2. Observed or projected retention — if median retention is below your break-even year, a lifetime option captures more value from users who would otherwise churn.
3. Market and user psychology — higher price-sensitivity markets and users with subscription aversion convert better on a one-time model.
4. Growth stage — early-stage apps benefit from lifetime's immediate cash and trust signal; apps with established acquisition funnels benefit from subscription predictability and LTV modeling.

Run both the subscription cohort LTV model and the lifetime break-even calculation with your own retention numbers before committing. The math is not complex, and a realistic cohort retention curve — even an estimate based on comparable apps — will tell you far more than category averages alone.

Sources and further reading

• RevenueCat: State of Subscription Apps (annual industry report)
• Apple Developer Documentation: Non-consumable product type (StoreKit)
• Apple Developer Documentation: Restoring purchased products
• Phiture: Mobile Growth Stack — conversion and paywall research
• Apple: Auto-Renewable Subscriptions — overview and guidelines
• Apple Developer Documentation: App Store Connect Sales and Finance Reports