How to Plan an App

To plan an App is almost to build an App

You’ve created a Project Space and a Project within that Space. Now…

How would you plan an App?

Forget Logiak for the moment, consider the question: how would you plan out what you want from an App?

Events App

Let us suppose that your company manages Events of some kind and you want an App to help with this.

Suppose you want the user to login and then perhaps see all Events currently in the database. The user should also be able to register a new one and to select one from the list.

Planning an Events App

You might start to map out by sketching a flow chart.

Something like this perhaps:

  graph LR 
        A[Logs in] --> B[Views List of events in the db] 
        B --> C[Can add a new event] 
        C --> B
        B --> D[Can select events from List]

The Flow Diagram in Logiak

Now let’s look at Logiak.

To build an App, you do the same kind of thing as we have done above to plan an App.

To build an App with Logiak, make a flow diagram out of Components linked together.

Despite the surface differences, this is fundamentally the same as the flow chart above: it shows a Login component (user logs in), followed by a Listing component (user is shown all events).

The user can choose to SELECT something from the list or to ADD something to the List.

The difference is of course that once you have planned the App out like this in Logiak, you have also already built it!

Component Flow Diagram for the Events App

Watch this short video to see how this can be achieved in Logiak

New Apps have a LOGIN component by default, then we add a LISTING…

In a Logiak Component Flow diagram, each “node” represents a Logiak Component.