Quickstart

Create, publish, and verify your first Nuxie Experience on iOS

This guide follows the launch path end to end: ask Nuxie to create an Experience, review it, publish it, connect the iOS SDK, and prove that the published Experience was shown.

Before you begin

You need:

A Nuxie workspace and an iOS app in the dashboard.
An Xcode project targeting iOS 15 or later.
A real moment in the app where the Experience should appear.

You do not need to configure Products for a non-purchase Experience. If the Experience includes purchase or restore actions, create or import the Products first and choose who owns checkout. See Purchases.

1. Start a Task

From Home, choose New Task. Describe the user, moment, outcome, and important constraints. For example:

Design an annual-first paywall for free users who reach the export limit. Use one primary upgrade action, explain what unlocks immediately, and make successful purchase the goal.

Nuxie creates or updates a Project inside the Task. Continue the conversation if the result needs a different direction.

2. Review the Project

When the Editor appears beside the Task, check the work in each relevant mode:

Design — inspect the screens, hierarchy, text, layout, imagery, and styling.
Flow — confirm the starting point, navigation, trigger, Goal action, and branches.
Preview — run the Experience and exercise every path a user can take.
Data — inspect response collections when the Experience gathers input.

Publishing requires a starting point and at least one named Goal action. Fix any broken bindings, parse failures, or unsupported platform actions shown by the publish review.

3. Publish the Experience

Choose Publish in the Editor. The review shows the target app, trigger, audience, delivery changes, and any experiment changes.

For a first publish, choose the intended target and confirm Publish. Nuxie creates a versioned release and builds it for delivery. Wait for Published before continuing.

If an update fails to build, the current live version stays live.

4. Connect the iOS app

After publish, choose View in your app or open the app’s Connect your app surface.

The fastest path is Agent install: copy the generated task into the coding agent that has access to your iOS repository. It includes the two publishable keys, exact trigger event, Experience name, and verification contract.

For manual installation:

Add https://github.com/nuxieai/nuxie-ios with Swift Package Manager.
Add the Nuxie product to the app target.
Put the test key in debug builds and the live key in release builds.
Configure Nuxie once at app launch.

import Nuxie

let configuration = NuxieConfiguration(apiKey: apiKey)
try NuxieSDK.shared.setup(with: configuration)

Do not silently discard setup errors while verifying the integration. The complete, agent-readable setup is in Integrate Nuxie with iOS.

5. Fire the published trigger

Place the exact event from Connect your app at the real domain entry point:

NuxieSDK.shared.trigger("export_limit_reached")

Do not rename or prefix the copied event. A paywall triggered when the export limit is reached belongs at that limit decision, not unconditionally at app launch.

6. Verify the real result

Run a debug build on a device or simulator.

Reach the code path that calls setup(with:).
Confirm the dashboard changes from Waiting for your app… to Connected.
Fire the trigger.
Confirm the Experience appears.
Confirm the dashboard changes to Shown.

Connected proves the app reached Nuxie with the selected key. Shown proves one of the versions from this publish was actually presented. Both are part of the completion contract.

If verification stops

Not Connected: check the selected build configuration, key value, network access, and setup error.
Connected but not Shown: check exact trigger spelling, verify the event fires after setup, and confirm the Experience is live for the same app and environment.
Publish blocked: resolve every item under Before you publish; the server may also return a more specific preflight failure.
Experience rejected by the SDK: use SDK logs to inspect release authentication or acquisition failure. The SDK will not render an unauthenticated or incomplete release.