DOCUMENTATION

EXPLANATIONS OF OUR IDEA

Many small producers are the origin of food supply chains around the world. Despite being key players in the immense challenge of "feeding the world", there are many who do not have enough income.

This problem has serious human and economic consequences, both direct and indirect: the families of producers have difficulty meeting their needs or even maintaining the sustainability of their operations because they are not very productive.

As a result, the availability of their products is also affected, which is felt in all stages of the chain to the end consumers.

Many factors influence the income of these producers. Intervening on these various variables through financial, technological, educational and structural solutions would increase the income of certain small producers, and extract them from the vicious circle in which they are caught.

Our mindmaps

First, each of us worked on the following topic: increase the incomes of small-scale producers. Thanks to our research, we have found that short circuits best meet our problem. Short circuits already exist, initiatives have been created in particular in recent years, especially in developed countries like France. It's the AMAPs that make it possible to rethink circuits, to reshape them by offering the possibility of shorter circuits.

One problem: these initiatives are isolated, and there is a glaring lack of communication, of visibility. AMAPs are mostly done by word of mouth, and much of the population is unaware of the possibilities that surround it in terms of farmers' offerings. However, this concept is an “easy” solution to implement, in a large geographic area but also useful and practical.

However, this solution has many advantages, both for consumers, for producers but also for the environment, the State and all the resulting bodies at the national level.

From there, our idea of application followed: listing the AMAPs.
Creating an application seems to be the best response to increase the visibility of AMAPs and thus increase the income of small producers.

The goal is therefore to highlight the AMAP, these allowing to considerably increase the living conditions of the producers, to the users, because we believe that it is an extremely promising offer but too little used nowadays, for lack of mainly communication. We would therefore be a dynamic interface, young, simple and easy to use, so that everyone can navigate.

Here is the link of our mindmeister, feel free to have a look for further explanation:

If you want to go deeper and got all our reflexion about our application, here is our glitch with all explanations and answers to your questions:

Sketch and wireframes of our project

Secondly, we made a sketch of our project to give us an idea of how the different functionalities were going to be arranged. It seemed obvious to us that the application would be downloadable on a phone.

We then made wireframes to better understand the visual of the application and the first changes were made compared to what we had done for the sketch.

You can have a look directly of our final wireframe here if you want:

Also, If you want to take a look at our sketch or our wireframes more precisely, here are the links :

Mockups of our application and tests

Thirdly, we made mockups. This step was one of the longest because we had to think about a name and a real identity, with a choice of colors, icons, texts, etc. During this phase, we had to make our application functional and establish the links between the different pages of it.
You can click here to see what Proximy's mockups look like and have an overall view of our improvment.

If you want more explanations about the differents steps of improvments of our mockup, click on the followed buttons.

More details

Now, for some details, we had to carry out two test sessions to be able to improve our application, whether it is about the design or the use of the application.
For the first test session, we called two people, a student and a team leader. They then gave us several feedback.

Here is our first mockup, before the both test session.

Here are the feedbacks of our first user :


Here are the feedbacks of our second user :


After taking into account the various tips of our two users, we made changes to our mockup such as creating a search bar in the map or even adding the ability to see past orders. We finalized our improvements by doing a second test session with two new users, a salesperson and a consultant. We have made the following changes :



You can find here the link of all our tests for the concept number 1, with more details.

After all those changes, our mockup looked like this:

After our weekly meeting with our teacher, we had to make some improvements, and here it's our final version !

Technologies and improvements

We would like to use technologies for our application. The main functionality being a map geolocating the AMAPs, we will need to use APIs (application-programming interface) to communicate our application with Google map for example. The user can then authorize or not his geolocation when using our application. We will also be using APIs for the payment functionality.
Using APIs seems to be the best solution. Indeed, API is a set of programming instructions and standards for accessing a Web-based application. It allows applications to communicate with each other without any user knowledge or intervention.

To improve our application, we would like to insert a chatbot that would answer questions from users (consumer and producer). To create the chatbot, we could, for example, use IBM Watson assistant.
In addition, we think that having the harvest progress in real time would be interesting for consumers since it's possible to reserve a basket in advance on our application. He could then get an idea of when he will have his basket. This functionality could be achieved with a "comments" space that producers could fill in to inform consumers.