-
Notifications
You must be signed in to change notification settings - Fork 0
Sprint 3
I implemented the feature which allows the user to see the stats the app has tracked during the game mode, and shows to the user which songs they have failed to guess. There were tons of unexpected issues, mainly with passing information along intents, and recovering resources on non-app classes for testing purposes.
I was unable to finish all my tasks due to these issues, which took a lot of time to look into.
Although I learned a lot, I should have picked a smaller task.
I finished testing and implementing the sing in with email/password or google. Added some validation so that incorrect inputs would not break the program. Implemented ability to change for a use its' name and handle
I was not able to fully finish the task of linking user authentication with the profiles because of small bugs and catching up with last weeks task.
The takeaway from this week was I improved my code quality but my estimation of how long tasks will take is still lacking. Will try to improve for the upcoming week.
I implemented the typing game task. It was an exciting task, but too challenging to test. I've lost a lot of time on it.
In hindsight, I should take a smaller task for the next time.
On a positive note, we've reached a great milestone in the project with a well-designed asynchronous activity that allows the user to type its guess and help him with the automatic suggestions feature. (Stability with the API may be still improved)
I had two tasks this sprint: find API to fetch songs by tag and explore why Gradle does not work. I have found the Lastfm API to fetch songs by a specific tag and successfully used it in our app. This task was time-consuming, I did not manage to do my seconds task. Besides, we found a bug in Lastfm API.
In hindsight, I should be more specific on time, so I can manage all my tasks. Also, I wish Cirrus worked correctly.
On a positive note, I feel much more confident about my code. The code quality improve, I do understand testing part more, so I am happy about it.
I finished my task of fixing the issue of the untestable popup: I replaced it with an Espresso-testable layout, and this allowed me to reach 100% coverage. I also started my second task (implementing the logic of the scores update for the buzzer game screen), however I haven't had the time to test it. The popup fixing task from before indeed took a lot more time than expected due to issues with the CI and androidStudio.
In hindsight, I should have started the second task earlier on in the sprint, instead of spending too much time looking into technical issues.
On a positive note, these tasks helped me learn more about certain features of UI layouts and how to connect UI code to logic classes.
My original task was to find and implement a speech recognition API, then I discovered Android has a built-in class for it so I moved on to the lyric API. I first find one but it doesn't work as expected after spending some time on it, therefore I switch to another one. I implement the class and the tests, I got some problems with CI, sometimes the CI cannot build, sometimes it failed on some wired checks or because of my tests. But I got it works in the end. I have a minor task about setup the color theme for the app, too. But that one is not very important now and since I already had enough hours of work for this sprint, I decided not to do it.
This week we did not manage to solve all the tasks as planned. The main reason was internal issues with Cirrus and Github. It look a lot of energy and time trying to fix it, and reruning checks for PRs. Nevertheless, we managed to implement important features, and do a great job in general.
Our meeting are organized better. We are more efficient and straight to the point. Compared to last sprint, I feel everyone has a clear understanding of what to do and how to do.
However, we should better work on our time estimation. We have to take into the account the time we spend on github and CI.