Inspiration
When you visit a town or city for the first time, you generally have no idea what it has to offer. And of those things, what would be suitable for the weather? Nobody wants to go apple picking if it's raining cats and dogs. And similarly, many people would prefer to spend a nice day outside rather than being stuck in some museum or gallery the entire day.
How it works
We figure out the user's location, and using that as well as a few different API's (Google Places, Wolfram|Alpha, and Weather Underground to give a few examples), figures out what attractions are indoors or outdoors, and uses that information to recommend a schedule for the user.
Challenges I ran into
Some REST API implementation was tough, and we quickly ran out of API calls for some APIs we were using Also, speed became an issue due to the things we had to do with events server side, on a free Heroku instance. Maybe that had something to do with that.
Accomplishments that I'm proud of
Creating a way to get information from a variety of APIs quickly and with a minimal number of calls.
What I learned
I learned more in depth JSON integration with Rails from using that to get information for the iOS app.
What's next for FitTrip
Preferably, an Android version. Also, we want to be able to recommend other attractions to the user based on tags from the attractions they visited. Maybe we could even get our own ratings system going.
Log in or sign up for Devpost to join the conversation.