Sprint 3

Gaëtan Schwartz (@gaetschwartz)

I worked on implementing the cloud functions as described in my proposal. This took more time than originally estimated as I had an issue with install Node on Windows and had to remember how to code in TypeScript. I also took some time (2h) to think more aobut our server architecture, and different issues we might encounter (synchronization, parallelism, etc).

Adam Narozniak (@adam-narozniak)

I worked on the game simulation. It includes playing with the computer and then displaying the win/lose/draw. It's really simplified version (has a few shortcuts, it supports only one round game, and doesn't use the models - they, in my view, need changes). I had trouble with data binding and using it (especially group radio buttons that were included and I still have to figure it out) and I think I need to learn live data for score updates during the game along with the rounds. In the next week, I'll collaborate on the game model and round model. I'll also work on polishing up and solving temporal solutions. I also implemented the result screens in sigma.

Silvio Müller (@aladin6060) (Scrum Master)

In this Sprint I worked mostly on the implementation of a Figma model. This took way more time than I expected. UX design takes time, who would have thought! Maybe I should have used my time better on learning more of the backend and coding tasks. Next, I will work on changing the Navigation element to bottom navigation and look into options for how to use some sensors for our app. Either vision for detecting hands or GPS for locating close players.

Bhargav Venugopal (@bhvrgav)

This sprint, I wanted to have a fully connected and functioning friend's page to showcase during the demo. However, due to a frustrating issue with github, I was delayed a lot and was not able to complete much. My inexperience with github and the various components of android studio definitely did not help. So, as for my intended outcomes, I missed the mark.

Leonardo Pennino (@leonardopennino)

This week I worked on a problem that made impossible for the other people in my group to use correctly google sign in. Turns out that there were errors with the configurations of private OAUTH keys. After I worked on connecting the authentication with the underlying database. On successful authentication now it is created data in the database if the user did not exist or data is retrieved from the database in case it was already registered. In the meantime I have been trying to find the simplest way to share the data between fragment, possibly by using a central model referenced by all fragments / activities. Still a WIP.

Jinglun Pan (@panadax)

In this sprint, I mainly worked on Firebase Database, which I am not familiar with at all, so I have learned from youtube at first (1-2h). I have designed a database structure and mocked corresponding data for the STATS module (1h). You can refer to here. At the beginning, I encountered trouble in firebase authentication, but with the help of @Leonardo, I can set the environment up to link properly. Another problem is the Firebase Database loads data asynchronously so that I cannot return something now that hasn't been loaded yet. In other words, you cannot simply create a global variable and use it outside method because it will always be null. Fianlly I found a solution to create callback interface to make it (8h).

Overview/Summary