Skip to content

projectproposal.md

Latest commit

 

History

History
104 lines (73 loc) · 5.94 KB

projectproposal.md

File metadata and controls

104 lines (73 loc) · 5.94 KB

Access Code 2.1 Final Project Proposal

Project Name
ChipChop

Team Name
ChipChoppers

Team Members
Madelyn Tavarez, Anthony Fermin, Alvin Kuang

Problem:

The problem that our app is aiming to tackle is the unfilled desire of users(Millennials) who are looking for a convenient way to enjoy an authentically prepared and home-cooked meal. This app will also serve as a MarketPlace startup for independent contractors that would like to sell their home-cooked goods to people in their communities.

Solution:

Our mobile app aims to create a platform that connects the 'users' with 'chefs' in their local community/neighborhood to deliver or pick-up authentic home-cooked meals! By doing so, this would also allow people to create real social connections with members of their local community, and familiarize/befriend those who live in their local area whom they might not have the chance of ever meeting in a vast city, such as NYC. People would have the ability to buy from and cook for people in their community and be given the opportunity to bond over that experience and/or the dishes they love. Repeat customers could form real connections with their cooks.

Competitors:

Web:

  • Josephine.com
  • Homemadegoods.com

Mobile:

  • Foodie Shares (Local to California)

Use Cases:

Consumers = Primarily working professionals (20's and 30's) who are too busy to cook, but wish to enjoy a convenient, authentic, freshly prepared home-cooked meal.
Providers = People who love to cook and would like to make some extra money on the side by sharing their cultural delicacies with locals in and around their neighborhood. (e.g. A stay at home mom who loves to cook and would love to contribute to the household income while staying at home to take care of their children)

Baseline Features:

  • Individual User accounts (Allow the users to create their own profile and store it within the Firebase cloud database with all relevant information to the user to allow easier future access to using the product with saved searches, etc.)
  • Profiles with user/chef information, location, photos and a live update of dishes currently available at the time (including any allergens)
  • Review system for all sellers (Similar to yelp's star ratings that would allow users to rate the chef in general)
  • Utilizing geolocation to locate local chefs and populate onto map (FOR FRESH FOOD!) also allow entry for zip code when searching as a backup for geolocation fail -DELIVERY: chefs can decide whether they want to deliver and/or allow pick-up users can filter through one, other, no preference

Bonus Features

-integrate FB login upon account creation to verify users are real and also traceable to a certain extent (Using the Facebook option provided by the Firebase API that will allow us to verify legitamacy of user/chef, and also provide a social platform for our app to be shared and marketed via media).

  • Credit Card Payments (To allow contracted chefs to conveniently receive payments and for users to conveniently pay for food)
  • Bluetooth connection when order is close by (Using Bluetooth LE to create a connection within 30 ft when the deliverer is outside the door of the recipient to provide a location-based alert notification)
  • Shake phone for random suggestion (Fun feature that would utilize sensors of the phone to sense when it is being shaken to randomly select a location and cuisine for the user when the user feels too indecisive to search for something specific but would like to enjoy a homecooked meal)
  • Responsive UI (That has the ability to change according to the time of day, Hunger Level, other parameters; simply to delight the user)
  • Create a website (Allow for multiple forms of access to our product on different device types to increase accessibility overall and convenience of use)
  • Using SendGrid API to send confirmation/forgotten password e-mails

Execution

WireFrame: Prototype - https://marvelapp.com/8c8iaa

Breakdown: *
*

Week Date Deliverables
Week 1 8/3 - 8/9 Ideation & Brainstorming Project Structure
--- --- ---
Week 2 8/10 - 8/16 Basic Functioning MVP (includes working profile accounts storing into cloud database, general UI layout skeleton)
--- --- ---
Week 3 8/17 - 8/23 Finalize functioning MVP, User Testing ,and begin bonus features (begin working on implementing bonus features as enhancements)
--- --- ---
Week 4 8/24 - 8/30 Finalize bonus features and UI/design and debugging/testing
--- --- ---
Week 5 8/31 - 9/6 First Demo and Implementing changes from feedback
--- --- ---
Week 6 9/7 - 9/14 Continue debugging / user testing and implementing changes from results
--- --- ---
week 7 9/15 FINAL DEMO

Roles and Responsibilities

####WEEK 1:

  • Alvin: Front End Design and Layout Skeletons and Basic functionality linked to Methods plus listView Adapter and xml layouts for it
  • Madelyn: Setting up and entering information to Cloud Database and User Login plus Database Helper Class and Objects classes for Addresses, Items, Orders, Reviews and Users
  • Anthony: Getting information from Database and implementing maps including getting users Location and functionality of reviews

####WEEK 2:

  • Alvin: - Shake phone for random suggestion
  • Madelyn: Credit Card Payments (To allow contracted chefs to conveniently receive payments and for users to conveniently pay for food), Facebook or Text Verification
  • Anthony: Using SendGrid API to send confirmation/forgotten password e-mails and track order via map or bluetooth

####WEEK 3:

  • Alvin: UI Beautify and Responsive UI (That has the ability to change according to the time of day, Hunger Level, other parameters; simply to delight the user)
  • Madelyn: Finishing Up Bonus/Testing/Debugging
  • Anthony: Finishing Up Bonus/Testing/Debugging