✍️
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

Was this helpful?

  1. Frontend
  2. Client Screens

Client Profile

This page consists of the client's details such as his biometric details, personal trainer engaged, and other actions.

PreviousClient DashboardNextEating History

Last updated 3 years ago

Was this helpful?

As seen from below, when in the profile page, the client can do the following:

  • View biometric details

  • Edit his target calories

  • Contact his trainer

  • Add a trainer (If they do not have one)