Quincy's Coding Journey

Written by: Quincy Williams After 4 months of production, our team, Scrum of the Earth was successfully able to create and finish or RepAdvisor application! We were able to successfully publish our app to the play store and it is currently available for download, via an early access version of the app. We have had many down times for the app, such as UI issues, merging conflicts and our lack of commenting the code as we should but there were a lot of things that wen right as well, such as never breaking the repository with those merge conflicts, successfully launching the application and having a good team chemistry to be able to make a great final product. The link to the application is under the RepAdvisor Page where it will navigate you to the application posting in the play store for download! Hoping to create more great projects in the future!

Written By: Quincy Williams This week, I was able to bring my attention back to exercise notifications for our application. We decided that the notifications were good but we wanted to take them a step further by having them be more intuitive and not as harassing by adjusting the notifications to go off based on the day of the week and if that day of the week matched a day that was in a current routine that was yet to be completed. Initially, the notifications were more generic and based off of the day of the week, so it would fire everyday except for Saturday and Sunday. This may have been seen as intrusive by the user and it was decided that adjusting the logic would make that feature more useful and not be instantaneously disabled by the user. To fix this, I needed to find a way to get the routines, and narrow down the routines to just their days and have the app check the current day, from the system time, and compare it to the days that the user set that they would like to do the ...

Written by: Quincy Williams This week, I continued to work on improving the User Interface and fixing a few bugs that were presented during our testing for build review. The main thing that I worked on for UI improvement was adding and editing exercises and fixing some issues with the initial design, as it was not the cleanest look. I was able to update the xml for the adding and editing functions to give a cleaner look of the activities but still provide some visual cues to the user on what can be clicked on and what is just plain text. The views were initially updated to have a card for every field but we decided that it made the design a little off putting and went with generalizing the fields into groups for a cleaner look. UI Update for adding exercises Now adding and editing exercises will have this new cleaner UI. The xml is updated to have the cards views hold more fields and now they have headers and the fields that are able to be clicked on are underlined, via edits to the st...

Written by: Quincy Williams This week we started the final month of development for our application and we are working the final push towards a final product. During this time, we are going to be strongly focusing on UI improvements to provide the best experience possible. Each of us are currently focusing on working on the pieces of the application that we felt, and users from testing felt, needed some revisions and cleanup. This week, I focused on updating the UI's for Timers, Body Metrics and Adding/Editing exercises. The first two portions were me making adjustments to the layout of the fragments so they are more compatible for smaller devices as much of the build has been created using a bigger device, so compatibility needed to be added into the build as well. There was an issue with how certain fields seemed cramped on smaller devices and looked normal on larger screens, so there was a need to make the views more consistent across device sizes and I was able to make xml adju...