iOS Bridge and Plugin - AppActor

Most native iOS apps should use the native AppActor API directly. Bridge and plugin surfaces exist for wrapper authors and hybrid integration layers.

Bridge surfaces

Use bridge-style surfaces only when you are building interoperability code:

AppActorBridge for callback-oriented bridging
AppActorPlugin for plugin-style request routing

Those surfaces mirror the same purchase, offerings, customer, attribute, Remote Config, and experiment primitives. They do not define a separate product contract.

Native app recommendation

If you are building a Swift or SwiftUI app, prefer:

await AppActor.configure(apiKey: "pk_YOUR_PUBLIC_APP_KEY")
let offerings = try await AppActor.shared.offerings()

If you are writing Flutter or React Native app code, stay on the wrapper package instead of calling the bridge directly.