With the Betty Blocks platform you can build the three application types by using the following sections: Data Model, Back Office, Page Builder, Actions, and Tools. Every sections has its own purpose and together they form a broad pallete of instruments to build your app with.
A data model is the visual and simplified representation of all the information stored in the application and underlying database. You build your data model just by drag and drop. You don’t have to create tables and write queries into the database by yourself. The intuitive data model takes care of that. A data model consists of models (the visual design for real-world objects), properties (type of information) and relations (associations between objects).
The back office interface is already built and designed largely by us. Take advantage of that, and see how quick you can build views and forms with components directly from your data model. Just pick up your model and see the visual object as a grid and the forms for every single record. Drag and drop columns and components to customize the view to your own needs. No coding is needed!
Every app type you can build on the Betty Blocks platform needs a back office module (and interface) to administer your data. Use default features in the back office, like filtering, ordering, show/hide functionalities, searching, calculating multiple records or triggering actions to start workflows.
Actions allow you to express the logic of your application. Sending an email when a user clicks a button for example. An action is a visual workflow which requires a sequence of events to execute. Actions are built with a visual editor. Designing an action in a visual way instead of traditionally programming provides you with an increased speed of development and allows you to process easily complex logic into your application. Actions always start because of a certain trigger, automatically (after create) or manually (buttons).
Actions are created at two places in your application: in the Back Office and on Pages/Endpoints. Actions in your Back Office are called 'model actions', because they always involve a specific model, like Order. Actions in Pages are called 'endpoint actions' because they are always initiated when that specific page is visited. Actions always have variables to execute the action events with. Variables could be objects or collections from your stored data.
Contrary to the Back Office, the Page Builder enables more freedom to make any web page you like. To speed up development, we made a Drag-and-Drop web editor with a default set of components. Drag and drop components to create your first login page for public use. Make any web page you like and collect data from the Back Office and render it on your web pages.