# Create a blank app

Start from scratch when no prepared starter fits the experience you want to give users. A definition-based app begins with a layout you author in the builder. It can combine input controls, tables, document views, status, and workflow-driven interactions.

## Create the starting app

1. Open **Apps**, then **New App**.
2. Expand **Advanced — build from scratch**.
3. Choose the available definition-based runtime template.
4. Enter the app's **Name**, **App id**, and optional **Description**.
5. Submit the form. Strive opens the new app in the builder.

The app id becomes part of its address and must be unique within your tenant. Use a stable, meaningful id. The display name can be changed later without changing that identifier.

## Build the first useful experience

Begin with one clear task. Insert an input, a button, and an output view, then add the workflow data source those controls need. Set the output component's data binding, and wire the button's event to a supported action. Use the preview to check the arrangement before saving.

Definition apps configure data sources in the builder; selecting a workflow at the creation step is unnecessary. Older fixed-template apps use a different creation path: they require a workflow binding and may expose advanced record-type and run-marker restrictions. Keep the template's supplied binding preset unless you understand the records and run markers the template expects. A mismatched binding can leave the app without the intended records even when the workflow has produced data.

## Save and run

Fix the builder's reported problems, then choose **Save**. Open the app's **Overview** to deploy or start it and test the saved experience. The builder preview does not start backend workflows; test execution from the saved app.

Build incrementally. Confirm the first workflow, data binding, and result view work together before adding more components. [Builder overview](/docs/builder/overview) explains the editing tools; [Workflow data sources](/docs/builder/workflow-sources) explains how an app reads and starts work.