Plan week 11

--Originally published at How to HACK or not

This week we will continue working with the implementation of the app in relation to the api of google maps, we will perform GPS location tests and so on.

We hope at least finish this part, the map view and the current location sending in intervals of n meters away to be able to present it in the next week presentation, that also we will have to prepare it.

Review week 9

--Originally published at How to HACK or not

This week we were making the google maps integration.

We faced some troubles because some unknown errors, but with help of the google maps api documentation, god google and his disciples stack overflow and other reliable sources (ok, other blogs that seemed cool) we were able to solve them, also Gabriel knowledge was helpful.

Plan week 9

--Originally published at How to HACK or not

This week we will start with the integration of google maps. Remembering the project mockups, we need to be able to display the map, get our current location and also show our position reflected there. Maybe (pending) we will show also information about nearer places.

So we will start trying to develop the map screen and at least be able to make other needed google maps api’s requests although we still do not show/draw the answer.

Review week 8

--Originally published at How to HACK or not

This week we worked with the firebase and google maps installation. Also we were able to create the needed accounts and generate the api keys.

Since we (Mark, Constanza, David) are new developing iOS native applications we have some challenges with firebase set up, but regardless of this was nice of us because we learnt about this process.


Review week 7

--Originally published at How to HACK or not

This week we were able to finish all the needed mockups regarding to the functional requirements. Since we had the mid-semester presentation we prepared the requested slides with the work we had already done, mockups and diagrams.

Finally we initialized the project to transfer all the work to a tangible, functional application.

Review week 5

--Originally published at How to HACK or not

This week we were able to generate the following screen designs:


The first one will be the initial screen of the application, we just have the logo and the input for the bici’s code that the user will have to enter in order to map their information with its bicycle. The splash screen will be similar, white background and the logo will be launched.

Then we have the permissions screen, a topic that we previously discussed, where we clearly ask the user for share with the app his location.

Later on, we have the map screens where the user will be able to see his location, general information of places and to end up their journey. While he does not click the button, application will be saving its coordinates every time user moves 10 mts.

We are also thinking about putting other screens to give the user more relevant information about their journey, for example distance, speed, total time, etc. But this is not really important for the goal of this project, it could simply give it more value as a cyclist application.

Weekly plan #5

--Originally published at How to HACK or not

This week, according to the ideas that the whole team has collected in the previous weeks, we will finish defining the screens of which the application will consist.

Finally we will make designs, our mockups, for based on them to program the views. Together we will share opinions and generate the general idea, but Gabriel is the one who will illustrate the designs.

At this moment, we are clear that we will use the logo of “mibici”


and in general we will use those colors for the theme of the application.


--Originally published at How to HACK or not

This week we will start with the technical planning of the application. We will generate the backlog according to what, we have investigated and agreed, at the moment, is fundamental for our development flow.

Since Gabriel is the one who has more experience working with native applications for iOS, he will define the tasks about project configuration and initialization. From then on we will write the tasks related to the configuration of firebase, what we need according to the design ui of the application as design of views and generation of assets, etc. To avoid inconvenience, we will define all tasks with detailed description and acceptance criteria.

At the end of the week, because of the Project Management class, an interview will be held with Bosch, to finish clarifying some doubts regarding the requirements of the original project,  but it may be relevant for us to define the way in which the data that we will analyze later will be treated and stored.

For this phase we will use a board in trello: