App Builder data and routing FAQ
Answers about the App Builder environment, and the Globals, Data Source, Route, Table and Events building blocks that connect a component to its data.
App Builder is Studio's editor: the same visual environment covered in full on Studio overview. This page answers the questions that come up about it as a whole, and about four of the pieces a component connects through: Globals, Data Source, Route and Table. For the deeper reference on any one of them, follow the links in each answer.
What is the App Builder?
The low-code editor at the center of Xuda: a visual canvas for building screens, logic and data without writing boilerplate, with AI able to generate a starting point when you want one. See Studio overview and The AI App Builder for the assistant panel that does the generating.
What are the building blocks every app is made from?
Four kinds: Globals for values and logic the whole app shares, Tables for structured data, Programs (components and the logic units that support them) for behavior and screens, and Routes for navigation.
Can AI generate parts of an app for me?
Yes. The AI panel can describe and generate logic, data models and UI from a prompt, and you stay in control of the result. See The AI App Builder.
Globals
What is Globals for?
The one shared program every other program in the project can read from: constants, shared variables and startup logic that belong to the whole app rather than one screen, like the signed-in user, a feature flag, or an event hub several components listen to. See Globals.
Does Globals run on the server or the client?
Always the client, regardless of what a program's runAt setting says elsewhere. Anything that
must stay off the device, a secret or a privileged read, belongs in a server-side Get Data or Set
Data program instead.
Data Source
What is a Data Source?
The connection between a screen or a piece of logic and the information it reads: a table, an array built inside the app, a CSV or JSON payload, or an external URL, with filtering to shape the result before it reaches your component. See Data source.
Which units can use a Data Source?
Components, and the Get Data, Batch and API logic units, since all of them can need a place to read information from.
Route
What is a Route?
A navigable entry point: a menu destination that maps a path or label to the component that renders it. Routes live in their own branch of the Studio tree, separate from Programs and Database, and have no folder nesting, every route sits directly under the Routes root. See Route.
Can a Route control who reaches it?
Yes. A route can require specific permissions or group membership before it opens, so a sensitive screen stays reachable only by the people who should see it.
Table
What is a Table?
How the app stores structured data: rows and columns with typed fields, validation and indexes, designed visually in Studio or from the project's Data tab. See Table.
Can a Table connect to an external database?
Yes, through a database plugin. Xuda ships built-in connectors for its own store, CouchDB and MySQL, with more available as plugins. See Plugins for the plugin system this draws from.
Component events
What do a component's events do?
They tell a component when to act: attach a workflow to an event (load, exit, before or after save, a button click, or an event you name yourself) and the component runs that logic automatically at the right moment, without someone triggering it by hand. See Component events.
Can one event trigger more than one action?
Yes. Each event runs an ordered workflow, so a single trigger can chain as many steps as needed, and any step can carry its own condition to decide whether it runs.