Core Concepts
Learn about the App Builder's core concepts. These definitions will guide you throughout this documentation and your building process.
Last updated
Was this helpful?
Learn about the App Builder's core concepts. These definitions will guide you throughout this documentation and your building process.
Last updated
Was this helpful?
There are 3 major types of data source in the app builder: Table, Metric and Query
Tables: are the primary data sources in the App Builder. Tables is an intuitive way to access and data in your app and interactive with them in the app.
Metrics: work as a data source that's ready for reporting and charting.
Queries: allow you write templated SQL queries to retrieve data from your data sources or modify your databases.
Data Store is a place where you can create variables to store data and flexibly use it anywhere. These variables can be accessed via . The variables can also receive data via interactions within a specific scope. There are three levels of data in the Data Store:
App Data: Data is stored at the app level. All the elements, or pages in the app can access it or send an interaction to it.
Page Data: Data is stored at the page level. Only the elements on the same page can access or send an interaction to it.
Element Data: Data is stored at the element level. It can only be accessed by the element that stores the data. For some elements, such as Lists, their child elements (that is, elements placed within them) can get parent element data directly by declaring specific keys, such as ${$item}.
The App Builder provides users with the low code tools to easily build custom web applications to streamline business operations. Web pages are built using a variety of drag-and-drop elements, each with highly customizable settings, so you can build the most relevant app for your purpose.
An app is an application software that is stored on a remote server and runs in a web browser. They can be designed for a wide variety of use cases and functions.
The app builder is designed for collaboration.
You can see who is collaborating with you at the real time.
Pages are just like a webpages of a website. An app is usually composed of several pages. For example, it can contain a sign-in page, home page, and profile page.
The app builder accommodates three distinct layout options designed for various devices: Desktop, Tablet, and Mobile, all available at the same time for your convenience.
When designing layouts for tablets and mobile devices, the styling is exclusively applied within their respective scopes. As a result, each of the three devices can have its unique view without interfering with the others. This allows for best adaptation and optimization of your content for different screen sizes and devices.
Canvas is the space where you arrange all the components across pages.
In Canvas View, all the pages are positioned on the canvas, and you can organize them with spatial logic. To edit a page in Canvas View, simply double-click on the page
The Default View is designed to focus on a single page at a time, offering enhanced zooming and scrolling experiences. This view helps you delve deeper into page development.
There are 3 types of Elements: Basic, Layout, and Form.
Basic: These are essential elements such as buttons, text, images, and charts.
Layout: Layout elements provide a formatted layout that you can reuse to organize the elements.
Form: Form elements can be used to capture user input, such as user-entered text, date pickers, and checkboxes
Data sources, elements, and your app communicate through Interactions.
Interactions consists of 2 components: event and action. When an event occurs, an action is carried out. For example, a click of a button can be an event to trigger an action to navigate to a different page.
Scheduler Node to trigger other actions or Nodes Notebook Node to connect to a Jupyter Notebook. Used for connect an algorithm or machine learning model.
An consists of two candidate events. Simply put, it will send out an outbound event when it senses an inbound event. An action requires a source and a target. Usually, an action is defined on the source, which is an element that listens to the inbound event. For example, you can define an action on a button that sends out a notification when someone clicks this button.
