Startup documentation

Before starting the actual development...

Perhaps the most important step in the project

Based on our experience: The more you do work on this the faster you can get your app to market and the smaller the development costs are. In our projects we need to have following documents:

  • App view documents: How the App look, what view it has and what fields and how the user moves between the views.
  • What data your application access: Eg. Users and their attributes (name, age, address, discount groups etc.); Products and those attributes (size, color, price, discount price etc.); Sellers and their attributes (product lists and price lists, terms etc.)

First one we need for Felgo SDK development. Second one for modelling the Aurora serverless database (Postgresql compatible). And after this both for figuring out what REST API endpoints the App need.

We accept all the document formats - even hand written papers. And if something is missing we will ask more information And we can iterate the documentation together. After the documentation is done we can try  to figure out is it possible to implemented the App in the budget..

Design guide

Here is a short description how we have make a design for Bigas (our White Label -project). In short it contains following major parts:

  • Model the real world and relations, business processes etc. to database
  • Create UI for the App
  • Implement the App, REST API endpoints against the database and set up the database.

On the left side you can see draft database model of the Bigas created on Amazon Aurora serverless. This is something you don't need to worry - we create this for you. All you need to do is answer some questions that might rise up while we do this modeling.

UI desing

This is actually quite tricky part and because of this we have some "basic elements" that the design would be good to build on. These elements are

  • Navigation: The easiest way to implement this so that it works "native way" on iOS, Android and Desktop is to do it in following way.
  • Define in which roles the users can use the App
  • Define navigation items each role have in navigation men when using the app in that role. In short the navigation item list will change after the user have select the role.

On the right you can see how this look on IOS and Android. There are three roles from Bgias and in iOS the navigation items are bottom and in Android (modified screen size for this) you can see opened "Hamburger menu" containing the navigation items. Each item will then have a screen containing pictures, input fields etc.