Build an Application

First steps from idea to a working prototype.

This is a short path from idea to a working app.

You’ll stay inside the Editor and Runtime preview.

Who this is for

• Product and design teams.

• Developers building fast prototypes.

• Teams that want a shared UI-first workflow.

Outcome

You’ll have:

• A small, testable app.

• A clean first-pass schema.

• A loop for safe iteration.

The workflow

1

Start with one goal

Write 1–3 goal statements.

Keep each statement one sentence.

Example:

• “As a teammate, I want to add tasks so I can track work.”

2

Sketch the screens

Draw the flow.

Most apps start with three screens:

• Home or dashboard

• List

• Create/edit form

Give each screen one primary action.

3

Define the minimum data

List the data people must enter or see.

Then group them into sources.

Example (Tasks):

• Title

• Notes

• Due date

• Completed

4

Create sources

In the Editor:

1. Create the main source.

2. Add the minimum fields.

3. Add a few sample rows.

5

Create pages

Create two pages per source:

• A list page for browsing.

• A form page for create/edit.

Then enable actions:

• Create from the list.

• Edit from list rows.

6

Preview the full loop

Open Runtime preview.

Run the primary task end-to-end:

• Create a record.

• Confirm it appears.

• Edit it.

• Delete it.

Time the flow.

Remove friction.

7

Iterate safely

Change one thing at a time.

Then re-run the same flow.

Common iteration moves:

• Reorder form fields.

• Rename labels.

• Add one missing field.

• Split one page into two.

8

Prep for production

Checklist:

• Avoid renaming fields with live data.

• Back up or export before major schema work.

• Add validation only where it prevents real mistakes.

• Write clear error messages and empty states.

Practical example: Task Manager

Build this in under 30 minutes.

1. Source: Tasks.

2. Fields: Title, Notes, Due date, Completed.

3. Page: Tasks (list).

4. Page: Task (form).

5. Wire Create and Edit actions.

6. Add 5 sample tasks.

7. Test the full loop.

Habits that keep teams aligned

• Use shared naming conventions.

• Keep pages small and purposeful.

• Record risky schema changes in a changelog.

• Test with real people early.

Related guides

• Sources first: Create and Manage Sources

• Screens and actions: Create and Manage Pages