The wandkit iOS SDK

The calls you will actually write

This is every call most apps ever make. There is no builder, no nested namespaces, no WandKit delegate to implement. The rest of the surface is push permission helpers and the referral calls.

import WandKit

WandKit.configure(apiKey: "wk_...")
WandKit.identify("user_123", displayName: "Jane Appleseed")
WandKit.event("checkout_completed", properties: ["plan": "pro"])
WandKit.presentFeedback()
WandKit.registerDeviceToken(deviceToken)
WandKit.logout()

iOS 15+ Swift Package Manager No runtime dependencies Private beta

1. Add the package

In Xcode, use File, then Add Package Dependencies, and paste the repository URL. Or declare it yourself.

// Package.swift
dependencies: [
    .package(url: "https://github.com/FlabbergastAgency/wandkit-ios", from: "0.1.0")
]

// then add the product to your target
.product(name: "WandKit", package: "wandkit-ios")

2. Configure

Call this once at app startup, before any other WandKit function. The API key is the wk_ key from your project settings.

import WandKit

WandKit.configure(apiKey: "wk_...")

// with a theme for the native survey cards
WandKit.configure(apiKey: "wk_...", theme: .default)

3. Identify the user

Call this after sign-in, or whenever the user becomes known. The display name is a suggestion shown on their posts and comments until they set their own name in the feedback UI, and re-identifying never overwrites a name they chose themselves.

WandKit.identify("user_123")
WandKit.identify("user_123", displayName: "Jane Appleseed")

// on sign-out, so the device stops receiving their notifications
WandKit.logout()

4. Send an event

The event goes to wandkit and, if a survey is configured for that event name, the form is presented automatically. Nothing else to wire up.

WandKit.event("checkout_completed")

WandKit.event(
    "onboarding_finished",
    properties: [
        "plan": "pro",
        "source": "paywall"
    ]
)

5. Open the feedback board

The SDK finds the top-most view controller of the active scene itself, so from SwiftUI or UIKit alike this is one line. Pass from: only when you need to anchor to a specific controller.

WandKit.presentFeedback()

// or take the controller and present it your own way
let feedback = WandKit.feedbackViewController()
navigationController.pushViewController(feedback, animated: true)

6. Forward the push token

Optional, and only if you want notifications. wandkit does not swizzle your app delegate. Hand it the token iOS gives you and it does the rest.

final class AppDelegate: NSObject, UIApplicationDelegate {
    func application(
        _ application: UIApplication,
        didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data
    ) {
        WandKit.registerDeviceToken(deviceToken)
    }
}

In SwiftUI, wire it up with @UIApplicationDelegateAdaptor. Your target also needs the Push Notifications capability, which creates the aps-environment entitlement for you. You never tell the SDK which environment you are in: it reads the value Apple signed the build with and reports it at registration.

Forms as code

Bind a directory to a project once and your survey definitions become files you can diff. wandkit projects use writes the .wandkit.yml that pins the project id, so agents and CI need no flags.

# authenticate with a personal access token
export WANDKIT_TOKEN=wkp_...

# bind this repo to a project (writes .wandkit.yml)
wandkit projects use 

# pull, review, push
wandkit forms pull
wandkit forms diff forms/onboarding.json
wandkit forms validate forms/onboarding.json
wandkit forms push forms/onboarding.json

# confirm the integration is really sending
wandkit events tail
wandkit responses export --form 

Files land at forms/.json, one per form, identified by the form's own key rather than a project-specific id, so the same file pushes to staging and to production. Push replaces every editable field on the target form rather than merging it, so run diff first if someone may have edited that form in the dashboard since you pulled.