jordansne / team3-gproject Goto Github PK

User can sign up for an account.

• Must login with Google/Gmail account.
• Cannot create an account if another account with the same email exists.

Frontend (Display signup/signin forms): Jordan
Backend (Backend APIs for frontend & database handling) : Khalil, Qiang

User can sign in to their existing account

• Log in through Google
• Password input must be hidden.
• User is able to log out

Frontend (Display signup/signin forms): Jordan
Backend (Backend APIs for frontend & database handling) : Khalil, Qiang

User can like recipes.

• Visual feedback shown to confirm like.

Note: liking and saving recipes combined into one feature.

Frontend (Displaying likes): Nathan, Kirk, Jordan
Backend (Backend APIs for frontend & database handling): Qiang, Khalil, Diana

After logging out, a grey square appears around the profile picture circle.

• Update Software Design Page (ie the UML diagram) to reflect the current state of code
• Update Project Plan with any new features since Stage 1
• Add instructions on how to build app & list dependencies to README.md

User can view recipe search results

Frontend (Displaying results): Kathryn, Nathan
Backend (Backend APIs for frontend): George, Ali

User can change the settings of their account.

• Can delete their account
• Can add dietary preferences
  User can set their profile picture Profile picture will be retrieved from google account.
  Can change their display name Display name will be retrieved from google account.

Frontend (UI forms to change settings): Jordan, Nathan
Backend (Backend APIs for frontend & database handling) : Khalil, Qiang

Search results display recipes relevant to the user's tastes, as indicated by the user's likes and favourites, higher up in the results list.

User can share a recipe via Facebook, Twitter, etc.

User can view similar recipes based on their saved recipes and/or most recent search.

User can specify dietary restriction on home page.

Frontend (Displaying results): Jordan
Backend (Backend APIs for frontend): George, Ali

"Write a brief description of the look and feel you want your program to have, or cite an existing design language (e.g. minimal, Material Design, flat design, etc.) You could also cite an existing application or website as a source of inspiration. Describe at a very high level how users will interact with your software.

This page should also include mock-ups of screens or views you plan to include in your application. You should use, at the very least, a vector graphics based drawing tool to create examples. You could also use photos of a whiteboard drawing as long as they are exceptionally clear and easy to understand. Better yet, why not search for a free mock-up tool online to generate these for you? You might find something useful.

No matter the format, ensure that your UI Design Page portrays the intended interfaces for all of your application’s user facing features, and how users will navigate between them."

"When your project proposal is returned, we may include under-specified features that we would like to see added. These will be under-specified in order to challenge your creativity. Use this page to propose any additional features your team would like to add to the project. Either in response to the returned proposal, or for something completely new, you must include:

• A title for the new feature or component
• A brief description
• A detailed and itemized feasibility statement and implementation plan
• A brief statement about the rest of the project’s dependency on this feature"

User can click on a recipe to view more information about a recipe

• Like count and users who liked this must be shown. (While database does track who likes what, feature considered unfeasible as too many likes on one recipe would be unnecessarily long and take up too much space.)
• Can see most recent comments; can expand to see all comments.
• Ingredient list must be shown.
• Nutritional information provided.
• Link to original recipe webpage provided.

Note: liking and saving recipes combined into one feature.

Frontend (Displaying recipe details): Kathryn, Diana
Backend (Backend APIs for frontend): George, Ali

User can explore popular/trending recipes.

Frontend (Display recipes): Kathryn, Kirk
Backend (Backend APIs for frontend) : George, Ali

"This page will outline the design of your project and will consist, for now, of a UML class diagram. More details below."

User can comment on recipes if logged in.

• Created comments must be displayed immediately.

Frontend (Displaying comments): Nathan, Kirk, Jordan
Backend (Backend APIs for frontend & database handling): Qiang, Khalil, Diana

"The page must include a list of all your team’s members and a brief summary of each member’s skills/background/hobbies/philosophy/whatever. You should also list any roles or responsibilities that have been delegated to members (e.g. Code Champion, Repo Hero, Database Ace, Team Overseer, UX Guru, etc.) Be creative!"

Clicking buttons on RecipeBox's on the RecipeGrid inadvertently triggers onClick for RecipeBox, opening it's details.

User can use the search bar to search for an ingredients on the home page.

• Clicking ENTER adds the ingredient to the list, and clears the search bar.
• Can click "Go" when finished adding recipes.

Frontend ONLY

"Include your team name and number (e.g. InterSlice - CS 2212 Team X) and a brief description of the project you are developing."

User can remove an ingredient from the list

• Ingredient must disappear from the list.
• List must be able to handle removing last item properly.

Frontend ONLY

User can save a recipe for later use.

• User must be logged in to save it
• Can access saved recipes from their profile

Frontend (Displaying saved recipes): Kathyrn, Diana, Jordan
Backend (Backend APIs for frontend & database handling): Diana, Khalil

If a search results in no recipes being found, an indication much be shown.

On home page, user is able to add ingredient when textbox is blank.

User can view suggestions as they type their search input.

User can specify meal type on the home page.

Frontend (Displaying results): Jordan
Backend (Backend APIs for frontend): George, Ali