# 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

# Indicator

Show users their progress through a flow with the indicator element.

The indicator element displays progress through a multi-page flow, showing users where they are and how much remains. Adding an indicator reduces abandonment by setting clear expectations.

### Adding an indicator element

To add an indicator element:

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

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

### Configuration

The indicator has two main properties: **Current Item** and **Total Items**.

**Current Item** controls which step is highlighted as active. By default, this uses the indicator's own state (`"Indicator".currentIndex`), which automatically tracks the user's position in the flow.

**Total Items** determines how many steps the indicator displays. You can set this using one of three modes:

* **Number:** Enter a fixed number directly (e.g., `5` for a five-page flow). Use this when you know the exact number of steps ahead of time.
* **Child Count:** Select another element on the page, and the indicator will use that element's child count as the total. This is useful when the number of steps is determined by dynamic content, such as a stack of slides.
* **State:** Bind the total to a variable. This gives you full control over the count through your flow's state, and is useful when the total changes based on branching or other conditions.

### Dynamic progress

Any indicator 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 -> Indicator**.

You can bind the indicator to the actual flow progress using dynamic values. This way, the indicator automatically updates as users move through pages.

Use the indicator's properties in dynamic values to show progression:

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

### Placement

Common indicator placements:

* **Top of the page:** Shows progress at a glance as users enter each page.
* **Inside a navigation bar:** Integrates with back/forward controls.
* **Above the CTA:** Reminds users they are almost done before the final action.

> **Tip:** For shorter flows (2-3 pages), an indicator may be unnecessary. Use your judgment based on the content density and expected completion time.