This week was very successful with lots of problem solving and actually coming to conclusions on some issues. I was able to get the writing function to work perfectly as intended creating a workoutId so I could easily look up and pull that information from the database and also logging the information in the database under the correct pathing. I wanted to work more on the writing function because before I was going to try and look up the workout from the date entered but that wasn't going to work with my method of reading because the data didn't have access to the workout information in the database, so instead I had it create a key, log that key, and then use that key to look up anything it needed to that the key covered.

My struggles this week relied on the reading function and there were multiple reasons for that but the main one was that it was originally using a date to look up the workout. Another issue that I was having with it was that the information being looked up was not updating and I found out later that the key being entered in the function to read workout data was not being saved and shared across classes so that didn't allow it to retrieve any information about the most recent workout logged. Finally I was able to create a sharedPreference that would allow both classes to have access to the variable storing the generated workout ID and that made finding the information that I needed to look up and read a lot easier.

I realized late that the function I am doing for the home screen, while cool, it actually doesn't have much use unless you are displaying across the whole screen. People often will do multiple workouts as part of a workout session and only being able to view one at a time would seem pointless. While I realized that it still was a good learning experience and project to work on so I continued and learned a lot about working with the database and learned a lot a lessons from my mistakes. If I were to do it again I would possibly find a way to create each workout stored under their date rather than a key so it can look up each date and then under that date, each workout can be stored under an ID. I think this method of approach would be successful because then you could have information on all the workouts that day and then if you want a specific workout that day, you can pull it with the ID. That way there is less clutter and also information is easily accessible. I would also just have this information displayed on a separate screen. We had good intentions when we originally thought of this idea for the app and I thought it would be cool but it is also impractical. I would just instead put an appealing button that could bring you to your workouts and then allow the user to check off what they have completed that day as kind of a progress check. This allows more options for creativity like adding a reward system along with a progress check, retaining user retention and making them feel like they are accomplishing something every time they check off a workout.