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

This page is where clients will be able to see the circular progress bar, weekly caloric intake, and also access all other pages from

PreviousClient ScreensNextClient Profile

Last updated 3 years ago

Was this helpful?

The Circular progress bar is constantly up to date with the clients' current calorie intake. In the event where the client exceed the calorie intake, the progress bar and the chart's bar for that day will turn red.

The below gif will showcase the seamless transition between the dashboard page and the profile page, together with the buttons that allows the user to navigate to other pages.

Dashboard page