generated from mwc/project_banjo_app
Worked on views and models
This commit is contained in:
@@ -5,7 +5,7 @@ The app's target user is a person who struggles with planning what exercises to
|
||||
|
||||
|
||||
## 2. What need or problem will your app solve? How do you know this is really a need for your target user? How does the target user currently deal with the problem?
|
||||
This solves the problem that my current workout tracking app costs money (or I have to watch annoying ads while I'm trying to log information). Currently, I just turn off my data and internet when I'm in the gym to override the app and keep the ad from loading, but this means I don't get notifications from my other apps and I can only listen to the music I have downloaded. Currently, I just do the same exercises over and over, and it gets really boring, or I waste time searching for new workouts that I don't ever try. Eliminating the mental load of choosing a specific workout will help me (and others) be more likely to actually go to the gym.
|
||||
Currently, I just do the same exercises over and over, and it gets really boring, or I waste time searching for new workouts that I don't ever try. Eliminating the mental load of choosing a specific workout will help me (and others) be more likely to actually go to the gym.
|
||||
|
||||
## 3. How will your app's design meet the need you have identified?
|
||||
I will create a bank of exercises sorted by what muscle group they target and that have attributes for weight, reps, sets, or time. I will have a path that allows the user to add their own exercises as well. I will support returning a random exercise based on the muscle group it works. I will also support updating the recommended weight, reps, time etc for each exercise.
|
||||
|
||||
Reference in New Issue
Block a user