0%

Leader Price : Courseur

Mobile app

Context

Creation of a mobile app for LeaderPrice

Client

Leader Price / Courseur

Fields of expertise

#Mobile #UXdesign #Ergonomie

Divisions

App
Consultancy

A service-oriented app

Based on the observation that many people use their vehicle to fetch supplies from the closest supermarket to their home, Courseur decided to create an app that enabled users to limit such travel with a view to reducing their environmental footprints. This worked by enabling users who visited the supermarket to buy another user’s shopping on their behalf and to have it delivered to them via the app.

Adaptation and responsiveness

Since the lead time was particularly short, the agency adopted an agile approach by doing away with the traditional specifications regarding the working method. As for the technical aspects, the developers used a hybrid technology combining Cordova and Ionic that enabled them to code in web language whilst at the same time being supported by native languages for iOS and Android. The agency also used a special server for storing the data and created an API (business logic). This was designed with Ruby On Rails.

Very comprehensive test phases

In order to ensure that the app worked as best it could, the agency’s technical teams introduced a series of tests using Gitlab and a docker registry, as well as using Selenium via Browserstack. Communication with the web app version of the API was also important in order for Protractor to be able to test it on all browsers.

The iterative method enabled each developer to modify part of the code, send it to our Git (Gitlab) source server and have these tests performed automatically to verify that the app was working as it should. Whilst the developers were obliged to use this testing method, they did enjoy being able to try out new technologies such as Appium and AWS Device Farm.

Three environments for greater flexibility

148 Agency was able to quickly reconfigure the server using the various scripts pertaining to the Ansible platform and therefore to also create three environments - one for testing, another for production and a third for implementing the app demo. This single-track method makes it possible to work in one environment without any direct impact on the other two, meaning that it was far easier and quicker to adjust and modify the various components of the app.

Rémi: lead developer on the Courseur app

How did the project go?

We worked alongside the app’s creator, Sébastien Vray (initially known for the Respire association), and branding agency Pixelis in agile mode on this project. Sébastien had set up a study with a view to improving our knowledge of the market and had designed a number of app screens to guide our thought process. My team and I broke the task down into a series of functions to enable us to estimate a cost/time ratio for each app function, such as the electronic signature on the phone, or the way a delivery driver drops off a parcel, for example.

We then created a minimal version of the app featuring the basic functions. Each new stage of the project was consequently seen as a development broken down into V2, V3, etc.

What method did you use to design the client pathway?

The agency’s developers then worked alongside one of our UX designers to introduce wireframes of all of the app screens in order to visualise the user pathway from the perspectives of both the courier and the client. This structure and the corresponding functions were agilely honed over the course of the project through regular exchanges with Sébastien and Pixelis.

What was your contribution to the project?

I designed an initial build of the app before breaking the functions down, together with Amélie and Axel - two of our back-end developers. We then had the whole thing approved by Mathias - 148’s technical director -,

at which point the development could begin. I was notably responsible for the front end, meaning that I focused on developing the parts of the app that would be visible to the user. Amélie and Axel oversaw the back aspect - the database and the API. The two developers were responsible for introducing the environments (staging, demo and production servers) with Mathias.

Throughout the development process Sébastien needed to add certain functionalities that were considered to be vital, and Mathias and I supervised this aspect for the purposes of enhancing the app with the additional features.

What happened next?

Once an initial stable version had been achieved I was responsible for adapting the apps to test them on mobile platforms (iOS and Android) with a view to eventually rolling them out in the corresponding stores. (Google Play Store, App Store).

148 Agency oversaw only the development aspect. The logo and screen design were supplied and integrated by Courseur”.

Got a project? Want to talk about it?

It’s even better if you make it happen!

Contact us

We use cookies to ensure that you get the best experience on our site. By continuing to use the site you agree to our use of cookies.