Subscriptions vs In-App Purchases vs Ads: What Earns Most in 2026

Before any pricing discussion, understand what Apple takes. Every dollar that flows through Apple's In-App Purchase system has Apple's commission removed before you see it.

Standard rate: 30 percent commission on all transactions. This applies to developers earning more than $1 million per year in proceeds.

Small Business Program rate: 15 percent commission. Any developer who earned under $1 million in the previous calendar year qualifies. Apple auto-notifies eligible developers; you apply through App Store Connect and approval is typically fast.

Subscription loyalty discount. Apple drops the commission to 15 percent on any subscription after a customer has been subscribed for more than one year, regardless of your overall revenue. This significantly boosts long-term subscription economics.

In practice for most indies in 2026: you will be paying 15 percent on nearly every transaction because you will qualify for the Small Business Program. Budget as if you keep 85 percent of your gross.

Example: a $4.99/month subscription generates roughly $4.24 net after Apple's 15 percent cut. A $29.99 annual subscription generates about $25.49 net. Internalize these numbers when you price anything.

Important: digital goods and services must go through Apple's IAP for iOS apps. You cannot route users to your website to pay. Apple rejects for this, and in some cases has pulled apps entirely. Physical goods (Uber rides, Amazon packages) are different — those can use any payment processor. For indie utility apps, you live in the IAP world. See the Apple App Store review guide for how this rule interacts with approval.

For an indie working from home with no marketing budget, monetization model is almost a survival question. Subscriptions compound retained users into recurring revenue. Ads need scale you cannot afford to buy. Let's run actual numbers comparing the three main monetization models for a hypothetical indie app with 10,000 monthly active users.

Subscription model: 10,000 MAU, 3 percent of free users convert to paid (typical for a good utility), so 300 paying subscribers at $4.99/month. Gross revenue: $1,497/month. After Apple's 15 percent cut: $1,272/month. Over a year, accounting for churn but also for new conversions, expect steady-state revenue of $12,000 to $18,000.

In-app purchase model (one-time unlock at $9.99): 10,000 MAU, 4 percent conversion (slightly higher than subscription because one-time feels lower-commitment), so 400 one-time purchases per month of new users. Gross: $3,996/month. Net: $3,397/month. BUT — this is only sustainable if you keep acquiring new users. Existing users have already paid and do not pay again. If acquisition plateaus, revenue plateaus immediately.

Ad-supported free model: 10,000 MAU, average session length 4 minutes, 2 ad impressions per session, 20 sessions per user per month. That is 400,000 ad impressions per month. At $5 to $10 eCPM (typical for banner/interstitial ads in utility apps in 2026), gross revenue: $2,000 to $4,000/month. Net after AdMob's cut: $1,700 to $3,400/month. No Apple cut because ads are not IAP.

The subscription advantage compounds. After year 1, subscribers from month 1 who retain are still paying. IAP revenue from month 1 buyers is gone. Ad revenue from month 1 users is only ongoing if they keep opening the app — churn decays the base. Subscriptions turn each acquired user into a long-term annuity.

The catch: subscriptions only work if you have a retention case. Apps users only need occasionally (ID photo, unit converter) cannot sustain subscriptions. IAP is honest there. Know which category you are in. For examples of what works in which niche, see best iOS app niches for 2026.

Technically implementing subscriptions used to be hell. In 2026, it is manageable even for beginners because of two things: Apple's StoreKit 2 (modern subscription API introduced in iOS 15) and RevenueCat (third-party service that handles the server-side hard parts).

StoreKit 2 is Apple's modern framework. It uses async/await Swift, provides type-safe products, and handles purchase flow natively. Writing subscription logic directly in StoreKit 2 is feasible for a small app but has real complications: server-side receipt validation for fraud prevention, handling subscription status across devices, managing introductory offers, and subscription lifecycle events (cancellation, billing retry, refunds).

RevenueCat is a third-party SaaS that wraps StoreKit, handles server-side validation, manages subscriber state across devices via an anonymous user ID, and provides clean analytics. It is free up to $2,500/month in MRR, then takes a small percentage above that. For 95 percent of indie developers, RevenueCat is the right answer.

Typical implementation path:

1. Create subscription products in App Store Connect (monthly and annual tiers).
2. Add RevenueCat SDK to your iOS app.
3. Wire up the paywall screen with RevenueCat's `Offerings` API.
4. Gate premium features based on RevenueCat's subscription status.
5. Test with Sandbox accounts in TestFlight before shipping.

