# Superwall: Subscription Infrastructure for iOS, Android, and Web

Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue.

## Pricing

- **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge.
- **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed.

Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0.

## Scale

$1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow.

## Infrastructure capabilities

- **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN
- **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows
- **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe
- **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan

Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation.

## Migration

Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code).

## Paywall product (optional, separately billable)

One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release.

## Architecture

Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost.

## Docs

* Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
* Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
* Webhooks: https://superwall.com/docs/integrations/webhooks
* Pricing: https://superwall.com/pricing

# Input

Capture typed responses from users with the input element for names, emails, feedback, and more.

The input element lets users type a response directly into your paywall or flow. Use it to capture names, email addresses, feedback, or any custom text input.

### Adding an input element

To add an input element:

1. In the left sidebar, click **+** to add a new element.
2. Choose **Input** under the "Onboarding" header.

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/component_add_input.jpg)

### Placeholder text

Set placeholder text to give users a hint about what to enter. The placeholder appears inside the input field before the user starts typing.

Try to make the placeholder text contextual to the type of input you expect:

* "Enter your name"
* "[you@example.com](mailto\:you@example.com)"
* "Tell us what you think"

### Keyboard type

Choose the appropriate keyboard type to make input easier for users:

* **Text:** Standard text keyboard. This is the default.
* **Email:** Keyboard optimized for email addresses (includes @ and . keys).
* **Number:** Numeric keypad for number-only input.
* **Telephone:** Phone number keypad.
* **URL:** Keyboard optimized for entering URLs.
* **Password:** Text keyboard with secure text entry enabled.
* **Search:** Text keyboard with a search-style return key.

Selecting the right keyboard type improves the user experience and reduces input errors.

### Using responses

The text users enter can be stored as a user attribute, used as a variable, dynamic values, and more. Any multiple choice item is available as a variable. You can view variables either from the left side [variables](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables) menu, or via the floating toolbar. Either case, it's exposed via **Element -> Input**.

![](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/comps_input_vars.jpg)

This is useful for:

* **Personalization:** Use the user's name on later pages (e.g., "Welcome, Sarah!").
* **Email capture:** Collect email addresses during onboarding for follow-up.
* **Feedback collection:** Gather open-ended responses for product insights.
* **Backend integration:** Pass the value to your backend via webhooks or the SDK.

### Using input values in dynamic content

After a user enters text, you can reference it elsewhere using dynamic values. For example, if you store the input under the key `user_name`, you can display it on the next page with a personalized greeting.

> **Tip:** Input elements work well paired with a "Continue" button that has a Navigate Page action. The user enters their response, then taps to proceed.