-
logo
Inspiration
We wanted to utilize Cincy Open Data, and compete in the 'Feed the Human' category. Once we realized Cincy Open Data had a 'roadkill' data set the idea just came to us and we ran with it. Ran very very hard.
What it does
Coordinates pop-up culinary competition events centered around a fixed number of ingredients and whatever nearby fresh roadkill the participants can find. App provides facilities to submit & judge meals, and find the aforementioned fresh roadkill to use in their dishes. Yum!
How we built it
The app is mostly Angular.io with a Firebase backend. To import the VERY IMPORTANT & CRITICAL roadkill data from Cincy Open Data, there is also an external scraper agent written in Ruby. Google Maps APIs are used for functions such as directions to roadkill. Both components of the system are distributed as Docker images, allowing for easy deployment on a wide range of infrastructures.
Challenges we ran into
Firebase was a new experience for the team, and it was challenging to figure out how to integrate with it in a hurry. We had similar issues with integrating with Cincy Open Data. All around the team really stretched to learn new skills & tech we hadn't touched, or at least used extensively before. Backend devs slung angular code, we all learned how kludgy Firebase is to work with data.
Accomplishments that we're proud of
We managed to almost entirely eliminate the external server component.
What we learned
Firebase doesn't allow not-equal queries.
What's next for Project MeatUp
Syndication. Also, we're going to win the shokugeki with our squirrel dish.
Log in or sign up for Devpost to join the conversation.