paywallBuild high-converting paywalls for mobile apps and web with proven patterns, pricing strategies, and A/B testing.
Install via ClawdBot CLI:
clawdbot install ivangdavila/paywallActivate on: "create paywall", "subscription screen", "pricing page", "improve conversion", "paywall not converting", "free trial flow".
| Aspect | Mobile (iOS/Android) | Web (SaaS) |
|--------|---------------------|------------|
| Context | Full-screen takeover | Pricing page or modal |
| Timing | Onboarding, contextual, campaigns | Landing page, upgrade prompts |
| Billing | App Store / Play Store | Stripe, Paddle, etc. |
| Trials | Store-managed | Self-managed |
| Testing | Remote config, A/B tools | Standard web A/B |
See mobile.md for iOS/Android specifics. See web.md for SaaS pricing pages.
| Type | When | Conversion share |
|------|------|------------------|
| Onboarding | After install, during setup | 40-60% of trials |
| Contextual | User hits premium feature | 20-30% |
| Upgrade button | Persistent in UI | 10-20% |
| Campaign | Push, email, in-app trigger | 5-15% |
Rule: Always have an onboarding paywall. Most conversions happen when motivation is highest.
See placement.md for timing and trigger strategies.
Every high-converting paywall includes:
See layout.md for design patterns and examples.
| Pattern | Effect |
|---------|--------|
| Monthly equivalent | "Just $4.99/mo" for yearly |
| Savings badge | "Save 50%" on annual |
| Decoy plan | Makes target plan look better |
| Price anchoring | Show "was $X" or compare to alternatives |
Default selection matters. Pre-select the plan you want users to buy.
See pricing.md for plan structures and psychology.
See copy.md for formulas by paywall type.
Test in this order (highest impact first):
Rule: Always A/B test paywall changes. Even "obvious" improvements can backfire.
See testing.md for metrics, sample sizes, and experiment design.
Stop and fix:
Generated Mar 1, 2026
A fitness app integrates a paywall after the user completes initial setup, offering a free trial to premium features like personalized workouts. This leverages high user motivation post-install, following the skill's rule to always include an onboarding paywall for 40-60% of trial conversions.
A project management software company updates its web pricing page with clear plan options, a highlighted annual plan with savings badges, and trust signals like 'cancel anytime'. This aims to improve conversion rates by applying core layout elements and pricing display patterns from the skill.
A photo editing app triggers a paywall when a user attempts to access an advanced filter, presenting benefits over features and a single CTA. This targets users at the point of need, aiming for 20-30% conversion share as per the placement strategy.
A streaming service runs remote A/B tests on its mobile app to evaluate different price points and plan presentations every 6-12 months. This follows the skill's testing priority to optimize revenue and avoid backfiring changes.
Apps on iOS/Android use this skill to design paywalls for in-app purchases or subscriptions managed through app stores. It focuses on onboarding flows and contextual triggers to drive recurring revenue from user upgrades.
Web-based software companies apply the skill to create pricing pages or modals that convert visitors into paying customers. It emphasizes plan options, trust signals, and A/B testing using tools like Stripe for billing.
Businesses offering free basic services use this skill to build paywalls that promote premium tiers with free trials or guarantees. It targets conversion improvement by highlighting benefits and simplifying plan choices.
💬 Integration Tip
Start by implementing an onboarding paywall as per the skill's rule, using remote config for A/B testing to avoid deployment delays.
Full Windows desktop control. Mouse, keyboard, screenshots - interact with any Windows application like a human.
Control Android devices via ADB with support for UI layout analysis (uiautomator) and visual feedback (screencap). Use when you need to interact with Android apps, perform UI automation, take screenshots, or run complex ADB command sequences.
Build, test, and ship iOS apps with Swift, Xcode, and App Store best practices.
Control macOS GUI apps visually — take screenshots, click, scroll, type. Use when the user asks to interact with any Mac desktop application's graphical interface.
Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.
Write safe Swift code avoiding memory leaks, optional traps, and concurrency bugs.