Overview Meal planner for the week

Description

Add recipes for each day of the week, get a shopping list to buy, share your week with others, follow or copy other people plan, create your own recipes or get recipes from the web or others plan.

Video demo

App Evaluation

• Category: Food & Drink
• Mobile: Mobile first experience
• Story: Allows you to create a week meal plan, create your own recipes, get a shopping list, copy other people plan or recipes
• Market: Anyone who wants to organize their meals.
• Habit: Users are constantly using the app to follow the recipe or to see the shopping list, each week the user will need to create a meal plan, this meal plan can be changed at anytime
• Scope: V1 would allow users to create recipes and add them to the week, V2 would allow users to see other people's plan, copy other people's plan or recipes.

Product Spec

1. User Stories (Required and Optional)

Required Must-have Stories

• User can create an account
• User can login and logout
• User can create recipes
• User can add recipes for each day of the week
  • User can search for recipes with a search bar
• User can see the shooping list of the week
  • User can add more things to the shoopíng list
• User can search for other user
• User can see other user profile
  • User can see week plan
  • User can see the other user personal recipes
• User can copy recipes from other user
• User can copy other person's meal plan
• User can see recipes from a database and add these recipes to his recipes
• User can filter the search of recipes by:
  • ...

Optional Nice-to-have Stories

• User can add a order food option to buy food from a restaurant or something like that
• User can follow other users
• User can get updates from other pople's plan
• User can save week plans to be able to use them later
• User can choose to have a private profile, which is not visible for anyone else
• User can click on a random generator button that will create a random week plan with random food.
• User can orginize recipes with tags
  • User can search recipes with tags

2. Screen Archetypes

• Login screen
  • User can login
• Registration screen
  • User can create an account
• Week screen
  • User can add recipes for each day of the week
    • User can search for recipes with a search bar
• recipes screen
  • User can create recipes
• Shooping list screen
  • User can see the shooping list of the week
• Social screen
  • User can search for other user
  • User can see other user profile
• Profile screen
  • User can see other user profile
    • User can see week plan
    • User can see the other user personal recipes
  • User can copy recipes from other user
  • User can copy other person's meal plan

3. Navigation

Tab Navigation (Tab to Screen)

• your week/shooping list
• your recipes
• search other users
• Profile screen

Flow Navigation (Screen to Screen)

• Login screen
  • Registration screen
  • your week screen
• Your week screen
  • shooping list
  • recipe details screen
  • saved recipes screen
• Saved recipes screen
  • recipe details screen
  • Online recipes screen
    • recipe details screen
• Social screen
  • User profile screen
    • User's week plan screen
    • User's saved recipes screen
• Profile screen

Wireframes

[Add picture of your hand sketched wireframes in this section]

Link: https://www.figma.com/file/ydaSJP7CCaMLQ4GeqtKAmZ/Food-planner?node-id=0%3A1

Schema

[This section will be completed in Unit 9]

Models

[Add table of models]

Model: User

Property	Type	Description
objectId	String	unique user identifier (default field)
createdAt	DateTime	date when user is created (default field)
updatedAt	DateTime	date when user is last updated (default field)
name	String	user name
lastname	String	user lastname
isPublic	Boolean	indicates if the user's profile is public to appear on the social screen
email	String	user email
password	String	user password

Model: Saved recipe

Property	Type	Description
objectId	String	unique recipe identifier (default field)
createdAt	DateTime	date when recipe is created (default field)
user	Pointer to User	user that saved this recipe
title	String	title of the recipe
imageUrl	String	url of the recipe image
dishType	String	The dish type a recipe belongs to
mealType	String	The type of meal a recipe belongs to
cuisineType	String	The type of cuisine of the recipe
totalTime	String	approximate time to cook the recipe
calories	String	calories of the recipe
recipeUrl	String	Url to the original site of the recipe
instructions	String	instructions too cook the recipe
ingredients	Array	list of ingredients
updatedAt	DateTime	date when recipe is last updated (default field)

Note: the online recipes will be obtained from Edamam API, when the user saves these recipes we add them to this table. Note 2: Edamam API doesn't have instructions, the user should add the instructions manually, but it gives you the original url for the recipe

Model: Week

Property	Type	Description
objectId	String	unique recipe identifier (default field)
createdAt	DateTime	date when recipe is created (default field)
day	String	day of the week
user	Pointer to User	user that added this recipe to his week
recipe	Pointer to recipe	recipe added to this day of the week
quantity	Integer	number of recipes
updatedAt	DateTime	date when recipe is last updated (default field)

Model: Item

Property	Type	Description
objectId	String	unique recipe identifier (default field)
createdAt	DateTime	date when recipe is created (default field)
name	String	name of the product
amount	String	amount of the product
updatedAt	DateTime	date when recipe is last updated (default field)

Model: Shopping list

Property	Type	Description
objectId	String	unique recipe identifier (default field)
createdAt	DateTime	date when recipe is created (default field)
user	Pointer to User	user that owns this list
item	Pointer to Item	Item to buy
checked	Boolean	Did you already buy the item?
updatedAt	DateTime	date when recipe is last updated (default field)

Networking

• [Add list of network requests by screen ]
• [Create basic snippets for each Parse network request]
• [OPTIONAL: List endpoints if using existing API such as Yelp]

• Login screen
  • (Read/GET) User authentication
• Registration screen
  • (Create/POST) Create a new user
• Week screen
  • (Read/GET) Query user week plan
  • (Create/POST) Add new recipes to the user's plan
  • (Update/PUT) Update the number of recipes
  • (Delete) Delete recipes from the user's plan
• recipes screen
  • (Read/GET) Query all user's saved recipes
  • (Read/GET)(API) Query recipes from Edamam's API
  • (Creat/POST) Save new racepies from Edemam library
  • (Update/PUT) User can edit his saved recipes
  • (Delete) Delete recipes from saved recipes
• Shooping list screen
  • (Read/GET) Query all user shooping list
  • (Creat/POST) Add new items to the shooping list
  • (Update/PUT) Update the item from the shooping list
  • (Delete) remove items from the shooping list
• Social screen
  • (Read/GET) Query users
  • (Read/GET) Query user's week plan
  • (Read/GET) Query user's saved recipes
  • (Update/PUT) User can copy other user's plan
  • (Creat/POST) User can copy other user's saved recipes
• Profile screen
  • (Read/GET) Query username and public profile option
  • (Update/PUT) Update public profile option

Ideas

• Use Hunter API to verify emails: https://hunter.io/api
• Use Youtube API to reproduce recipes videos: https://developers.google.com/youtube/
• Use kiwilimon API to get recipes or other API like edamam
• Add a button to each ingredient to search the ingredient in a store like walmart, and redirect the user to google with the search
• Use stores APIS to get the price for the products in the shooping list
• Filter recipes
• recommend recipes