What to avoid: do not try to build your own server-side receipt validation unless you have specific compliance needs. It is a maintenance headache, Apple changes receipt formats periodically, and getting it wrong leads to either revenue leakage (users bypassing your paywall) or user anger (legitimate subscribers being locked out).

For the full build path, see how to build an iOS app with AI.

Pricing a subscription is not a guess. There is a reasonably consistent set of patterns that convert well for indie utility apps in 2026.

The $4.99/month, $29.99/year sweet spot. These prices dominate for a reason. Monthly at $4.99 feels cheap enough to try. Annual at $29.99 gives roughly 50 percent savings vs monthly, which is the minimum annual discount that feels meaningful. Below 40 percent annual discount, most users stick with monthly (hurting your LTV).

Anchoring with three tiers is often unnecessary for simple utilities. Two tiers (monthly + annual) outperform three tiers for most indie apps. Save three-tier pricing for apps with genuinely different feature sets per tier.

Showing "per week" on annual plans. "$29.99/year (just $0.58/week)" converts better than "$29.99/year" alone because the weekly framing feels smaller. Legitimate psychological framing, not manipulation.

Free trials matter. 7-day free trials on monthly plans improve conversion significantly. Longer trials (14 or 30 days) do not consistently help and extend the "will this convert?" decision. 7 days is the indie utility standard.

Introductory offers. Apple supports pay-up-front-for-year-one at a discount ($19.99 first year, $29.99 subsequent years). These can boost initial conversion but hurt year-2 retention when the price jumps. Use carefully.

Paywall placement. The paywall should appear after the user has experienced value, not before. "Complete onboarding → see a win → encounter paywall" converts 2x to 4x better than "see paywall on first launch." This is both ethically and economically correct.

Localized pricing. Apple lets you set per-country prices, and they matter. $4.99 in the US corresponds to roughly 4.99 EUR in Europe but feels very different in rupees, reais, or pesos. Apple's default tier mapping is usually reasonable; aggressive underpricing in emerging markets can raise revenue noticeably. For the broader international play, see the localization section of the App Store ASO guide.

Subscriptions are usually best, but not always. There are specific scenarios where one-time IAP outperforms subscriptions.

Use IAP when:

• Your app does a one-off job. An ID photo generator, a one-time PDF merger, a specific file converter. The user needs it once or twice, not forever. Subscription would feel exploitative and convert badly.
• Your app has expansion content. A meditation app with specific course packs, a language app with specific vocabulary packs, a fitness app with specific training programs. Users pay per course they want.
• Your app is a game or has game-like progression. Unlockable levels, cosmetics, power-ups. Consumable IAP fits user mental model.
• Your app has a small, one-time "remove ads" upgrade. Traditional freemium remove-ads-at-$2.99 still works for certain categories.
• Your audience culturally rejects subscriptions. Certain user bases (older users, users in certain niches) have strong "I will never pay a subscription" feelings. Listen to reviews.

Revenue math for IAP: because IAP is one-time, your revenue depends entirely on ongoing user acquisition. Steady-state IAP revenue = new monthly users × conversion rate × average purchase value. There is no compounding from retained users. Plan your marketing accordingly.

Hybrid models work. Some apps succeed with a subscription for core features + IAP for occasional premium content drops or special packs. Just make sure the mental model is clear to users so you do not confuse them at the paywall. Apple allows both in the same app.

Paid-upfront is essentially dead for consumer apps in 2026. The one exception: premium professional tools where $10 to $30 upfront is normalized (specific audio editors, specialty calculators for trades). For 99 percent of indie apps, do not go paid-upfront.

Ads pay the least per user of any monetization model. They only produce meaningful income at scale that indie apps rarely reach.

Rough 2026 ad revenue per user per month for utility apps, assuming normal engagement:

• Banner ads: $0.05 to $0.20 per monthly active user.
• Interstitial ads: $0.15 to $0.50 per monthly active user.
• Rewarded video (user opts in to watch for rewards): $0.30 to $1.00 per monthly active user.

Compare to a subscription app: even at 3 percent conversion, each monthly active user produces $0.15 in monthly revenue ($4.99 × 3 percent), and each paying user produces $4.24 net. The kicker: paying users produce that every month.

Ads only work when all three are true:

1. You have high volume (tens of thousands to hundreds of thousands of DAU).
2. Your app has long session times (utility apps with 30-second sessions earn nothing).
3. Subscriptions would fundamentally break your user experience (social feeds, content consumption).

