# 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

# Flow Elements

Add interactive elements to your flows: multiple choice, text entry, progress indicators, and date pickers.

Flows can be enhanced with interactive components designed for multi-page experiences. They capture user input, show progress, or request permissions. Use them to personalize the flow or gather information for branching.

## Multiple Choice

The multiple choice element presents options for users to select. This is the key element for enabling branching. User selections can determine which page they see next.

![A multiple choice element in a flow](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_mc_example.jpg)

### Configuration

* **Single-select or multi-select:** Choose whether users can pick one option or multiple.
* **Randomize order:** Shuffle the options each time (useful for surveys to reduce bias).
* **Choice items:** Each choice has a label and a value.

### Labels and values

Each choice has two parts:

* **Label:** What users see (e.g., "Grow subscriptions").
* **Value:** What gets stored (e.g., `goal_grow`).

The value is used internally for routing conditions and user attributes. Keep values short and consistent (lowercase, underscores).

![Labels and values for multiple choice items](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_mc_items_example.jpg)

### Storing selections

When a user makes a selection, two variables are available: `selectedValue` (the internal value, e.g., `goal_grow`) and `selectedLabel` (the display text, e.g., "Grow subscriptions"). If localization is active, `selectedLabel` returns the translated label for the user's locale.

You can use these in routing conditions to branch the flow, store them as user attributes for analytics or personalization, reference them in dynamic content on later pages, or pass them to your backend via webhooks.

> **Tip:** Multiple choice controls are commonly used for [branching](/docs/dashboard/dashboard-creating-flows/linking-pages).

## Input

The input element lets users type a response, like their name, email, or feedback.

![An input element in a flow](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_input_example.jpg)

### Configuration

* **Placeholder text:** The hint shown before users type.
* **Keyboard type:** Choose the appropriate keyboard (default, email, number, etc.).

### Storing responses

Like multiple choice, text entry values can be stored as user attributes. This is useful for personalizing later pages with the user's name, capturing email addresses for follow-up, or collecting feedback or custom responses.

## Indicator

The indicator element shows progress through the flow, like "Step 2 of 5."

![An indicator element in a flow](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_indicator_example.jpg)

### Configuration

* **Style:** Choose from different visual styles (dots, bars, numbers).
* **Current step:** Which step to highlight.
* **Total steps:** How many steps to show.

Add an indicator when your flow has more than 3-4 pages. Users are more likely to complete a flow when they can see their progress and know how much is left. You can also use their properties in dynamic values such as progression:

![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_elements_element_vars.jpg)

## Date Picker

The date picker element lets users select a date, time, or both using a scrollable wheel or compact input. This is useful for collecting birthdates, scheduling preferences, or any date-related input during onboarding.

![A date picker element in a flow](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/flows_datepicker_example.jpg)

### Configuration

* **Style:** Choose between **Wheel** (scrollable columns) or **Compact** (native date/time input).
* **Components:** Choose what to collect.
  * Wheel style supports **Date & Time**, **Date**, **Time**, and **Time List** (a single scrolling column with pre-formatted time options).
  * Compact style supports **Date** and **Time**.
* **Min Date / Max Date:** Constrain the selectable range. Options are **No Limit**, **Today**, **Relative** (e.g., 30 days before or 1 year after today), or a **Fixed Date**.
* **Minute Interval:** When using a time component with the wheel style, set the interval between selectable minutes (1, 5, 10, 15, 30, or 60).

### Storing selections

The selected value is stored as a string and accessible as a variable. The format depends on what components are configured: `YYYY-MM-DD` for date, `HH:MM:SS` for time, or `YYYY-MM-DDTHH:MM:SS` for date and time. You can use this value in routing conditions, dynamic content on later pages, or pass it to your backend.