We started with a kick-off workshop to help us define the client’s actual needs. Quite often the list of requirements is long but most of them have to be reconsidered due to limitations imposed on by time, budget or technology. So an initial consultancy meeting is a great opportunity to go through the list together. You can then select the functions that are absolutely necessary from the very beginning and identify the ones that can be developed at a later stage.
Cycling Service wanted the solution to be compatible with mobile devices, especially the iPad. That is why we decided to adopt the Mobile First approach. It is a method of designing projects with mobile functions in mind in the first place. You leave the complex, multi-function desktop version aside for a while and concentrate on the mobile one. The Mobile First approach allowed us to build a separate application to serve the mobile devices, without touching the existing one
When the first version of the new solution was ready we took on yet another challenge. We had to convince the client to show demos to the end-users. Performing user tests at an early stage of software development is the best way to make sure you are going in the right direction. That was also the case with Cyclotivity – we wanted to validate our ideas as soon as possible.
The technologies used to develop the app were Java Spring Framework for the back-end and HTML5 for the front-end. The project was Agile of course, so we could deal with all the challenges, be ready for unexpected changes and quickly react.