When to use ads as a supplement (not primary):

• Free tier of a freemium app to lightly monetize users who will never subscribe. Keep ads minimal — aggressive ads drive 1-star reviews and hurt retention.
• Content or media apps where paywall would kill engagement.
• Social or viral apps where growth requires frictionless free access.

Ad networks to consider for indies in 2026: Google AdMob (largest reach), AppLovin (competitive for rewarded video), Unity Ads (games-leaning). Do not layer more than 2 networks — the integration and mediation complexity is not worth it at indie scale.

Avoid: MRAID banner-heavy implementations that clutter UX, interstitials that appear every screen transition (1-star review magnet), and any ad network with a reputation for malware ads (investigate before integrating). For the bigger revenue picture, see how much indie iOS developers actually make.

Subscriptions look great until you see the churn numbers. Every subscription app loses users every month, and your long-term revenue depends on keeping churn under control.

Typical subscription churn for indie utility apps in 2026:

• Month 1 churn (users who cancel within the first 30 days): 40 to 60 percent of new subscribers. Brutal but normal.
• Month 2 to 6 churn: 10 to 20 percent per month.
• Month 7+ churn: 3 to 8 percent per month for users who made it past the hump.

Lifetime value (LTV) is the average total revenue per paying user. For an indie utility app at $4.99/month with typical churn, LTV lands between $25 and $60 per paying user. Knowing your LTV is essential because it sets your maximum customer acquisition cost.

How to reduce churn:

1. Improve onboarding. Users who never complete a meaningful first action churn fastest.
2. Send value-reminding push notifications. Not spam — genuine reminders of progress ("your 7-day streak!") or new features.
3. Annual plans reduce churn mechanically. A subscriber on an annual plan cannot churn mid-year. Push annual aggressively after the first month.
4. Respond to cancellation. Apple now allows a brief in-app confirmation before cancellation. Use it.
5. Ship updates every 2 to 4 weeks. Active apps retain. Stale apps churn.

Annual plans are your best friend. If 30 percent of your subscribers go annual, your churn economics improve dramatically because they cannot cancel mid-year and annual payment amplifies each conversion.

Free trial conversion. Of users who start a 7-day free trial, 40 to 60 percent typically convert to paid for a well-built utility. Below 30 percent signals your onboarding or value prop is weak. Above 70 percent is suspicious (possibly a trial too short or a paywall showing before value). For retention-adjacent ideas, ChatGPT side hustles and AI automation for small business have parallel economics.

Your paywall is the single most important screen in a subscription app. It is the moment users decide whether your work gets paid for. Small changes in paywall design produce outsized revenue swings.

The components every effective paywall needs:

1. A clear headline stating the benefit users get by subscribing. Not "Premium Access" — "Track Unlimited Habits" or "See Your Full Finance Picture."
2. 3 to 5 specific features listed as short benefits, not feature names. "See your habits on any widget" beats "Widget support."
3. Two pricing options side by side: monthly and annual. Make the annual option visually dominant with a badge ("Save 50%") but do not hide the monthly.
4. Free trial messaging if you offer one: "Try free for 7 days. Cancel anytime." The "cancel anytime" language reduces friction meaningfully.
5. Apple-required disclosures just below the pricing: subscription title, length, cost, trial terms, renewal language, and links to your privacy policy and terms of service. These are mandatory per Apple's guidelines — missing them is a rejection reason.
6. A restore purchases link at the bottom. Apple requires this. Users who reinstall or switch devices will tap it.
7. A clear dismiss option. Hidden X buttons or blocking dismissal entirely hurts conversion and triggers rejection.

Common mistakes:

• Showing the paywall on first launch. Converts terribly because users have not seen value yet. Show after meaningful first action.
• Listing too many features. 10 feature bullets overwhelm. Pick the 3 to 5 that matter most to your specific audience.
• Confusing pricing layouts. Three-tier pricing (basic/pro/ultimate) usually hurts conversion vs two clear options.
• Using generic stock photos. Paywalls with real product UI screenshots convert better than decorated paywalls.
• Auto-selecting monthly by default. Default to annual — it doubles LTV per converter even though monthly-selector rate stays similar.

Test paywall variations one change at a time over 2-week windows. Services like RevenueCat's Experiments feature make A/B paywall testing straightforward. Paywall optimization alone can move indie app revenue 30 to 80 percent without adding a single new feature. For broader monetization framing, see website monetization strategies.