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

Recipe screens

In this section we will be covering the pages related to creating, editing and viewing recipes.

PreviousMealsNextSearch screen

Last updated 3 years ago

Was this helpful?

Creating or Editing a recipe

This will be the standard format for adding a new recipe or editing an existing recipe. The only difference between the two is that if a recipe is being edited, the text input will be pre-loaded with the existing information about the recipe.

Viewing a recipe

The user will be navigated to this page when the view action button is tapped on a food item. In this screen, the user can look at the details of the ingredient, and even use the ingredient assistant, which we showcase .

here