Apps

Apps provide an interface for end-users to view and interact with the data in a solution. A solution can have many apps and they all share a common data model. This allows you to create targeted apps that serve a specific purpose for a group of users For example, a common pattern is to have one app for customers and another for admin users.

Building an app consists of three main elements:

• A user interface (UI) to create the visual structure and design of the app for end-users.

• Data to define variables and what objects in the database can accessed and manipulated.

• Actions to add logic for data manipulation and app navigation.

Apps can be built with responsive design, supporting multiple screen sizes and device types, or restricted to certain screen sizes. By default, apps require authentication and support fine-grained user permissions, but they can also be published to the open web.

Apps built using Appfarm Create are Progressive Web Apps (PWAs) and this enables users to install an app on their device and use it in much the same way as a native app, without having to download it from an app store and keep it updated.

UI

The user interface of an app is built up of views that represent the pages, dialogs and menus a user can interact with. A view is constructed using a library of customizable UI components to render static text and images, collect user input, and display data from the database. Additional interactivity is enabled using actions.

pageUI

Data

Data contains the data sources which an app can use to read and manipulate data. Built-in data sources such as App variables are used to track and manage the state of an app, and custom data sources can be added used to access and store data in the database. Data sources and individual properties are available in the UI and actions using data bindings.

pageData

Actions

Actions are blocks of logic used to run data operations and move between the views in an app. Actions consist of one or more action nodes – pre-built logical operations with customizable properties. An action is typically run when triggered by an event.

pageActions