CSCI 5117, Fall 2024, assignment description
- Team Name: 20245117
- App Name: Easy Cooking
- App Link: https://project-1-20245117.onrender.com/
- Qinghong Fan, fan00123@umn.edu
- Linghe Wang, wang9257@umn.edu
- Zhiyuan Lin, lin00905@umn.edu
- Abdullahi Nor, nor00003@umn.edu
Describe the most challenging features you implemented (one sentence per bullet, maximum 4 bullets):
- Retrieving all recipe data from the database and displaying them based on the filter selected or similar keywords
- The logged-in users can create, edit, and delete their own recipes
- Checklist enables users to save the recipes they are interested in and print the ingredients in a PDF file
- Evaluating the nutrition information of each recipe through nutritional API and printing the info in a table on each recipe page
Is there anything special we need to know in order to effectively test your app? (optional):
- N/A
Add a screenshot of each key page (around 4) along with a very brief caption:
On this Recipe page, users can explore all recipes, and filter recipes based on the style from the sidebar or the filters selected in the filters block. Users can click on any recipe to view the recipe details as well as the nutrition info.
Users can type keywords on this Search page to search for recipes. All the recipes related to the keywords will be shown at the bottom. Users can also use the filter to obtain the recipes they want.
On the portal page, users can create their own recipes. When the users click on an existing recipe, they should be able to edit the info and then update, or delete this recipe. Users can only edit/delete their own recipes, but not the ones created by others.
When the users browse the recipe details, they can add this recipe (or multiple recipes) to the checklist if they want. In the checklist, the users can check/uncheck the ingredients if they are interested in them (e.g. want to buy them later). A PDF version of the checklist can also be printed out via the button.
There are a few tools for mock-ups. Paper prototypes (low-tech, but effective and cheap), Digital picture edition software (gimp / photoshop / etc.), or dedicated tools like moqups.com (I'm calling out moqups here in particular since it seems to strike the best balance between "easy-to-use" and "wants your money" -- the free teir isn't perfect, but it should be sufficient for our needs with a little "creative layout" to get around the page-limit)
In this space please either provide images (around 4) showing your prototypes, OR, a link to an online hosted mock-up tool like moqups.com
Add images/photos that show your paper prototype (around 4) along with a very brief caption:
This is the home page of the website.
This is the recipe page that shows all recipes based on user choice.
The next two pages are for the specific recipe including all information about this recipe.
This is the sign-up page where the user can create an account.
This is the login page.
This is the user portal page. After the user has logged in, the user can review, create, edit, and delete the recipes owned by the user.
This is the page where the user edits the specific recipe.
This is the search page.
This shows all relevant recipes based on keywords typed in the search bar.
Document integrations with 3rd Party code or services here. Please do not document required libraries. or libraries that are mentioned in the product requirements
- The Edamam Nutrition Analysis API link
If there's anything else you would like to disclose about how your project relied on external code, expertise, or anything else, please disclose that here:
...