By starting a user account or typing a message, you create new data. By clicking on the "save" button, you show that they need to be processed now and saved to use in the future. Choosing "edit account" or "send a message" - give commands to deal with them in a certain way.
All information for your application is stored in databases. They are ordered structures that clearly define the place for each element, indicating the relationships between them and how you can work with them. Databases can be built on different principles, AppMaster.io uses classic relational databases, fully compatible with PostgreSQL.
To be able to fill your application with information, you need to create its database:
For this, AppMaster Studio has a Data Design data model designer. In it, you, like ordinary programmers, will design a database. But instead of lines of code, you will use visual programming tools.
Data models describe the information you add to your application that is “understandable” for AppMaster Studio. They can be compared to shapes or drawings: they determine how your data will look, with what other data it will be associated with, and how it is stored and processed.
By creating and customizing models, you design your application's database.
A unit of data that is generated in your application based on a specific model will be called an object.
In the AppMaster Studio designer, you will only describe and plan future objects, but you can create them only in the finished application.
To create an object from a data model, you need to add a special element to your application page - for example, a registration form. You will be adding elements in the application designers: Web Apps (for web applications) and Mobile Apps (for mobile applications). To obtain information about objects, other elements are used - tables, cards - which are also added in designers.
Each object is assigned an ID - an identifier with a unique number by which your application will "recognize" it.
Each data model has fields that contain the characteristics of future objects and basic instructions for your application on how to work with them.
The fields define what characteristics the object can have. While creating it, you do not need to fill in all of them - you can do it later or not do it at all. You can also set up auto-complete or set some fields as required.
Relationships can be established between two data models - to determine how objects created from them will relate to each other and interact. There are three types of such links:
Linked Data Models gain additional capabilities for collaborative processing in your application. One data model can be associated with an infinite number of others - the main thing is not to complicate the logic of connections so much that you yourself cannot figure it out.
For example: if your application allows employees to create internal orders (for example, for the purchase of stationery), then you create an Order model and associate an existing User with it through has_many - then Jenny can create many orders (for example, every month or quarter). If you establish thehas_one relationship, Jenny will only be able to create one ticket.
So you've learned the basics of working with data models in AppMaster Studio. Now create your first model using this instruction.
You can add additional functions using modules.
We are constantly expanding the list of modules to give your applications new possibilities. Today we will tell you about the ones that have appeared on the platform during the last month.
Today - 5 popular questions that no-code newbies ask our developers.
The Telegram module lets you manage your telegram bot. It now features a Send Message business process block, which adds the function of sending messages to telegram channels. For the module to work, you do not need to program the bot. You just need to create it, add it to the telegram channel, and correctly configure the Appmaster Studio components.
You have reached the maximum per-minute rate limit.
Try again in one minute.