1 - Validation and signature

This first step's goal is to define the functional parameter of your future mobile application.

Before signing any contract, you will go through a technical validation process. This validation aims at confirming that it will be possible for ApppScho to connect to your infrastructures to display (and not store) the data on the student's phone.

Afterwars, you will sign a purchase order detailing the features and Service User Contract. This last document does not have to be signed for the project to start. However, we will not publish any version until it is done.

The CUS can be signed after examination of the document by your legal services. The project can start without but no uploading of the application in a production environment can be done without its signature.

Note that once the order form has been signed, it will not be possible to modify the list of functionalities desired for the current version. Any addition requests will be studied for an addition to our roadmap if the functionality is not developed or for an addition to a later version of your application.

It is always better to start with a simple and effective first version in order to ensure that it is available to your users as soon as possible. The heavier the perimeter, the longer the project time will be.