Steplark

configure(autoPresent:) controls whether the SDK shows itself.

Auto (default) (autoPresent: true). The SDK auto-shows on launch, no host code beyond configure(), snapping the overlay into place before your first frame paints.

Manual (autoPresent: false). The SDK still pre-fetches and pre-warms at configure() time, but waits for you:

Steplark.configure(apiKey: "sl_...", placement: "paywall_main", autoPresent: false)

// later, on a tap
Button("Upgrade") { Steplark.present() }

Manual present slides up with UIKit's native modal animation and slides down on dismiss. A per-call completion overrides the configure-time closure for that call only:

Steplark.present(onOnboardingComplete: { /* ... */ })

onPurchaseComplete fires on all three of these, so you wire entitlement gating in one place. Telemetry is split by event name so revenue analytics stay clean while engagement signals are still captured:

Screens can trigger host work the SDK doesn't ship: permissions, opening URLs, recording a choice.

Screen JS:

Steplark.action("request_notification_permission")
Steplark.action("set_goal", "lose_weight")

Host: handle via onAction: (or the delegate's steplarkDidReceiveAction(name:value:)):

Steplark.configure(
  apiKey: "sl_...",
  placement: "onboarding",
  onAction: { name, value in
    switch name {
    case "request_notification_permission":
      UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .badge, .sound]) { _, _ in }
    case "set_goal":
      UserDefaults.standard.set(value, forKey: "user_goal")
    default:
      break
    }
  }
)

value is nil when the screen called Steplark.action(name) with no second argument.

Steplark.dismiss()

Host-side only, not exposed to screen JS. Most commonly called from inside onPurchaseComplete after flipping your entitlement flag. The overlay animates out using the same path as a natural completion. dismiss() does not fire onOnboardingComplete, the complete telemetry event, or steplarkDidCompleteOnboarding.

If the user kills the app mid-onboarding, the SDK resumes them on the screen they were on at next launch, with no host code needed. The saved position is wiped on completion, on reset(), and after seven days of inactivity. If the flow was edited and the saved screen no longer exists, the SDK clamps to the most recent visited screen still present; if none survive, it starts fresh.

Steplark.identify(userId: "user_123")  // your stable user id
Steplark.reset()                        // clear on sign-out

Anonymous events are joined into the identified user the moment identify is called. reset() wipes local user state and starts a fresh anonymous session.

For observability beyond the configure() closures:

@MainActor
final class MyObserver: SteplarkDelegate {
  func steplarkDidCompleteOnboarding(flowId: String, durationMs: Int) {}
  func steplarkDidCompletePurchase(productId: String, transactionId: String) {}
  func steplarkDidAbandonPurchase(productId: String) {}
  func steplarkDidReceiveAction(name: String, value: String?) {}
  func steplarkDidFail(error: SteplarkError) {}
}

Steplark.shared.delegate = MyObserver()

Every method has a default no-op, so implement only what you need. The delegate fires alongside the configure-time closures, not instead of them.

SteplarkError is what steplarkDidFail(error:) hands you:

The user-visible recovery is a "Tap to retry" UI inside the same WebView; the SDK never auto-dismisses on error. The delegate fires for observability.