No matter the programming language, applications share 3 different well-differentiated pillars:

1. How Data is organized
2. How Data is used and presented to the user
3. Supporting assets

See there's no “programming language” there? Yet that's usually the first choice when starting a new project: 

“I'm building a React application that does….” 

Being forced to pick the language from day 0 is like being forced to pick the device it will run into. Nobody says:

“I'll build an iPhone 10 app that does…”

Usually a project idea starts with: 

“I'll build something that solves this problem” 

And it … should stay in those terms!

How data is organized

Aptugo applications start with how you'll setup your data. You'll have "articles", then you setup all the data you wish to store for every article.

As it can be seen on above image, a new table can be created by clicking on “Plus” (+) sign. For demonstration purposes, Untitled table contains an ID field.

How data is used and presented to the user

Another key area of Aptugo is the navigation and page builder. In there you can create a list of those “articles”, a form to add or edit those articles. 

Tutorials table, that can be later renamed as Articles, contains a Name field for description purposes. Other fields such as ID, title and summary can be added as well.

Supporting assets

Once you have thought on your data and how users interact with that data, then you might think on adding stylesheets, logo, etc… the “assets” of your application.

You can drag and drop different images, easily change code and stylesheets, documents and other files as well as backups of your application.