Glossary
Offerings
Offerings are the server-defined catalog objects your app fetches before presenting purchase choices. Depending on platform, the public models expose:- a current offering
- all offerings
- packages inside each offering
- package metadata such as identifiers and pricing context
- product-entitlement relationships that help explain access after purchase
Packages
Packages are the objects you actually purchase. Common patterns include:- monthly or annual subscription packages
- upgrade or downgrade flows that reference an old purchase token or replacement mode
- placements that tell AppActor where the package was shown in your product
monthly, annual, or lifetime only populate when those package slots exist in the offering configuration.
Access decisions
Use customer info and entitlements to gate access. A typical question is:
Does the customer currently have the premium entitlement?
That answer should come from SDK-backed customer state, not from which button the user tapped most recently.
Fallback and cached behavior
Some SDKs expose cached getters, fallback offerings, offline entitlement keys, or anisComputedOffline signal. Those are valuable for resilience, but they also mean your docs should explain:
- when a screen may show cached catalog data
- when access can still be decided offline
- when you should force a fresh fetch or recovery path
What is not included
These repos do not expose a hosted visual paywall renderer. If you want a polished paywall experience, your app should:- fetch offerings
- map packages to UI cards
- call the purchase API for the chosen package
- refresh customer info and gate access
Displaying Products
Map packages to price cards, badges, descriptions, empty states, and CTA handlers.
Trusted Entitlements
Combine active entitlement checks with verification state for sensitive access.