Studio overview
The project editor's five working areas and the tree of building blocks every Xuda app is made from.
A Xuda app is built inside a project, and a project is built in the project editor: the workspace you land in once you open or create a project in Studio.
The Studio start screen, before a project is open, and the project editor, after one is open, are not the same UI. This page covers the editor. For the start screen and the Empty project / Draft / Template choice, see Starting a project.
The five working areas
Once a project is open, the editor is split into five areas:
The left tree
The tree has five top-level sections:
An older description of this screen calls this section "Tables". The tree itself labels it Database, a table is what you create inside it.
Programs: the pieces an app is built from
Everything under Programs and Globals shares the same underlying document shape, fields, events, a workflow, specialised by its type. The ones you'll reach for most:
Each of these has a matching Studio page in this section: the Datasource, Fields, UI and Events tabs are how you build a component by hand.
The right panel
The right side of the editor is a split pane, not two tabs you switch between: an inspector on top and the AI chat underneath, both visible at once.
- The inspector shows the Properties of whatever is selected, in the tree or in the UI canvas. Nothing selected leaves it empty.
- The chat underneath is always available. See The AI App Builder for what it can do.
The bottom console
Turning on live preview runs the selected component as a real session instead of an editable canvas. The console at the bottom attaches to that session: capture a screenshot, inspect an element, read logs, or reload it. See Live preview and the console.
Typical build flow
Add the data
Create a table under Database, and add the fields each record needs.
Build a screen
Create a component under Programs, connect its Datasource to the table, and lay out its UI.
Make it react
Add Events and give each one a workflow: save, alert, navigate, refresh.
Make it a page
Add a Route so the screen can be opened as a URL.
Check it
Preview the result, then run validation before sharing it.