Planning for travel comes from the desire to travel from seeing a beautiful picture of the location or after finish reading the review on a particular site. There is an untapped territory of social content and user contents that is not well covered by the OTAs. Thus, there is a disconnect in the call to action from these content sites to the OTA's site.

What it does

Live as a browser extension that user can interact with. When triggered, the extension will look for the place of interest and location from the page images and it will display to user the possible locations from the content of the page. User can set the travel preferences and click on the location to display the list of available hotels that user can book. All this without leaving the site.

How I built it

Built as a chrome extension. only triggered when user interact with it - thus no performance overhead to user's browsing experience. Once triggered, it will inject its own html and UI, scan the images in the page and read the image alt attributes, and send it to the server which will check with google natural language API to detect LOCATION entities from the image descriptions. The location entities is filtered out based on its relevant scores. When user select a particular location, the location info is passed to Sabre Hotel Avail API call to get the list of available hotels for the particular location.

Challenges I ran into

Sabre API. absent of list of possible destinations to try. alot of missing data. alot of inconsistent data between hotel avail and hotel rate api calls. Working with chrome extension is challenging...

Accomplishments that I'm proud of

Chrome extension

What I learned

Check API days in advance.

What's next for Quivel

Apply to other industry.

Built With

Share this project: