Models describe the data that your app uses. Example models include:
You can create the models yourself or import (share) models from other apps. For example, importing the user model from System allows you to bind app-specific data like schedules to users (binding models together is done using Relations).
Models consist of attributes. Each attribute describes some important property (for instance, a customer’s address or phone number or an article’s price) and has a data type that defines how the attribute looks and behaves.
|Data Type||Description||Example use cases|
|Integer||A number. Allows arithmetic operations, cannot have any decimals||1, 2, 3, …|
|Float||A number. Allows arithmetic operations, can have decimals.||Prices|
|String||Plain text.||Use for storing text of all kinds. Also for numbers you do not want to perform arithmetic operations on (such as phone numbers).|
|Boolean||A value that can only be true or false.||Completion of tasks, calendar bookings, etc.|
|Date, Time, Date & Time||Stores date and/or time in various formats.||Start times, completion times, durations, etc.|
|State||Has a finite number of values, defined by you.||Order status (placed, in progress, done) and similar|