---
title: "Creating a Project"
description: "Build and update the Experiences your users see in your app."
search:
  tags: ["Features"]
  keywords: ["remote UI", "onboarding flow", "survey builder"]
---

A Project brings together everything you need to create an Experience: screens, content, styles, data, and interactions. You can use it to help someone get started, choose a plan, answer a survey, or take another step in your app. Work on the Project with Nuxie, then publish it when you're ready for users to see it.

<span id="create-with-nuxie" />

## Create a Project

Start a Task and tell Nuxie what you want the Experience to do. Include the people it's for and where they should end up. For example:

**Create onboarding for our running app. Ask about the user's goal and experience level, then show a plan summary. Include a skip path.**

> Create onboarding for our running app. Ask about the user's goal and experience level, then show a plan summary. Include a skip path.

Nuxie adds the Experience to the Task's outputs. Open it alongside the conversation to see the screens and the path between them. You can ask for changes in the conversation, edit the output directly, or move between the two as you work.

## Project contents

<span id="edit-the-project" />

The visual part of a Project is made from [screens and components](/docs/guides/screens-and-components). Use [shared styles](/docs/guides/styling-and-themes) to keep colors and typography consistent, and add [images and assets](/docs/guides/images-and-assets) from your app or generate them with Nuxie.

[Data and bindings](/docs/guides/data-and-bindings) let the screens respond to user input. A goal selected on one screen can appear in a summary on the next. [Interactions and flows](/docs/guides/screens-and-interactions) connect those screens and decide what happens when someone continues, skips a question, or makes a purchase.

### Canvas, Code, and Responses

**Canvas** is where you work on the screens and their connections. Select a screen or layer to see its properties. **Design** contains layout and appearance settings; **Animate** opens timelines and state machines for the selected screen or reusable component.

**Code** contains variable collections and their values. **Responses** contains the collections of answers your Experience collects, along with their fields. All three views stay within the Task, so you can keep the conversation open while editing. Individual screens can also open as outputs when you want to focus on one screen.

## Preview

Choose **Preview** to use the Experience as a user would: enter answers, follow branches, and try a simulated purchase. **Stop preview** returns you to editing.

You can also run it with different customer personas or restart from an earlier screen. See [Preview](/docs/guides/preview) for those controls and the Run Log.

<span id="deliver-the-experience" />

## Publish

[Publishing](/docs/guides/publishing) turns the Project into a version your integrated app can display. Its [delivery rules](/docs/guides/delivery) determine which users receive it and when.

You can keep editing the Project after publishing. Those changes stay in the draft until you publish again, so replacing an image or rewriting a headline doesn't immediately change what users see. Learn more about [Versions and updates](/docs/guides/versions-and-updates).