Concepts
The main concepts used in Nuxie and how they fit together.
Suppose people sign up for your running app but leave before their first workout. You can ask Nuxie to investigate, create shorter onboarding, publish it, and measure whether more people start a workout. These are the parts of Nuxie you’ll use along the way.
Workspace and App
A Workspace contains your team, Tasks, Projects, connected accounts, and Apps.
An App represents an application you ship. Its customers, events, Products, and Experiences belong to that App. Test and live environments keep development activity separate from real customers. Your SDK key selects the App, platform, and environment.
Customers
A Customer is someone using your app. They can use it anonymously before signing in. When they sign in, your SDK identifies them with your app’s account ID so activity and access can follow the same person. Customers are separate from the team members in your Nuxie workspace.
Task
A Task is a conversation with Nuxie about a piece of work. It can produce an investigation, a recommendation, a new Experience, or a change to an existing one.
Start a Task directly or from a Report, which presents findings and recommendations. For the running app, you might start with “Why are new users leaving before their first workout?” and then ask Nuxie to improve the onboarding. The Task keeps that investigation, your feedback, and the resulting work together.
When work needs approval, Nuxie presents a Proposal for you to review. An Automation starts Tasks on a schedule or when a connected service sends an event, so you can repeat useful work such as a weekly onboarding review.
Project
A Project contains the editable screens, content, styles, data, and interactions used to create Experiences. You and Nuxie work on the same Project. Changes stay in the draft until you publish them.
Screen and Flow
A Screen is a view in your Experience, such as a welcome message, question, or plan selector.
The flow defines how screens connect and what their actions do. A button can open another screen, submit an answer, start a purchase, or close the Experience. Work with Nuxie to change these paths, then try them in Preview.
Experience
An Experience is the interaction delivered to your app. It combines published content with a trigger, audience, and delivery rules. Onboarding, paywalls, and surveys are all Experiences.
Edit its source Project to change its content. See Creating a Project.
Version and release
A Version captures the Experience as it was when you published it. Your app receives that version while you continue editing the draft. You can try an update on your device before making it available to production users. See Versions and updates.
Event, trigger, and goal
- An Event records something that happened, such as
signup_completedorworkout_started. - A trigger defines when an Experience starts, such as an app event or a customer entering a Segment.
- A goal measures an outcome, such as starting a workout within seven days of entering onboarding.
Goals are optional. Completing an Experience and achieving its goal are tracked separately. See Events and triggers.
Journey and response
A Journey is one customer’s run through an Experience. It records the version, progress, and outcome.
Responses are the answers collected during that run, such as a training goal or product preference. View them alongside the customer’s Journey history.
Segment and Experiment
A Segment is an audience defined by conditions, such as customers who completed setup but haven’t subscribed. Use it for targeting and analysis.
An Experiment compares paths within an Experience. Customers are assigned to variants, and results measure outcomes for those who reach the Experiment action.
Product, Feature, and Entitlement
A Product is something a customer buys. A Feature is a capability or allowance in your app. A Product Grant defines which Features the Product includes; an Entitlement is the access the customer receives.
For example, monthly and annual Products can both grant the premium-access Feature. Your app checks that Feature to decide whether to open a premium workout, regardless of which Product the customer bought. See Features and entitlements.
The complete path
For the running app, the Task produces a Project with shorter onboarding. Publishing makes the Experience available when your app sends signup_completed. Each eligible customer starts a Journey, answers the onboarding questions, and returns to the app. The workout_started event then tells you whether the change helped them reach the outcome you wanted.