Lauren Dyson, Christine Chung, Paul Mack, Leith McIndewar

https://docs.google.com/presentation/d/1ZxHKsRMSGbwFMtpbUibnd6yFMMpW3dBG5YCZxZcA2YM/edit#slide=id.g107979916d_0_182

Meet Halfway helps Chicagoans find a place to meet safely and securely. Our algorithm makes it easy to find a place to meet a friend or stranger that's convenient for both of you.

Given two starting locations, preferred modes of transit, and a desired type of location (coffe shop, restaurant, park, etc.), Meet Halfway finds a meeting destination with roughly equal travel times for both parties. Meeters have the option revealing their location to the other person or not; this way a meeting location can be agreed upon while protecting privacy.

• As a Craigslist seller, I want to arrange a meeting place with a potential buyer at a halfway point without revealing my location.
• As a U Chicago student, I want to meet my friend who lives on the north side at a coffee shop that’s convenient for both of us.
• As an online dating service user, I want to find a bar where I can meet my date without revealing my location.

• Google Maps & Distance Matrix API

• Google Places
• Yelp API

Jan. 24

Repo Created

Jan 26 at 5pm

Written Proposal: One or two page proposal that describes the goal of the project and the source of data the group will use. It should also give a basic sketch of the work required to complete the project and a time-line for completing it. The proposal should also include a description of how the group plans to fulfill the third condition listed above.

Proposal Presentation: Ten minute presentation that describes goals and plans.

Wireframes completed

Week of February 8

Deliver MVP of distance identification: Given two addresses and modes of transit, we can identify a meeting point that's roughly equal travel times for both (Main owner: Christine)

Progress Check-in: Each group will meet with an instructor for 15-20 minutes once during sixth week and again during eighth week to discuss the group’s progress, challenges, and plans.

Week of February 16

Deliver MVP of user interface: Working prototype of frontend that allows user to input two locations / parameters at once (Main owner: Leith)

Week of February 22

Deliver MVP of location identification: Given a meeting point, identify K locations meeting user requirements within a radius (Main owner: Lauren)

Progress Check-in: Each group will meet with an instructor for 15-20 minutes once during sixth week and again during eighth week to discuss the group’s progress, challenges, and plans.

Week of February 29

Deliver phase 2 MVP of user interface: Working prototype of frontend that allows users to separately enter their locations and view a result (Main owner: Paul)

Week of March 7

Usability testing: Working complete prototype that we can test with users

Week of March 10

Final Project Presentations (10th week): Each group must give a 15-20 minute presentation describing its project. The presentation should include descriptions of the project’s goal, the results obtained, and how the system is structured, along with anything interesting the group has learned in the process of building the system.

March 15 at 5pm

Completed Software: Each submission should include a description of how to run the software and should be well documented. We must be able to compile and run your program(s) on a VM and we must be able to understand the structure of your code without undue effort.

• Data & Algorithm
  • Middle Finding Algorithm
  • Google Maps API
  • Google Places API
  • Yelp API
• Backend and Database
  • Django
• Frontend
  • Bootstrap
  • Javascript
  • CSS/HTML

• Python
• Backend
  • SQLite