Optimize Read/Writes to DB

[GabrielJDavila]

I'm having too many read and writes to firestore in a given workout. I think the best way to optimize this is:

• As soon as a user starts adding exercises to current workout, it get's added to local storage. From there I can have them use a "save" feature to save the workout to the DB, or automatically save the data after a certain period each day (the latter should only work if there is current data to save).

[GabrielJDavila]

Some notes:

• I've added functionality to when users click "add exercise" that adds the exercise to local storage.
• I'm pulling those exercises from local storage in WorkoutLog.jsx ans saving in state.
• Now I need to add functionality to add sets, delete sets, and delete exercises from local storage.
• Once the user is finished with their workout, they can hit "save workout" (need to create this) which then saves the workout to firestore.
• Also when the day ends, if user hasn't saved workout yet, it will save automatically if at least once exercise is logged.
• This process should help the amount of read/write queries to firestore, and hopefully optimize loading of data.

[GabrielJDavila]

Notes: Local storage definitely is faster, but a problem is that the same data persists even if I change dates. I need to add a date property to the data. Or, I could: initially save workout data to firestore when user is picking their exercises. When that data is initially pulled from firestore, save it to localStorage. Modify that data in localStorage (sets/Reps, notes, etc.) When the user finally saves the workout, then the data is sent back to firestore. If the user adds a new exercise, check to see if the localStorage item exists; if it does, then add the exercise. If it doesn't, add it to firestore first to initalize a new workout.