BillyFit's Planner

• 

  The front page, where you can input difficulty and equipment.

• 

  Input for the days and time available each day.

• 

  The end results based on the user input.

Inspiration

I remembered that when I was first starting out on learning to exercise, I struggled a lot with trying to find and learn what exercises to make a plan for. While I eventually got past this, I realize that many others would either decide on a random plan that is unfit for them and cause them to quit, or that the initial planning to make one would cause them to quit before they even start. While this was initially thought up of to make for people more hesitant, we decided that it was also good to make this available for others as well

What it does

We first ask a couple questions in a form to be able to create it. We ask the equipment available, how experienced you consider yourself, and the times/days you have available a week. After also selecting what body parts to target, it then creates a weekly plan for exercises, along with reps and rest time as well. If we were to get a bit more specific, it passes all of what we asked into a backend, where it grabs that info, along with a csv file of exercises. It then creates the structure of what exercises for what days, how many reps, etc., and passes that back to our frontend to display.

How we built it

We built this using a React and Next.js frontend, with a Flask backend. We also have a csv file that the backend is also able to read.

Challenges we ran into

Some initial challenges we ran into at the start was, for one, what we wanted to ask of the user along with how we wanted to format this. We wanted it to be more simplistic for beginners to use and intuitively fill out, but still not so overwhelming that others more experienced would find this useless. We decided on a middle ground where there's a toggle for either a more balanced workout, or for something more targeted if you know what you're doing. Another challenge was figuring out how to structure what we wanted and trying to send them too, as the frontend people and backend people were working a bit more separate, so we had initial troubles on how/what we wanted to send things over to communicate to each other. We were able to get around this, however, by just taking a brief time to talk together to figure out what we wanted from each other.

Accomplishments that we're proud of

We're pretty proud of the frontend we made, where it's both simple but in-depth enough to be able to fulfill what we wanted, with sleek animations. We're also proud of getting over some of the challenges/hurdles, especially getting the frontend and backend to talk to each other.

What we learned

Some of the biggest things we learned was the connecting the frontend and backend together. Additionally, we also learned very well how valuable organization, planning, and structuring how we want things to be done before we start very critical. Diagrams especially helped us. For instance, we were able to get off on a very good start on doing almost everything, but our vagueness with connecting frontend and backend put us at a standstill for a while, especially when compared to how we did most of the other parts much faster.

What's next for BillyFit's Planner

Ideally, our next step is to incorporate potentially images or short gifs/video as better additional guides for exercises, to make this even easier for beginners to understand. Additionally, we would also try to structure the days better so it's understandable what the user's trying to get out of each day. An additional thing we wanted to add is another way to motivate people to continue with the exercises: A level system! It would help track whether or not they did the exercises, and rewards "xp" as a motivator and levels them up as a sign of progress!

Built With

• csv
• flask
• json
• nextjs
• python
• react
• typescript