When a user hits an unprompted hard limit, churn spikes. We design freemium models with soft gates and transparent usage bars, achieving up to 12% conversion on limit-based paywalls. Freemium isn't just free + paid—it's a crafted experience where every gate and limit serves conversion. Over ten projects (from note-taking apps to AI editors), we've learned: the main mistake is giving either too little (user doesn't see value) or too much (no incentive to pay). Balance comes from clear value separation: feature gating, usage limits, quality gating, and well-timed paywall triggers. Integration cost is custom, but our clients save up to 40% on monetization by reusing our EntitlementManager.
Freemium is a business model where basic functionality is free and advanced features are paid.
Boundaries of Freemium: Feature Gating, Usage Limits, Quality Gating
Three effective patterns:
-
Feature gating — basic features free, advanced paid. E.g., task creation unlimited (free) plus team collaboration (premium). If a paid feature is free in a competitor's app, the value is lost.
-
Usage limits — same features but with quantitative caps. E.g., 3 projects in free version, 7 AI queries per day. Limits must be noticeable but not frustrating. 80% of users leave if the limit is not shown beforehand.
-
Quality gating — export without watermark, high resolution — premium. Popular in creative apps.
On the client, entitlement checks go through a centralized EntitlementManager—a single FeatureFlag + Entitlement layer. No scattered if-else.
When to Use Soft Gate vs Hard Gate
| Aspect |
Hard gate |
Soft gate |
| Block type |
Feature physically unavailable |
Feature accessible, then paywall |
| Conversion |
Lower — user doesn't see value |
Up to 40% higher — user tries and buys |
| Application |
Resource-intensive features (AI, cloud) |
Others |
Soft gate converts better, so we recommend it for most features. On iOS, implement via FeatureGateModifier in SwiftUI:
Button("Export HD") { viewModel.exportHD() }
.featureGated(.hdExport, paywallTrigger: .featureTap)
Displaying Limits and Progress Bars
Users must see their limits in advance. A hidden limit that triggers suddenly is frustrating. Better: a progress bar '7 of 10 AI requests today' and at 80% — a soft nudge towards premium. Limits are stored server-side; the client receives via API usage_quota. Daily reset is done by cron, with a push {"type": "quota_reset"}.
Effective Paywall Triggers
Freemium requires well-timed paywall presentations. Organic triggers (user naturally hits a limit) convert better than forced ones. PaywallTrigger enum includes: .usageLimitReached, .featureTapped, .exportAttempted, .scheduled(day: 7). Each trigger is A/B tested.
| Trigger |
Description |
Example Conversion |
| usageLimitReached |
Limit reached |
12% |
| featureTapped |
Attempt to use paid feature |
8% |
| exportAttempted |
Attempt to export (premium) |
15% |
| scheduled(day: 7) |
7 days of usage |
10% |
Retention-driven upsell: if a user is active for 7 days, conversion increases. Day-7 retention of such users is 70%+.
Why Smooth Downgrade Boosts LTV
When a user cancels subscription, they downgrade to the free plan. Smooth downgrade: if they have 15 projects with a limit of 3 — do not delete them; mark read-only and display 'Your projects are saved — re-subscribe to edit.' This increases re-subscription chances by 25%. On the client, DowngradeManager when entitlement changes from premium to free, calculates excess and updates UI without data deletion.
StoreKit 2 / Play Billing Integration
Auto-renewable subscription: product.subscription?.renewalInfo contains willAutoRenew — display status. Manage subscription: URL(string: "https://apps.apple.com/account/subscriptions") for iOS, launchBillingFlow with SubscriptionUpdateParams for plan changes on Android. For details, see StoreKit 2 documentation.
Our Process and What's Included
- Feature Map design (free vs premium).
- Develop EntitlementManager + FeatureGate layer.
- Implement limits and their display.
- Configure paywall triggers.
- Integrate StoreKit 2 / Play Billing.
- Implement downgrade logic.
- Set up A/B testing (Firebase Remote Config).
- QA and release.
What's included in freemium implementation
- Feature Map document
- EntitlementManager and FeatureGate code
- Paywall UI (adaptive for iOS/Android)
- A/B testing setup (Firebase Remote Config)
- Monetization model documentation
- Support during app store release
Timeline Estimates
Freemium model implementation with EntitlementManager, feature gating, limits, and soft/hard gates — 5 working days if IAP integration is ready. From scratch including StoreKit 2 / Play Billing — 1.5 to 2 weeks.
Contact us to discuss your monetization model — we'll help find the balance between free and paid to maximize LTV. Get a consultation for your project today.
Mobile App Monetization: IAP, Subscriptions, and Ad Mediation
An app with poorly implemented purchases loses money not because users don't want to pay, but because a StoreKit transaction hangs, Receipt Validation fails with an error, or restore purchases doesn't work — and the user writes to support or leaves a 1-star review. Our experience (over 7 years in mobile development) shows that proper monetization increases LTV by 30–60% within the first three months after implementation. Get a consultation on monetizing your app — we'll analyze the current model and find growth points.
Why StoreKit 2 is the Best Choice for IAP?
StoreKit 2 (iOS 15+) is a modern API with async/await and device-side verified transactions without a server. Transaction.currentEntitlements returns all active purchases. Key change compared to StoreKit 1: JWS signature verification on device via VerificationResult<Transaction> — no need to send receipt to server for basic validation.
But server-side validation is still needed for consumable purchases and fraud prevention. App Store Server API replaces the old /verifyReceipt endpoint. Webhooks via App Store Server Notifications v2 provide real-time events: SUBSCRIBED, DID_RENEW, EXPIRED, REFUND — without polling.
A typical mistake: not handling paymentQueue(_:updatedTransactions:) in the background for unfinished transactions. User bought a consumable, app crashed before finishTransaction — purchase remains in queue, restores on next launch and requires reprocessing on server. Without server idempotency — double crediting.
How Not to Lose Revenue on Subscriptions?
The subscription model requires tracking states: trial → active → grace period → expired → refunded. RevenueCat is the de facto standard for managing subscriptions in production. It abstracts StoreKit and Google Play Billing, providing a unified API, webhooks, cohort analytics, and A/B testing of paywalls.
Alternatives to RevenueCat include custom implementations with Adapty or Qonversion. Fully custom only if data must not leave the infrastructure or there is non-standard logic. We guarantee that webhook setup and subscription lifecycle event handling is done without losses — verified on projects with over 500k DAU.
Google Play Billing Library 6+ requires handling PurchasesUpdatedListener and explicitly calling acknowledgePurchase() or consumePurchase() within 3 days — otherwise Google automatically cancels the purchase and refunds. The average cost of such an error is a significant loss per user per month (based on our project data).
Ad Mediation: Boosting CPM via Bidding
Showing ads from a single source means losing revenue. Mediation (waterfall or bidding) requests ads from multiple networks and displays the best bid. Google AdMob is the foundation for banner, interstitial, rewarded ads. Mediation via AdMob Mediation or MAX (AppLovin) is the second de facto standard. MAX uses In-App Bidding — a real-time auction without waterfall. In practice, MAX yields significantly higher CPM than classic waterfall (depending on geo and audience). For example, for rewarded video in the US, the improvement can be substantial. With 100,000 rewarded video impressions per day, switching from waterfall to In-App Bidding can generate additional daily revenue.
ironSource (Unity Ads) has a strong position in the gaming segment, especially rewarded video. Mintegral covers the Asian audience well.
Setting up mediation requires ATT (App Tracking Transparency) on iOS 14+. Without requestTrackingAuthorization, ad CPM drops by 3-5 times for non-consenting users. SKAdNetwork and Privacy Manifest (iOS 17) are mandatory requirements; without them, review fails.
| Network |
Ad Type |
Feature |
| AdMob |
banner, interstitial, rewarded |
Wide network, easy start |
| MAX (AppLovin) |
rewarded, interstitial |
In-App Bidding, high fill rate |
| ironSource |
rewarded video |
Best for games |
| Mintegral |
rewarded, native |
Asia, programmatic |
How We Implement Monetization: Step-by-Step Process
- Current model audit — analysis of funnel, paywall, price tiers, and identification of bottlenecks.
- Model design — choose type (subscription, consumable, non-consumable) and optimize price points.
- IAP integration — set up StoreKit 2 / Google Billing 6, receipt validation, webhooks.
- Ad mediation — connect 3-6 networks, configure waterfall or In-App Bidding, test fill rate.
- Analytics and cohorts — integrate RevenueCat, Amplitude, or Firebase for LTV tracking.
- A/B testing of paywall — use Remote Config for experiments without a release.
- Launch and monitoring — 2 weeks of free support after launch, bug fixes by 24-hour SLA.
How to Design a Freemium Model and Paywall?
Freemium works when the boundary between free and paid is properly drawn. Too strict a paywall at the start — users delete. Too generous a free tier — no incentive to pay.
A technically sound pattern: server-side feature flags (Remote Config in Firebase or LaunchDarkly) control access to features. This allows A/B testing of paywall without a release, changing trial conditions, and running promotions.
Implementation at the code level: EntitlementManager — a single point for checking access to features, aware of subscription status, flags, and promos. No scattered isPremium checks throughout the code. Experience shows this approach reduces paywall-related bugs by 80% (confirmed on 30+ projects).
Checklist of Typical Monetization Mistakes
- Missing handling of
unfinished transactions — revenue loss of 5-10%.
- No server-side idempotency for consumable processing — double crediting.
- Forgot to call
acknowledgePurchase() on Android — purchase cancelled after 3 days.
- Not handling
REFUND and DID_RENEW events — incorrect subscription status.
- Paywall without A/B testing — leaving 20-40% of monetization potential.
- Ads from a single source (e.g., AdMob without mediation) — CPM 15-30% lower.
Scope of Monetization Work
- Current model audit — analysis of funnel, paywall, price tiers.
- IAP integration — StoreKit 2 / Google Billing 6, receipt validation, webhooks.
- Ad mediation — configure MAX / AdMob, connect 3-6 networks, test fill rate.
- Analytics setup — RevenueCat, Amplitude / Firebase, cohort analysis.
- Documentation — description of entitlements, restoration procedure, review checklist.
- Team training — analysis of typical mistakes, support recommendations.
- Guarantee — 2 weeks free support after launch, bug fixes by 24-hour SLA.
Estimated Timelines
| Stage |
Duration |
| Basic IAP (one store) |
1–2 weeks |
| Subscription system + RevenueCat + paywall |
3–5 weeks |
| Ad mediation (MAX + 3 networks) |
1–2 weeks |
| Full cycle (IAP + ads + analytics) |
4–8 weeks |
Cost is calculated individually. We have been working in this field for over 8 years and have implemented monetization in over 40 projects — many of which passed App Store Review without a single rejection. Contact us for an audit or order a consultation — we'll tell you what growth points exist in your app.
