Inspiration
We were inspired by how humans tend to find a way to connect and communicate even in the weirdest of ways. Thinking about how crazy it seemed for Vine to restrict videos to be a maximum of 6 seconds long, we wanted to come up with something similarly ridiculous, while still inspiring people to feel connected with one another.
What it does
Every day you can share one original quote with the world. Users will go through quotes selecting the ones they feel the most connected to. Whether it's humour, remorse, motivation, or otherwise, the most influential quotes will stand out and be forever remembered as the quote of that day.
How we built it
The front-end is built using React and deployed to Vercel. We designed the layout with Tailwind CSS.
The back-end is built using Starlette and deployed to Heroku. Our datastore of choice was Redis because it's very fast and was able to carry a lot of the weight with it's built in data structures (zrevrangebyscore!)
Challenges we ran into
In general, being able to create a working app in one weekend was a pretty big challenge for us. This is only our second Hackathon. We had a lot of issues with CORS... but we don't really want to talk about it. Sending requests to the back-end to fetch data dynamically gave us a bit of a pain. The prototype doesn't work on Safari...
Accomplishments that we're proud of
- We're all pretty proud of finishing the prototype in time.
- We got enough sleep.
What we learned
- We all got to brush up on our React skills, or learn a little more about React itself.
- We definitely learned a little bit more about CORS and why it exists (even if we're not happy about it).
- We practiced some better methods of organization and time management.
What's next for Kwot
We eventually plan on moving the app off of React to something more cross platform like Flutter. Our original intention was to make Kwot into a mobile app, but building a simple React web app was faster for the purposes of this Hackathon. We have a lot more features planned as well, but there isn't much reason to get into that right now. We also discussed moving the back-end over to serverless, because it can scale on the fly and is more cost effective. We also talked about using a serverless datastore like DynamoDB or Cosmos... but that would mean dropping Redis.
Log in or sign up for Devpost to join the conversation.