Using App Builder
Let's discuss the 10 important features as highlighted in the following diagram.
- Toggles the edit and view modes. View mode is selected by default in which the application behaves as if it is running in the standalone mode. this is convenient to check the behavior of the application after going through a phase of editing.
- Following are the set of features provided by this toolbar.
- Preview the application in a separate sandbox environment.
- Deploy the application directly on the runtime provisioned for the user development.
- Launch the application from the runtime once it has been deployed.
- Git push and pull operations. Also provide switching of branch between developer and the master.
- Home button is used to go back to the application catalog page of the workspace.
- This toolbar provides following features.
- Create a new item in the selected perspective.
- Save the current item which is being worked upon the app builder. Note that the app builder regularly auto saves the changes being made.
- Undo and redo changes.
- The perspective menu is the most important feature of the app builder. it allows you to select various aspects of each tier. the tiers include the front-end and the backend. in the front-end here is comprised of views scripts fonts and anything related to the styling of the front-end. The backend tier is comprised of the data model from various data sources, services, functions and flows.
- The application is comprised of multiple views. The homepage is one of the views which is created by default. Each view has a distinct name and is composed of a number of components that are selected from the toolbox and has been placed in a specific order by the user.
- A comprehensive list of components are provided to create views which are stitched together to create the application.
- Various HTML properties of the selected component inside the design Canvas.
- List of all the navigation states that are defined inside the application. Every application starts with the "initial" state and will also have the "home_" state. From these two states depending on the user actions the control is passed to a different state and the view associated with it will be rendered.
- The main design canvas where all the components will be laid out in a specific way in order to create a view.