Exit Offers Arrive as Standard Paywall Infrastructure
A second paywall shown at the moment a user dismisses the primary offer โ the exit offer โ is now supported natively by RevenueCat's paywall system for Android. When a user taps close or swipes away without purchasing, the SDK intercepts the dismiss action and presents an alternative offer: typically a lower price, a longer trial, or a different subscription tier. This mirrors e-commerce cart-abandonment recovery tactics and requires no code changes once configured in the dashboard.
The feature works only when paywalls are presented through PaywallDialog or PaywallActivityLauncher. The embedded Paywall composable does not support exit offers because it has no dismiss flow to intercept. For apps using navigation-based flows, switching to a dialog-based presentation unlocks the capability without altering the user experience.
Exit offers are configured entirely in the RevenueCat dashboard: create an exit-offer offering, attach a paywall to it, and link it to the main paywall. The SDK preloads the exit offering in the background, checks for a completed purchase before dismissing, and transitions to the exit offer automatically if the user has not subscribed. Analytics track exit-offer impressions separately, letting teams measure abandonment-recovery impact.
On iOS, the same pattern holds: exit offers work with presentPaywall() and presentPaywallIfNeeded(), but not with PaywallView embedded in SwiftUI. Apple's App Store Review Guideline 5.6 has been cited in some rejections for apps showing additional offers on dismissal, though enforcement is inconsistent. Teams seeking a safer initial approach can use RevenueCat's Targeting feature to enable exit offers only for Android users.
Exit offers represent a structural shift in how conversion moments are designed. Rather than treating paywall dismissal as the end of the opportunity, the tactic extends the funnel by one step โ catching the user on the way out with an alternative they might accept.
Dynamic Paywall Rules Enable Contextual Component Visibility
RevenueCat also introduced Paywall Rules, allowing developers to show or hide paywall components based on runtime conditions without creating multiple paywall variants. Rules can adjust visibility and text overrides based on whether the selected package includes an introductory offer, a promotional offer, a specific package identifier, or a custom variable passed at render time.
This means a single paywall can now handle multiple scenarios: show a trial timeline only when a trial is available, swap package highlights based on user segment, or tailor messaging for promotional offers. Rules are evaluated in a defined order at runtime, and multiple rules can coexist on the same component.
The feature reduces the overhead of maintaining separate paywalls for different contexts and enables more sophisticated conversion rate optimization without requiring new app releases. It positions paywalls as dynamic surfaces rather than static pricing screens.
The 75% LTV Gain from Dropping the Hard Paywall
A growth advisor working with a consumer subscription company replaced a hard paywall with a multi-step model: the product became free, but users were offered a seven-day trial of the premium experience. After the trial, users were prompted to subscribe. Combined with pricing and packaging optimizations, this shift increased LTV per user by 75%.
The shift represents a move from "playing checkers to playing chess," as the advisor described it. Hard paywalls convert five times better than freemium on average, making them the reliable choice for bootstrapped startups. But for companies aiming for billion-dollar scale, freemium is often the only way to grow a massive top-of-funnel audience. The challenge is executing the model with enough sophistication to avoid the trap of delayed monetization and low conversion.
The multi-step paywall is a hybrid: it combines free access with an immediate trial offer, reducing friction while still capturing high-intent users early. The strategy depends on delivering enough value during the free experience to justify the upgrade ask when the trial ends.
Industry data supports the importance of trial length in this context. Three-day trials capture curiosity; seven-day trials capture routine. Once a product becomes part of a user's daily workflow, the decision to subscribe shifts from "Is this worth trying?" to "Do I want to lose this?" Longer trials filter for users who have experienced repeated value and built reliance on core features, driving stronger post-trial wiki:retention-rate and higher lifetime value.
Freemium Tier Design: A Six-Step Strategic Framework
Designing an effective freemium model begins with clarifying the goal. Freemium can serve multiple purposes: standing out in a competitive market, driving organic growth through word-of-mouth, building user habits over time, generating data or network effects that improve the product, or achieving impact at scale. The goal determines how generous the free tier should be and where the paywall line is drawn.
The next step is defining user success: what job is the user trying to accomplish, and what actions predict they will achieve it? Free users should be able to make meaningful progress toward that goal but not reach the full solution. This requires understanding both the user's objective and the product's core value loop.
With that clarity, teams can choose a freemium architecture:
- Taster model: same product, with usage limits (Zoom's 40-minute cap, Notion's block limits)
- Split model: different features for different user types (CapCut's basic vs. polished editing tools, Surfline's casual vs. power-user forecasts)
- Hybrid model: taster limits plus split features (Slack's 90-day message history with premium-only cross-org channels, Duolingo's unlimited lessons with premium-only offline access)
A "Bill of Rights" for free users acts as a constitution for what cannot be touched. The risk in freemium is that incremental experiments โ each showing a lift in conversion โ cumulatively erode the free tier to the point where it no longer delivers real value. Nobody runs a holdout group long enough to measure that cumulative effect. Writing down what must always remain free prevents slow drift.
Trials in freemium should be strategic, not default. If premium features are self-evident from the free tier ("I can see the leaderboard exists but I can't use it"), a trial may be unnecessary. If premium features need to be experienced to be understood, a trial makes sense. Reverse trials โ where users start with premium access and then drop to free โ leverage loss aversion more effectively than traditional trials.
Apple Enforces Payment Policy Despite Epic Ruling Liberalization
Apple temporarily removed Cal AI, a food-logging app owned by MyFitnessPal, from the App Store for multiple guideline violations. The app had bypassed Apple's wiki:in-app-purchase flow by implementing an embedded payment system using Stripe, removing Apple's IAP as an option during checkout. This violated Guideline 3.1.1, which requires that IAP be offered alongside external payment links.
Cal AI was also cited for deceptive billing practices: the paywall displayed weekly calculated pricing more prominently than the actual billing amount, and a free-trial toggle obscured information about automatic renewal. Additionally, the app prompted users who declined the first subscription offer with a second, different purchase flow โ a manipulative tactic flagged under the Developer Code of Conduct's Guideline 5.6.
The app returned to the store after addressing the violations. The enforcement action demonstrates that Apple is actively policing how developers implement web payments, even though the Epic Games court ruling loosened earlier restrictions. U.S.-based developers can now link out to external payment systems, but most apps are still required to offer Apple's IAP alongside that link. The exception is for "reader" apps providing subscription-based access to digital content like books, audio, music, or video. Cal AI does not qualify.
The incident serves as a warning that platform guardrails remain in force. Apple is still policing billing design, payment flow implementation, and user-facing tactics โ even at the risk of losing its cut of revenue from a viral app that reached the No. 4 spot on the Health & Fitness charts.
Paywall Placement and Testing Drive Performance Spread
Paywall performance varies widely based on placement, design, and trial structure. Onboarding paywalls capture users when motivation is highest and the product is top-of-mind, making them the most common high-conversion placement. Contextual paywalls triggered when users hit gated features work when there is enough free value to build desire but not enough to eliminate urgency. An always-visible "Get Now" upgrade button can increase revenue by 10โ20%, serving as a constant reminder of the premium option.
Testing focus areas include:
- Visual hierarchy and imagery: first impressions shape perceived value in the seconds before a user bounces
- Trial length and pricing: longer trials filter for users who have built reliance; offering three products instead of two (using decoy pricing) can lift conversion by 44%
- Benefit-oriented copy: testing feature lists versus user-benefit summaries ("Advanced analytics" vs. "See exactly what's holding your progress back")
- Transparency in billing: clear renewal terms and cancellation instructions increase perceived legitimacy
- CTA copy and color: small variations in button text and color can produce meaningful lift
- Negative priming in decline buttons: "No, I prefer fewer features" versus "Maybe later" influences exit behavior
AI Cost Considerations Reshape Freemium Boundaries
AI features are lowering the cost of software development but raising the cost of serving users. Some features that would ideally be free are prohibitively expensive to give away, leading to usage-based models where free users receive a set number of credits or queries. ChatGPT, for example, does not lock features but limits how much of the best model you can use before upgrading.
A presentation tool, Gamma, reached profitability within six months by using longer-tail LLMs instead of the most powerful frontier models. For their use cases, these models provided performance that was "good enough" while delivering faster response times and drastically lower compute costs. Speed and affordability can be more critical to the user experience than peak AI performance, especially in consumer apps.
AI is also changing user acquisition. A running app, Runna, used AI tools to increase creative testing volume from tens of concepts per month to over 400. This rapid learning cycle does not just optimize ad spend by finding winning ads faster โ it feeds insights directly back into product roadmap decisions, creating a tighter loop between marketing and product.
Implications for Practitioners
The current wave of innovation in monetization infrastructure โ exit offers, dynamic paywall rules, hybrid freemium models, AI-driven creative testing โ reflects a maturation of the subscription app economy. The question is no longer whether to paywall or how to price, but how to design conversion moments that adapt to user intent, usage patterns, and platform constraints.
For teams operating in competitive categories, freemium strategy offers a path to scale but requires exceptional execution to avoid the median outcome of 2.1% conversion. The difference between the median and the top 10% is enormous, and getting tier design right is what determines placement in that spread. Exit offers and dynamic rules provide tactical levers, but only if the underlying value proposition and free-to-paid journey are sound.
Apple's enforcement of payment policy underscores that platform rules remain binding even as payment options expand. Billing design, user-facing tactics, and IAP availability are still actively policed. Teams must balance monetization optimization with compliance, particularly when implementing secondary offers or embedded payment flows.
The shift from hard paywalls to freemium for high-growth apps reflects a broader strategic trade-off: short-term revenue efficiency versus long-term scale. Hard paywalls convert better and generate faster payback, making them the right default for most apps. Freemium requires more capital, more patience, and more sophistication โ but for products that can execute it well, it unlocks word-of-mouth distribution, habit formation, and network effects that hard paywalls cannot match.