App Architecture

The AppMaster.io no-code platform builds applications in the same way as regular developers do. Therefore, the components of your application will be the same as any professional software.

Backend and frontend

The application created in AppMaster.io will consist of two main parts:

• Backend - the back end of your application - everything under the hood. Here the general logic of work is determined, key parameters are configured, the main data processing processes are created; this part is located on the server and is not visible to users.
• Frontend is the visual part of your application that users interact with. You can say that this is your application - how it will look from the side of users. This part is configured in one of the app editors - Web Apps for web apps and Mobile Apps for mobile apps.

Because of this structure, you can simultaneously create a web and mobile application that will be connected to each other - through a common backend.

Backend

The backend of the applications that AppMaster.io creates can be hosted on your local server, cloud hosting AppMaster.io Cloud, or third-party storage - AWS, Azure, Google Cloud, etc.
You can export binaries, custom files, and your application source code - and move wherever you want, automatically or manually.

The backend of your application is built according to the following logic:

• Database design - creating data models and relationships between them.
• Building business logic - setting up business processes.;
• Endpoint and middleware configuration.

Modules are used to connect additional functions.

We recommend adding all the necessary modules at once - they contain elements that will be useful to you during design and speed up development. 

Frontend

After you design the back-end, you can go to the front-end settings - directly for applications - in one of the designers: Web Apps (for web applications) or Mobile Apps (for mobile applications).

The order of building an application in AppMaster.io is from backend to frontend. However, you can first create a mock application, and then "bind" the data and business logic.

Database and data models

All application data is stored in a strictly defined structure so that it can work with them using clear algorithms. The individual parts of this structure are called databases. For no-code database design, AppMaster.io uses a visual data model editor.

Data models

Data models are kind of tables with descriptions of data that are stored in databases. When you create a data model, you define exactly what data will be in your application, how it differs from each other, and how you can work with it.

Data models are located in a separate designer AppMaster Studio - on the Data Design tab.

The data you entered(users, customers, products, orders, messages, etc.) can be viewed in the finished application, but you will not see them in AppMaster Studio. In the designer, you will only work with a visual representation of the data storage structure and the processes that will occur with them.

Business processes

Business processes are logical sequences of actions that implement specific functionality in your application. For example, creating a customer request, booking a ticket, or sending a message. When creating a business process, you determine where the application will take information from, where to transfer it, how, and in what order to process it - that is, you set up the business logic of the application.

You can create and edit business processes in a special designer on the Business logic tab. The execution of business processes can be launched on a schedule, as well as called through other business processes or endpoints.

Endpoints

Endpoints are a kind of gateway that connects the server processes of your application to the front-end (web or mobile application itself). Each endpoint will be associated with a business process and a page (or screen) element - in order to transfer data between them.

You can create and configure endpoints on the Endpoints tab in AppMaster Studio.

To manage complex tasks (access control, data filtering), middleware is connected to the endpoint. It plays the role of an additional link between the endpoint and the business process and allows you to further customize their interaction.

Some middleware is added to your application by default, others when some modules are installed. For example, the Auth module, which is responsible for authorizing users, provides a Token Auth middleware for managing permissions to launch a specific endpoint.

Endpoints form what is called the REST API - the programming interface of your application for exchanging data implemented using the REST architectural approach.

API AppMaster.io

API (Application Programming Interface) is a set of tools that exchange data between the frontend of your application, its server part, as well as third-party applications, services, and sites connected to them. REST is the technology by which this data exchange takes place.

The API documentation for your application is generated automatically and saved in OpenAPI (Swagger) format in its backend.

You do not need to specifically understand how it works to master AppMaster.io - you will understand the basic principles by studying the platform tools. Besides, the main part of the API is created by AppMaster.io - most of the settings are made by default or when connecting modules.

You will need to manually change some of the API settings when integrating (connecting) your application with other applications or external resources.

Publication

After you create an application (or change some part of it) in AppMaster.io Studio, it needs to be published - that is, posted on the Internet - in order to test or make it accessible to users.

When you publish, the code generated from your diagrams in AppMaster.io Studio will be compiled - converted into a finished application.

You can publish your app to AppMaster Cloud, a third-party cloud service, or your personal server. Mobile applications can be placed on the App Store and Google Play.
Application server components (including mobile application manager), web applications, and Swagger are packaged in a single binary file. This file can be compiled for various operating systems - Linux, Windows, MacOS with various processor architectures - x86-32, x86-64, and even ARM.

Mobile apps can be published directly to the App Store or Google Play. Thanks to the Mobile Apps Adapter, you only have to publish your app in the store once - if you want to change or update it, in most cases you will not need to republish.

The Mobile Apps Adapter is a modern real-time engine that connects mobile app endpoints and design into the user interface and data streams for deployed mobile apps. Rendering of the interface and data happens in real-time with no visible delay. This approach provides many options for editing applications without republishing them to stores.