BW - Weight Lifting Journal

Proposal

• What problem does your app solve?

  • Record keeping, memory, substitutions
  • Organization
  • Go-to app for all things weight lifting

• Be as specific as possible; how does your app solve the problem?

  • Users can log in and can create, review, update, and delete data on their workouts .
    • Can create a name of the exercise, amount lifted and/or reps completed, date, and region of the body exercise targets.

• What is the mission statement?

  • Easy to use, convenient, accountability

Features

• What features are required for your minimum viable product?

  • CRUD operations, name of the exercise, amount lifted and or reps completed, date, region of the body, etc.

• What features may you wish to put in a future release?

STRETCH GOALS

- Reminders
- Social media-ish things, likes, comments, shares, etc.
- Goal setting
- Mapping
- Recommendations
- Visual comparisons
- Cardio section

• What do the top 3 similar apps do for their users?
  • Mapping, likes, comments, shares

Frameworks - Libraries

• What 3rd party frameworks/libraries are you considering using?

  • Material UI

• Do APIs require you to contact its maintainer to gain access?

  • No

• Are you required to pay to use the API?

  • No

• Have you considered using Apple Frameworks? (MapKit, Healthkit, ARKit?)

  • Yes

Target Audience

• Who is your target audience? Be specific.

  • People who lift. Gymgoes, weightlifters, etc

• What feedback have you gotten from potential users?

  • Make it easy to use, organized, good UX & things mentioned in stretch goals

• Have you validated the problem and your solution with your target audience? How?

  • n/a

Research

• Research thoroughly before writing a single line of code. Solidify the features of your app conceptually before implementation. Spend the weekend researching so you can hit the ground running on Monday. Prototype Key Feature(s)

• This is the “bread and butter” of the app, this is what makes your app yours. Calculate how long it takes to implement these features and triple the time estimated. That way you’ll have plenty of time to finish. It is preferred to drop features and spend more time working on your MVP features if needed.