1. Goal setting
2. Sketching
3. Building
4. Testing
5. Making changes
6. Demonstrating
7. Support


In the previous step you have determined the purpose of your application. Now you’re going to continue working out your idea! This starts with sketching your application. You’re going to do this the old-fashioned way, with pen and paper.

We do this because your brain works very differently when using pen and paper, than when creating a digital sketch. You’re far more creative when using pen and paper and you really don’t have to be able to draw very well for that. Good luck!

The structure of an application

The face

As a user of an application, you only see the screen (the face) that is shown by your web browser on your PC, laptop, tablet or smartphone. Well-known browsers include Internet Explorer, Chrome, Safari, Firefox. The face of the application is built up (created) by your browser; the browser can do this by picking up the building blocks from the application factory. He (mostly) uses the internet as a way of transport to the factory.

The technical name for this section is the front-end. The tools used to create the front end are HTML, CSS and Javascript.

The factory

The heart of the application is the factory. This is where the machine is and where the processes are carried out. What happens under what conditions with the data that is stored in the warehouse and how will this data be made available to the front-end? The factory creates complete packages that are then picked up by the web browser. Such a package can be an entire page of an application or only part of the page. The factory is started by typing in the address of the application in your web browser.

In technical terms, the factory is called the back-end. A fixed agreement (called a protocol) is used for the communication between the back-end and the front-end; this is called http (or https).

The factory (back-end) is usually located on a so-called web server. This is a server specifically designed to support traffic between the back-end and front-end (over the internet).

Factories are often on a shared web server (a type of business park with shared resources) or the application’s factory is so large that it needs its own web server.

Triggre’s factory consists of flow parts, automation flows and user flows. You’ll run into these items in the Academy videos.


The factory (back-end) uses data, stored for the production of the packages for the front-end. For example, these can be customer data or orders. The data is stored in some kind of warehouse. In this warehouse, the data is stored in a fixed structure that can easily be found by the factory.

We call this warehouse a database and it is usually seen as a part of the back-end. In Triggre, the back-end is only used for the factory and we name the database separately. This database is therefore the third important part of an application.

Databases come in various variants and structures. The still most commonly used structure is that of the relational database. In a relational database, the data is stored in tables that have a fixed relationship with eachother. In Triggre, this database is called Data and the data has a Referral between themselves. How to create this for your own application? You’ll discover that in the videos! Good luck!

Get started