AppActor helps mobile teams build and operate in-app purchases without scattering subscription logic across app clients, backend jobs, and support playbooks. Use AppActor when you want the app to stay focused on product UX while purchase validation, entitlement state, catalog structure, and recovery behavior stay consistent across platforms.

​
Core product areas

  • subscription and in-app purchase management
  • customer entitlements and access state
  • server-defined offerings and package slots
  • Remote Config for server-driven app behavior
  • Experiments for controlled assignment and measured variants
  • attribution, integration IDs, Apple Ads, and Install Referrer helpers
  • SDK diagnostics, cache behavior, and recovery paths

​
Start here

  1. Read How AppActor Works.
  2. Create the project and platform apps in Project and Store Setup.
  3. Create the catalog in Catalog Setup.
  4. Wire the app with Quickstart.
  5. Before launch, connect Server Notifications and Outbound Webhooks if your backend needs async lifecycle events.
  6. Add Remote Config, Experiments, Apple Ads, or Attribution only where your product needs them.
  7. Validate release behavior with Testing and Go Live.

​
Product boundary

AppActor does not render a hosted paywall for you. Your app fetches offerings, renders its own UI, starts the purchase, and then gates access from AppActor customer entitlements.