1 min Pitch
Scheduling service for online dating companies to recommend coffee shops dates based on the user's calendar and their frequent locations.
We[bold emphasis]
Make it happen
- Dating websites should not just be a platform for discovering new people, they should take the pain out by organizing one on one dates.
Make it better
- Dating websites should give their users date recommendations based on their time slot and location.
Make it connect.
- Start a relationship with your users, connect with them and connect with us via web view from your website or your app.
Two Versions
- Mobile Web app
- Used by dating apps or websites to render our website as an web view or in the browser. Users get the options for emailing the final meeting location details. Also recommended location/times are sent back to the website in the response.
- Native app(Future)
- Used for personal use to schedule events/parties with your friends.
UI flow(Native and web based app)
- Open our website as an web view if you have a app or open the url if you are a desktop app.
- Give us their email and a redirect url of your website.
- We will take them to Sync your calendar page.
- After syncing, we ll ask them if they want to add/update their location
- We will show simultaneously the progress of the other person on the top bar of the website
- Wait till both users are finished importing calendar and location
- Recommend them the local cafes with the distance from their location at one of their free time slots.
- Redirect them to your app/browser with the recommend time and slots in the response body.
Data Model
- User
- userId [Type : String]
- userName [Type : String]
- userEmailId [Type : String]
- freeTimeSlotIds [Type : Array of timeSlotIds]
- Location
- locId [Type : String]
- locName [Type : String]
- Location [Type : int]
- Latitude[Type : int]
- Time
- timeSlotId [Type : String]
- time [Type : Json array of String]
- locId : [Type : locId]
- ResultObject
- userName [Type : String]
- timeSlotStringName [Type : String]
- locationName [Type : String]
- distance [Type : Int]
Backend API
- Create/Find API : Create or find the user with the given email and user's name
- Fetch Google Calendar API : Call the google calendar API and get the calendar slots for the next 1 week.
- Save the calendar API : Convert the data into a array of free time slots with each free time slot linked to a day.
- Save user location API : Make an api that will store the array of locations from the users.
- Get the longitude and latitude API : Give a address, get latitude and longitude from the
- Matching API : Input parameters will be two user's emails Ids.
- Get the free time slots array from the userIds
- Get the common timeSlotIds
- Fetch the locId from the timeSlotIds
- If the locId is same, call Yelp API to get at most 3 cafes
- If the locId is different for the timeslotId, call Yelp API for the locId and get at most 3 cafes for each locIds.
- Yelp API : Call yelp api to get the cafes near a location, takes longitude and latitude as an input parameter and return list of cafes. Persist at most 3 cafes in our location object.
- Distance API : Given two locId, get the walking/driving distance between them by calling google map API
Test Data[User]
User 1 |
User 2 |
|
|
Test Data [Yelp Places]
Location 1 |
Location 2 |
Location 3 |
|
|
|
Test Matching API[For the start up weekend, everything comes from the test data]
Match API : Input (user 1, user 2)
Output (array of ResultObject)
- [Test data from DB]Get free timeslots for userid1 and userId2. Common time slots is 123
- [Test data from DB]For each free common timeSlotIds and userId, get associated location. locId for the common timeslot 123 for both user1 and user2 is googPla1287E3
- [Test data from DB] Call Yelp API and fetch places near the locId "googPla1287E3". Returns a bunch of locations with latitude and longitude.
- [Mock]For each of the returned cafe locations, call google Maps API and calculate the distance between the cafe location and the locId "googPla1287E3". Make a simple distance calculations and fill the result object with location name, distance and user name.
- Return an array of resultObjects as below.
Test ResultObjects
<----- Tuesday [2-3 PM] ---> |
|
Jake |
Lily |
Recommend Places
|
Recommended Places
|
<----- Friday [7-8 PM] ---> |
|
Jake |
Lily |
Recommend Places
|
Recommended Places
|
Data Getters
Make wrapper for all the getters. Getters should obscure the source of the data, this will help us in mocking the API calls, the data can either come from the test database or from the third party APIs.