✍️
Team FitBob
  • Introduction and Foreword
  • Motivation
  • Features
  • Tech Stack
  • Software Engineering Practices
    • Requirements
    • Software Design Patterns
      • Model View Controller (MVC)
      • Abstraction Occurrence Pattern
  • Deployments
    • Trying Our App
  • Activity diagram
  • Frontend
    • Login
    • User Registration
    • Client Screens
      • Client Dashboard
      • Client Profile
      • Eating History
      • Meals
    • Personal Trainer screens
      • Personal Trainer Profile
      • Personal Trainer Dashboard
        • Clients
        • Meal plans
        • Meals
    • Recipe screens
    • Search screen
    • Searching for Restaurants
    • Notes on BeautifulSoup and Flask
    • Request/Success/Failure Cycle
  • Backend
    • Notes on Django
    • API
    • Entity relationship diagram
  • Testing
    • User Testing
    • Backend
  • Project Limitations and Constraints
  • Closing Thoughts.
  • Project log
  • Poster
Powered by GitBook
On this page
  • Brainstorming
  • Prototyping the User Interface

Was this helpful?

  1. Software Engineering Practices

Requirements

Brainstorming

In the first stage of our prototyping process, we thought about what our end-users would like in our app and the gaps in existing nutrition apps that were possibly worth filling.

We then classified them according to 3 tiers:

  • Essential: Features that were critical for our app to have.

  • Typical: Features that competing apps commonly would have.

  • Novel: Features that competing apps didn't have/could have implemented better.

Name

Priority

Signup page

Essential

Login page

Essential

Caloric needs calculator

Essential

Food intake summary page

Essential

Food recipes recommendations

Novel

Restaurant recommendations

Novel

Trainer can send a link to their clients to sync their accounts/open a new account

Typical

Let restaurants list their menu on the app (with nutritional info)

Novel

Let users define their own meals (besides just Breakfast, Lunch and Dinner)

Typical

Kitchen Inventory tracker

Novel

Price getter for food ingredients

Novel

Prototyping the User Interface

Before we got to writing code, we thought it would be prudent to get a clear idea of what we wanted our app to look like first.

PreviousSoftware Engineering PracticesNextSoftware Design Patterns

Last updated 3 years ago

Was this helpful?

Thus, we drafted some screens that our final app would have using .

Figma
drafting screens in Figma