When we were traveling internationally, it was very difficult to get directions without incurring data charges.

What it does

With TravelQuest, customers will be able to get turn by turn transit directions from point A to point B via SMS.

How I built it

Website – uses the following solutions Radix Domains AWS Route53 AWS Cloudfront AWS S3 – Static Website Javascript / html Mapquest Directions API Twilio API

SMS – 78657QUEST- uses the following solutions Twilio Webhook AWS API Gateway AWS Lambda Mapquest Directions API AWS Lambda Twilio SMS

Challenges I ran into

Web application: The website is hosted on AWS S3 static website fronted by Cloudfront content delivery, and Route53 for DNS, with domains provided by Radix. The calls are handled by customer browser js. The integration of the services was the major challenge. Mobile application: Mobile application is directly handled by Twilio. Backend calls are currently made to Mapquest APIs. The integration of the services and patching together multiple lambda calls was the biggest challenge.

Accomplishments that I'm proud of

Creating a scalable, reliable and robust serverless architecture for the website and the SMS solution.

What I learned


What's next for TravelQuest

Voice call with directions – will be an extension of the Twilio code Integration with Alexa, Siri, Google to perform advanced features Integration with Yelp, Foursquare, Google Places etc for location aware and information rich services Adding voice and text ads for revenue streams

Built With

Share this project: