# 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

# Slider

Let users choose a numeric value or scrub progress directly inside a paywall or flow.

The slider element lets users choose a numeric value by dragging a handle or using keyboard controls. Use it for goals, budgets, intensity controls, percentages, rating scales, and progress scrubbers inside paywalls or onboarding flows.

Use a slider when the user is choosing a number. Use [Navigation](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-navigation-component), [Slides](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-slides-component), or [Carousel](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-carousel-component) when the user is moving between screens.

### Adding a slider element

To add a slider element:

1. In the left sidebar, click **+** to add a new element.
2. Choose **Slider** in the **Flows** section.

![Slider element in the paywall editor add menu](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-slider-component.jpg)

If you do not see **Slider**, flow elements may not be enabled for your workspace yet.

Adding a slider creates a small element group:

* **Track:** The background stack behind the slider.
* **Slider:** The interactive filled progress layer. Select this element to edit range, orientation, step size, and fill styling.
* **Knob:** A stack inside the slider that visually marks the current value.

Keep these elements together unless you are intentionally rebuilding the control. The knob is a child of the slider, so it moves with the filled progress layer as the value changes.

### Configure the range

Select the **Slider** element to configure its value behavior:

* **Orientation:** Choose **Horizontal** or **Vertical**. Horizontal sliders fill from left to right. Vertical sliders fill from bottom to top.
* **Range:** Set the minimum and maximum allowed values.
* **Step Size:** Set the increment used while dragging or using keyboard controls. Use `1` for whole numbers, `0.1` or `0.01` for decimal values, and `0` only when you need a continuous slider.

![Slider range and step settings in the paywall editor](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-slider-properties.jpg)

> **Note:** The slider starts at its minimum value unless its value variable already has a current or initial value. If the configured range changes later, out-of-range values are clamped visually until the user interacts with the slider again.

### Use the slider value

Every slider exposes a **Value** variable. You can insert it from the left side [Variables](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-variables) menu or from the floating toolbar under **Element -> Slider**.

![Slider value variable in the paywall editor variable picker](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-slider-variables.jpg)

Use the slider value to:

* Show the selected value in text, such as a goal amount, discount percentage, or intensity level.
* Drive dynamic values that show, hide, or restyle elements based on a threshold.
* Branch a flow based on the value the user selected.
* Pass the value into the rest of your paywall workflow when you need to persist or act on the selection.

![Text component bound to a slider value as an example](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/paywall-editor-slider-variables-example.jpg)

> **Tip:** You can use a slider to build a "Customize your price" paywall. Map each slider step to a product, then use the slider value to update which product is selected under the paywall. This lets users drag between price points while the offer copy, displayed amount, and purchase button stay tied to the selected product.

![Customize your price paywall using a slider to choose between products](https://2a2314a4-superwall-docs.staffbar.workers.dev/docs/images/yuka-exmaple-slider.jpeg)

> **Note:** AI Chat and Editor MCP use the native `sw-slider` element for this control. The underlying value is exposed as `state:node.<id>.value`, but most editor workflows should insert the value from the variable picker instead of typing the state path manually.

### Style the track, fill, and knob

The default slider is built from separate visual pieces so you can style each part independently:

* Select **Track** to edit the background bar. This is where you usually set width, height, background color, radius, padding, and placement.
* Select **Slider** to edit the filled progress layer. The slider's background color styles the fill, not the track behind it.
* Select **Knob** to edit the draggable handle. You can change its size, radius, border, shadow, and color like any other stack.

For horizontal sliders, the fill expands from the left edge. For vertical sliders, the fill expands from the bottom edge. When you switch a slider to vertical orientation, give the track a clear height and reposition the knob so it aligns with the fill edge.

> **Tip:** Style the track for the inactive portion of the control, and style the slider element for the active filled portion. If the slider seems invisible at first, it may be at its minimum value, where the fill has zero width or height.

### Common patterns

Common slider patterns include:

* **Goal selector:** Let users choose a target, such as workouts per week, minutes per day, or a savings amount.
* **Intensity selector:** Let users choose a level, difficulty, or personalization value.
* **Percentage selector:** Let users choose a discount, completion amount, or progress value.
* **Progress scrubber:** Let users scrub through a simple before/after or step-based experience.

### Troubleshooting

**Slider does not appear:** Make sure the track has visible styling, the slider has a real width and height, and flow elements are enabled for your workspace.

**Only the knob appears:** The slider may be at its minimum value, where the filled portion is zero width or height. Drag the knob or set an initial value.

**The value changes in the wrong increments:** Select the slider and update **Step Size**.

**A vertical slider still looks horizontal:** Set **Orientation** to **Vertical**, then give the track a clear height and reposition the knob for the vertical fill direction.

**Styling the slider changed the fill instead of the track:** This is expected. Select **Track** to style the inactive background, and select **Slider** to style the active fill.