paywall

Generate Apple-compliant paywall UIs for subscriptions and credit packs with RevenueCat.

32|10|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/moasq/nanowave --skill paywall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paywall
Source: https://github.com/moasq/nanowave/tree/main/internal/orchestration/skills/features/paywall
Command: npx skills add https://github.com/moasq/nanowave --skill paywall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized and Apple-compliant way to build custom user interfaces for subscription paywalls and credit pack purchases, ensuring adherence to App Store guidelines and a smooth user experience.

Core Features & Use Cases

  • Customizable UI: Design paywalls that match your app's unique design system, avoiding generic templates.
  • Apple Compliance: Strictly follows Apple's latest guidelines (post-Jan 2026) regarding disclosures, pricing, and UI elements.
  • Dynamic Pricing: Integrates with RevenueCat to display accurate, localized pricing and plan information.
  • Use Case: When developing a new feature that requires a subscription, use this Skill to quickly implement a compliant and visually appealing paywall that guides users through the purchase process.

Quick Start

Use the paywall skill to build a subscription paywall with monthly and annual plans.

Frequently Asked Questions about paywall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a subscription paywall that complies with Apple App Store guidelines?

To generate a compliant subscription paywall, implement specific UI patterns like fullScreenCover presentation and tappable plan cards. This ensures strict adherence to App Store guidelines regarding mandatory disclosures and dynamic pricing.

How do I display localized in-app purchase prices dynamically using RevenueCat?

Displaying localized in-app purchase prices dynamically requires RevenueCat integration within your paywall UI. This fetches accurate, localized subscription and credit pack pricing information dynamically.

Can I build custom UI for credit pack purchases instead of generic subscription templates?

Yes, you can build custom UI for credit pack purchases instead of using generic templates. This supports credit-based monetization models while allowing the paywall to match your app's unique design system.

What are the App Store UI requirements for subscription paywalls post-January 2026?

App Store requirements for subscription paywalls post-January 2026 mandate strict disclosures, dynamic pricing, and specific UI patterns. These include presenting via fullScreenCover and using tappable plan cards to ensure compliance.

Does this paywall approach work for both subscription and credit-based monetization models?

Yes, this paywall generation approach works for both subscription and credit-based monetization models. It supports creating custom user interfaces for both standard subscriptions and credit pack purchases.

Why does my custom subscription paywall risk App Store rejection?

Your custom subscription paywall risks App Store rejection if it lacks mandatory disclosures, dynamic pricing, or required UI patterns like fullScreenCover. Strictly following Apple's latest guidelines prevents these compliance failures.