Confused on database structure for fitness app

I’m working on turning a spreadsheet into a bubble application. Sort of like a fitness tracker.

In my spreadsheet in tab 1 is everything a user fills out and based on data entered on tab 1 there is another tab that displays the workouts for the week based on some simple math calculations. Then on day 7 the user retests on another tab which then provides week 2 workouts.

Tab 1 is done only once to create a baseline and week 1 workouts and every 7 days there is a re-test tab to create workouts for the following week. I’m seeing tab one as being a onboarding multi-step form.

Should I create a datatype for tab 1 called “user baseline” and then each of the rows is a field or split the rows based on themes such as “Endurance Baseline” and Location of Motion will be a datatype and fields nested underneath attached to that user?

Any help would be appreciated. Thank you.

Hi,

I understand you need help structuring your database. Do note that this structure will have an impact on app performance as well.

Your current tables would benefit from clarification because at this time it is difficult to grasp what is part of what.

In light of this here are a few questions and points to which I would need confirmation before making a DB structure suggestion:

  • each user has several “swimming”, each “swimming” has a distance and a time, and a week attributed to it
  • each user has several “running”, each “running” has a distance and a time, and a week attributed to it
  • each user has several “rowing”, each “rowing” has a distance and a time, and a week attributed to it

-What is the parent of your second table (in screenshot 2)?

  • Is LOM an attribute (of swimming, running and/or rowing?

Regards

Cynthia

Thank you for your response @cynthia.conrad1

Yes, to your question about each user.

Tab 1’s information results fill out tab 3 summary week one results. Once they are done with week 1 they click day 7 restest which takes them to the day 7 restest tab and those answers fill out week 2 workouts and so on.

This spreadsheet seems so cumbersome, I’m trying to wrap my head around the right database structure.