iOS Quickstart

Supported on: iOS SDK 1.0.61+

This guide walks you through configuring the AppDNA SDK, identifying users, and tracking your first event.

1. Configure the SDK

Initialize AppDNA as early as possible in your app lifecycle. For UIKit apps, place this in application(_:didFinishLaunchingWithOptions:). For SwiftUI apps, use the App initializer.

UIKit

import FirebaseCore
import AppDNASDK

@main
class AppDelegate: UIResponder, UIApplicationDelegate {
    func application(
        _ application: UIApplication,
        didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
    ) -> Bool {
        FirebaseApp.configure()

        AppDNA.registerBackgroundTasks()
        AppDNA.configure(
            apiKey: "adn_live_xxx",
            environment: .production,
            options: AppDNAOptions(logLevel: .debug)
        )
        return true
    }
}

SwiftUI

import SwiftUI
import FirebaseCore
import AppDNASDK

@main
struct MyApp: App {
    init() {
        FirebaseApp.configure()

        AppDNA.configure(
            apiKey: "adn_live_xxx",
            environment: .production,
            options: AppDNAOptions(logLevel: .debug)
        )
    }

    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

For background event uploads in SwiftUI apps, use @UIApplicationDelegateAdaptor and call AppDNA.registerBackgroundTasks() in didFinishLaunchingWithOptions.

If you don’t have your own Firebase: Keep FirebaseApp.configure() as shown above — it initializes AppDNA’s Firebase instance.If you already use Firebase (Analytics, Crashlytics, Realtime Database): Remove the FirebaseApp.configure() call entirely and just call AppDNA.configure(...). The SDK automatically picks up GoogleService-Info-AppDNA.plist and creates its own named Firebase instance. Your existing Firebase setup is not affected.

Call AppDNA.configure(...) exactly once before using any other SDK methods. Calling it multiple times will result in undefined behavior.

Configuration Options

The AppDNAOptions struct lets you customize SDK behavior:

Parameter	Type	Default	Description
`flushInterval`	`TimeInterval?`	`nil` (30 s)	Seconds between automatic event flushes. When not set, the server’s value from the bootstrap request applies once the bootstrap succeeds, if it is positive
`batchSize`	`Int?`	`nil`	A cap on the batch size the network sets (100 on Wi-Fi or wired; on cellular, 20 when the system marks the connection expensive (iOS: every cellular connection) or metered (Android: most plans), otherwise 50): the queue is flushed when it reaches the smaller of the two, and each upload sends at most that many. When not set, the value the server returns with the SDK’s bootstrap request is the cap if it is positive (100 today, so nothing is capped). A value below 1 is ignored (the SDK logs a warning), as if not set. Passing the default (100) is the same as not setting it. If your app already passed `batchSize` to an earlier SDK version — where it had no effect — it is now a hard cap: each upload sends at most that many events. Remove it, or raise it, unless that is what you want.
`configTTL`	`TimeInterval?`	`nil` (3600 s)	Seconds before cached config is considered stale. When not set, the server’s value from the bootstrap request applies once the bootstrap succeeds, if it is positive
`logLevel`	`LogLevel`	`.warning`	Verbosity of SDK console logs
`billingProvider`	`BillingProvider`	`.storeKit2`	Who owns purchases — see Billing
`vetoTimeout`	`TimeInterval`	`5`	Bounds host hooks on the Flutter / React Native bridges. Sign-in actions wait at least 120 s and a `refresh` interaction `max(vetoTimeout, 8 s)` on the bridges. Unused by a native iOS host: its `onBeforeStepAdvance` is not timed out, `onBeforeStepRender` ends at 3 s and a `refresh` interaction at 8 s

Environment

The Environment enum controls which backend environment the SDK targets:

Value	Description
`.production`	Production API and configuration
`.sandbox`	Sandbox API for testing

Log Level

The LogLevel enum controls console log verbosity:

Value	Description
`.none`	No logging
`.error`	Errors only
`.warning`	Errors and warnings
`.info`	Errors, warnings, and info
`.debug`	All messages including debug

Use .debug during development to see all SDK activity. Switch to .warning or .none for production builds.

Billing Provider

The BillingProvider enum specifies which billing system owns purchases:

Value	Description
`.storeKit2`	AppDNA’s own billing through StoreKit 2 (default when omitted); the SDK finishes transactions
`.revenueCat`	RevenueCat is your purchase SDK; AppDNA never finishes transactions; SDK paywall taps call `onPaywallPurchaseFailed(errorType: "providerNotAvailable")` in every published CocoaPods / SPM build (RevenueCat is not linked into AppDNA itself; see when a provider counts as linked); purchases reach AppDNA via the RevenueCat webhook
`.adapty(apiKey:)`	Adapty is your purchase SDK (with your Adapty API key); AppDNA never finishes transactions; as with `.revenueCat`, SDK paywall taps call `onPaywallPurchaseFailed(errorType: "providerNotAvailable")` in every published build
`.none`	Disable billing; purchase and restore throw `providerNotAvailable` (“No billing provider configured”)

See Billing for the full ownership table and the paywall recipe for .revenueCat / .adapty. Notification-proxy settings are Info.plist keys, not runtime options: AppDNADisableNotificationProxy and AppDNAForegroundPresentation — see Push → How push works on iOS.

2. Wait for Ready State

Use onReady to know when the SDK is ready — the bootstrap has succeeded or failed:

AppDNA.onReady {
    print("SDK ready")
}

onReady does not wait for the remote configuration. When it fires, the SDK serves the cached and bundled config, and the remote fetch may still be running (after a failed bootstrap it starts when a retry succeeds). Use remoteConfig.onChanged to pick up the fetched values.

3. Identify Users

Once a user signs in, call identify to associate events with their user ID:

AppDNA.identify(
    userId: "user-123",
    traits: [
        "plan": "premium",
        "signup_date": "2025-01-15"
    ]
)

Traits are merged with any previously set traits. You do not need to pass all traits on every call — only the ones that have changed.

4. Track Events

Track user actions with track:

AppDNA.track(
    event: "workout_completed",
    properties: [
        "duration": 45,
        "type": "strength"
    ]
)

Events are batched and flushed automatically: every flushInterval seconds, when the app goes to the background or returns to the foreground, and when the queue reaches a batch size set by the network (100 events on Wi-Fi or a wired connection, metered or not; 20 on a cellular connection the system marks as expensive (iOS) or metered (Android), which is every cellular connection on iOS and most cellular plans on Android; 50 on any other cellular connection). The batchSize option caps it: with a cap, the queue is flushed at the smaller of the two, and no upload sends more.

5. Flush Events Manually

Force an immediate flush of all queued events:

AppDNA.flush()

This is useful before the app enters the background or when you need to ensure events are sent immediately. Control whether the SDK collects and sends analytics data:

AppDNA.setConsent(analytics: true)

When analytics is set to false, events are silently dropped and not queued. No data is sent to AppDNA servers until consent is granted.

7. Remote Config and Feature Flags

Retrieve server-side configuration values:

let welcomeMessage = AppDNA.getRemoteConfig(key: "welcome_message")

Check whether a feature flag is enabled:

let darkModeEnabled = AppDNA.isFeatureEnabled(flag: "dark_mode")

8. Experiments

Get the variant assigned to a user for an experiment:

let variant = AppDNA.getExperimentVariant(experimentId: "paywall_test")

Check if the user is in a specific variant:

let isInVariantB = AppDNA.isInVariant(
    experimentId: "paywall_test",
    variantId: "b"
)

9. Session Data

Store cross-module session data that can be used in template interpolation across onboarding flows, paywalls, and in-app messages:

// Store session data
AppDNA.setSessionData(key: "selected_plan", value: "premium")
AppDNA.setSessionData(key: "referral_code", value: "FRIEND2026")

// Retrieve session data
let plan = AppDNA.getSessionData(key: "selected_plan") // "premium"

// Clear the values set with setSessionData (reset() clears onboarding answers too)
AppDNA.clearSessionData()

Session data values are accessible in Console-configured content using template syntax: {{session.selected_plan}}.

10. Reset on Logout

When a user signs out, call reset to clear the user identity and flush any remaining events:

AppDNA.reset()

This clears the identified user, generates a new anonymous ID, and flushes queued events.

You now have the SDK configured, user identification, event tracking, remote config, experiments, and session data working. Continue to the module-specific guides for Push Notifications, Billing, Onboarding, and Paywalls.

​1. Configure the SDK

​UIKit

​SwiftUI

​Configuration Options

​Environment

​Log Level

​Billing Provider

​2. Wait for Ready State

​3. Identify Users

​4. Track Events

​5. Flush Events Manually

​6. Set User Consent

​7. Remote Config and Feature Flags

​8. Experiments

​9. Session Data

​10. Reset on Logout

1. Configure the SDK

UIKit

SwiftUI

Configuration Options

Environment

Log Level

Billing Provider

2. Wait for Ready State

3. Identify Users

4. Track Events

5. Flush Events Manually

6. Set User Consent

7. Remote Config and Feature Flags

8. Experiments

9. Session Data

10. Reset on Logout