AppActor is the purchase infrastructure layer between your mobile app, the app stores, and your own product access rules. There are two practical ways to use it.

​
1. Subscription Management Mode

Use the AppActor SDKs to fetch offerings, make purchases, restore access, and read customer entitlements. In this mode AppActor validates purchases, stores customer access state, and gives your app a single customer info contract across iOS, Android, Flutter, and React Native. Use this mode when:
  • your app wants AppActor to be the purchase source of truth
  • you need cross-platform entitlement status
  • you want restore, sync, and receipt retry behavior handled consistently

​
2. SDK Infrastructure Mode

Use AppActor for SDK-side product infrastructure such as customer attributes, attribution identifiers, Remote Config, Experiments, and cached/offline state while keeping selected product decisions in your own app layer. Use this mode when:
  • you already have product-specific backend logic
  • your app needs Remote Config near the purchase flow
  • your app needs Experiment assignment for paywall or onboarding variants
  • you want AppActor SDK telemetry and customer context without handing every product rule to the client
Subscription Management Mode includes the SDK infrastructure surfaces. Most new AppActor integrations should start there.

​
The runtime loop

  1. Your dashboard catalog defines products, entitlements, offerings, and package slots.
  2. The app configures the SDK with a public pk_... key and optional appUserId.
  3. The SDK fetches offerings and your app renders a paywall.
  4. The SDK starts a store purchase for the selected package.
  5. AppActor validates receipts and refreshes customer entitlements.
  6. Your app gates premium access from customer info.