> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryhelium.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Helium is a paywall platform for mobile apps. Paywalls, workflows, triggers, targeting and experiments are configured in the dashboard (https://app.tryhelium.com); the SDK's job is to initialize, present a paywall for a trigger, and report purchases.
> Pick the SDK page for the user's platform: /sdk/quickstart-ios (Swift), /sdk/quickstart-android (Kotlin), /sdk/quickstart-react-native, /sdk/quickstart-flutter. Method names differ per platform; copy them from the page for that platform, never from another platform's page.
> Pages under /sdk/quickstart-ios-v3 and /sdk/quickstart-android-v0 are legacy SDK versions. Use them only when the user is on that version; for upgrades use the /migrations pages.
> For live dashboard data (paywalls, workflows, metrics) connect the Helium MCP server at https://app.tryhelium.com/api/mcp (see /ai-tools/mcp). For SQL over events, revenue, subscriptions and users use the Data Access API (/data-access/overview) and the helium-data-access skill (/data-access/agent-skill). This documentation site also exposes a docs-search MCP server at https://docs.tryhelium.com/mcp.
> Web checkout (App2Web) with Stripe or Paddle is a separate flow from in-app purchases; start at /web-checkout/overview.
> Every page is available as Markdown by appending .md to its URL. The full index is at https://docs.tryhelium.com/llms.txt.

# Helium QA Guide

> A short checklist for testing your Helium paywalls before launch.

Use this checklist after your paywalls are built and before starting your rollout.

> [!NOTE]
>
> Complete QA for the normal in-app purchase path first. If you also use App2Web, approve the IAP path before testing the full App2Web flow.

## Check the dashboard

* [ ] Apps and products are synced for each platform, and product IDs match the stores.
* [ ] The intended products, default selection, and trial states are attached and published.
* [ ] Each workflow trigger, targeting rule, and fallback points to the intended paywall.
* [ ] Analytics and revenue integrations are receiving test events.

## Check the paywall

* [ ] Design, copy, products, and pricing match the approved experience.
* [ ] Purchase, close, restore, and second-tier actions work.
* [ ] Trial states, variables, user attributes, and custom actions work when used.
* [ ] Product selection and purchase use separate actions so a user cannot buy the wrong product.
* [ ] Check a few currencies, every supported language, a small phone, and dark mode when relevant.
* [ ] The paywall opens without visual flashes or broken animations.

## Test on device

* [ ] Use the intended TestFlight or Android build on a physical device for each platform.
* [ ] Open every launch-critical trigger and confirm the correct paywall appears.
* [ ] Complete a sandbox purchase and confirm the correct product is purchased and access unlocks.
* [ ] Confirm cancel and restore behavior work.
* [ ] Confirm the purchase and entitlement appear in your analytics or revenue system.
* [ ] Confirm a current fallback paywall appears when Helium configuration cannot load.

## Ready to launch

* [ ] The release build uses the correct Helium environment and API key.
* [ ] Open issues are documented and the final paywalls are approved.
* [ ] Start with a small group of users using the [Helium rollout guide](https://docs.tryhelium.com/guides/rolling-out-helium.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.