After you've finished our Mobincube tutorial and know how to create a simple mobile application, it’s time to talk about advanced features. Sometimes you need to build a complex mobile app, and this requires using advanced techniques. But don’t worry – when using drag and drop app development software, like Mobincube, you are not obligated to have any technical background to start implementing those techniques into your app. Below, you will find some useful Mobincube tips on how to work with databases and data variables.

 

Imagine that you need to create an appointment booking app for your business: yoga studio, clinic, hairdresser service, restaurant, etc. This is one of the most popular types of mobile apps for a small business. Let’s use an appointment booking app case study to explain how to work with data sets in Mobincube.

 

First, we need to point out that Mobincube allows you to use variables and databases for storing data in your app. Variable is a symbolic name (an identifier) linked to some known or unknown piece of information. For example, you can name your variable Age and store the age of a user of your application. The Age variable has an unknown value just after the user launches the application, but changes to an exact numerical value after the user fills in their age somewhere inside of the application. When you know the date of birth of this user, then you can tell your program (mobile application) to change the Age variable and add +1 year to its value exactly on 0:00:01 AM on the user’s birthday. Variables exist in the memory of the user’s mobile device and are used during the current app session, or they can be written to a database and then restored from the database during the current or next user sessions.

 

The SET Action of Mobincube is used to assign values to any variables (including those stored in a database). Variables could also be Global – these are the variables that are automatically created by Mobincube to store some app environment data (like user location, user IP address, etc.). In the Mobincube interface, you will find a feature called Compositor, which is located just under the list of Actions. There, you can see a list of all Global variables which allow the developer to customize and analyze the activity of app users.

Mobincube tips (with appointment booking app case study)

Mobincube tips

For example, among Global variables you will find the following:

 

{country} -> A country where the mobile device is located

 

{language} -> Device language (En, Es, Pt, Fr, etc.)

 

Global variables are automatically created by Mobincube, but custom variables are created by you. You can store a value of any custom variable until the app is closed, or you can write your information to the database and use it in your app later. You can assign values to your custom variables in the following way:

 

SET (Column1)=55, or SET (Column1)={var.age} to save the user’s age that they submitted in their medical treatment form.

 

Databases can be edited manually via the Mobincube app development software interface (each table of your database can be edited row by row, like in Microsoft Excel), or you can work with a database using some programmed Actions, like SET. Databases can be exported, or even linked with an external database (the last one is recommended only for advanced users who know some programming and how databases work).

 

Database related Mobincube tips are easier to understand with the appointment booking app example. Let’s do it in the following way. First, you manually create a table of your appointment booking database (let’s assume this simple database has only one table) and list all available appointment times for each day of the week. For example, you name your first column Day_Of_Week, second Appointment_Time, and third Is_Booked.

Create an appointment booking app

When the first user of your app requests the available appointment times, you load Day_Of_Week and Appointment_Time values from this table. Then your app gives the user an option to fill in a form and put their personal data to book any particular appointment time from those shown. Then, you use SET Action to assign “booked” value to the Is_Booked column of the chosen appointment time (when a time is booked, you write Is_Booked=1 to your database). When the next client requests the available appointment times, you make your app show and book only those appointment times, which do not have Is_Booked=1 value, so that any particular appointment time is not booked by two people.

 

To display the available appointment times to an app user, you just Filter your appointment booking app table to exclude those times which are already booked (check out the filter settings in your Mobincube database editing interface). You can filter the data you display in any section of your app by adding some data filtering conditions. So, in our example, your data filtering conditions will check the Is_Booked value for any appointment time, and if the value is “1”, then you do not display this time as available for booking.