Sprint 4

Gaëtan Schwartz (@gaetschwartz)

I took time to explain to members of the team how to the proposal worked, what it implied as well as clarify/debate on some aspects of it. I also started and almost finished working on a game service that will manage the game on the device, as well. Thanks to a question by Jinglun, I realized we also needed to a clear way to access our different Repositories and Services, so I looked into DI (dependency injection) for Android. Being not familiar with it, I took quite some time to try and learn Dagger and Hilt. After to installing and trying Dagger and Hilt for a few hours, I felt like it would be too hard to explain to the team and ultimately use. I thus opted for a simple hand-made Service Locator. The matchmaking PR will probably be ready this weekend, once we all make sure we agree and understand the proposal, as some still didn't really review it before now. I couldn't get as much work done as I hope for , because of discussed personnal issues.

Adam Narozniak (@adam-narozniak)

I got acquainted in detail with the matchmaking proposal, did a massive review because it was also affecting the part of my code and is important in general. Then I move to my game simulation part (reflecting user rock, paper, scissor choices and letting them fight against a computer). I had troubles with fragment communication (home fragment - the one you choose the game type and game fragment). I implemented a shared ViewModel, which I had to learn about because my previous naive methods failed. It still has room for improvement - tests and logic decopling which I'll work on.

Silvio Müller (@aladin6060)

This week I changed the Navigation of the app from a side drawer to bottom navigation. This took more time than I anticipated since I had to replace a lot of the old layout files. And I had to reimplement the tests. After finishing that I started looking into options how we could use the sensors of the Phone in our app.

Bhargav Venugopal (@bhvrgav)

I tried to implement some simple button logic for the friend's page. After which I tried to write tests for my code. I spent a lot of time on SDP this week but it is not reflected in the work because it was spent trying to learn how to write tests. I found it very difficult because I could not figure out how to tweak the tutorials such that they would work on my code. I find it very frustrating not being able to merge my feature into the main branch for yet another week. I am going to spend some more time on it this weekend and hopefully I finish my testing and do a successful PR so you can finally see my feature live next week.

Leonardo Pennino (@leonardopennino)

• Implemented profile page to show database synchronisation
• Tested profile page
• Studied a way to easily share a state with all fragments. Check ui.profile.profileFragment to see how it works.
• Modified previous implementations of login and firebase references to accomodate user state into the app

Jinglun Pan (@panadax) (Scrum Master)

I have tried to collaborate with @Gaëtan and @Leonardo with the database linking since the STATS module should get info from the game and user, basically it can be linked with user DB in a proper way, and I also generate fake data in Game info so I can fetch it. The main obstacle is I should decouple my code out of the UI-Fragment so next week, so the code can be approved when I can refactor my code next week. Also, as a scrum master, I found this is a common issue for all of us, so we also need to reclaim what is the best practice to organize our code. In addition, I think we need more discussion before you plan to implement something is a good way to let others know what you are going to do in case you are in the wrong direction.