Experiences

Deliver screens to users with experiences

Experiences turn your Studio projects into live experiences delivered to your users. An experience is the container that holds published versions, controls when and to whom screens appear, and tracks how users interact with them.

What is an experience?

An experience connects three things:

• A trigger that decides when the experience activates (an event, a segment, or both)
• A goal that defines what success looks like (a purchase, a signup, or any custom event)
• One or more versions built from your Studio experience

When you publish a project in the Studio, Nuxie creates (or updates) an experience and builds a new version. That version is compiled into an optimized bundle and delivered from the edge to your users via the SDK.

Experience lifecycle

Every experience follows the same path from draft to live:

1. Author – Design your paywall or onboarding experience in the Studio.
2. Publish – Hit Publish. Nuxie creates an experience (if one does not exist for this experience), queues a build, and generates a new version.
3. Build – The build pipeline compiles your screens, styles, and logic into a bundle the SDK can render.
4. Live – On the first successful build, the experience is automatically promoted to live status and begins serving to users who match the trigger.

After the first publish, subsequent publishes create new versions under the same experience. You can switch between versions at any time from the Versions tab.

Experience status

An experience has two possible statuses that control delivery:

When an experience is live and has a built version, it is included in the configuration bundle synced from the server. Paused experiences are excluded from delivery entirely.

Tip: The first time you publish a project, the experience starts as paused and is automatically promoted to live once the build succeeds. After that, you control the status manually.

Auto-promotion

Nuxie automatically sets an experience to live when its first build completes successfully. This means publishing a brand-new project results in a live experience without any extra steps. For subsequent versions, the experience retains its current status.

Dashboard

Manage experiences from the dashboard under your app. The experience list shows:

• Name – The experience name (derived from your project or set manually).
• Status – Whether the experience has a published version or is still in draft.
• Trigger type – Event-based or segment-based, pulled from the active version.

Click any experience to open its detail view with four tabs:

• Overview – Trigger and goal configuration, conversion metrics, and a performance chart.
• Versions – Version history and build status. Activate any built version with one click.
• Experiments – A/B tests running within this experience.
• Journeys – A record of every user who entered the experience.

Experiences and the SDK

The SDK receives experience configurations as part of the user profile, delivered from the edge. When a user’s profile is fetched, Nuxie includes only the experiences that are live and have a successfully built version. The SDK evaluates triggers locally and presents the appropriate screens.

For details on integrating experiences in your app, see iOS SDK: Presenting Experiences.

Next steps

• Triggers & Goals – Configure when experiences appear and how conversions are tracked.
• Versions – Manage published versions and activate builds.
• Experiments – Run A/B tests to optimize your paywalls.