Editor

Review and refine the Experience Nuxie creates with Design, Flow, Preview, and Data

The Editor is the shared visual workspace where you and Nuxie create an Experience. It appears beside the Task once the Task has Project work to show.

The Editor is not a separate handoff from the agent. Your conversation and Project stay connected: ask Nuxie for a change, watch it update the artifact, then inspect or adjust the result directly.

The four modes

Use the mode switcher at the top of the Editor to change how you look at the same Project.

Design

Design is the visual authoring canvas. Arrange screens, select frames and components, edit text and visual properties, work with assets, and inspect the component hierarchy.

Use Design to answer: Does this look and feel right for our app?

Flow

Flow shows how the Experience behaves. Connect screens, inspect routes, configure triggers and actions, choose the starting point, and place Goal actions on the paths that confirm success.

Use Flow to answer: Will the right user see the right thing, and can every path finish correctly?

Preview

Preview runs the authored Experience inside the Editor. Interact with it as a user, follow branches, test navigation and purchase sheets, and inspect the current live-run state.

Preview uses the Project’s current draft. It is a validation surface, not proof that a published release reached your app.

Use Preview to answer: Does the complete Experience behave correctly before I publish?

Data

Data contains the response schemas and collections used when an Experience gathers structured input. Use it for surveys, quizzes, onboarding answers, and other response-driven Experiences.

Use Data to answer: What information does this Experience collect, and how is it shaped?

A practical review loop

Ask Nuxie to create or change the Experience in the Task.
Inspect the result in Design.
Check its routes, starting point, trigger, and Goal in Flow.
Exercise every meaningful path in Preview.
Review the exact target and changes in Publish.

You can move between conversation and direct editing at any point. Use chat for intent-level changes and the Editor for precise inspection or adjustment.

Projects and published Versions

The Editor changes the Project, which remains editable. Publishing creates an immutable Version for an Experience.

Editing the Project never changes the live Experience by itself. A new Version reaches users only after you review and approve Publish and its build succeeds.