Inspiration
During the college football season, Matthew, Alee, Raleigh and Roman were all parts of separate College Football Pick Em's groups, where the commissioner of the group would create separate lists where participants would make their selections, then manually upload the winner of the games into an spreadsheet in order to determine the winners. Spending hours every week manually uploading this information is extremely time consuming, forcing us to spend too much time pouring over spreadsheets and not enough time enjoying each others company and the game of Pick Em. So, we built Qwyck Ems, the Quick Pick Ems Builder that will automatically build the games and record participants' selections, generating rankings for each league. Rather than Pick Em becoming a chore that takes over 3 hours per week, we have turned it into something that we can enjoy for fun in seconds!
What it does
Functionality so far: Fully created backend Fully created front end Not really created endpoints :p
How we built it
Front end: React. [roman type stuff here] Back end: flask and mongoDB. When it came to mongoDB, we genuinely wish we had just used SQL instead. The UI was confusing, and with SQL it would've been easier to make the connections needed. However, after WAY too much searching through tutorials, we found out how to build our database from the ground up, and automate calls to the database, both to build new objects and search for existing objects. After modeling the database to be based off .
Challenges we ran into
ENDPOINTS ARE CONFUSING! One of our group member's laptops was completely busted so we needed to completely set up a computer with git, required software, sign-in information, etc. One of our members was called out for an emergency after the first 12 hours, so we needed to readjust all of our task planning and take on much higher workloads.
Accomplishments that we're proud of
Built our first ever database that's fully fleshed out Used React and flask, frameworks which we had never used before
What we learned
Full stack development is quite a challenge, but it is doable provided that you know how your back end speaks to the front end, and vice versa. Without the medium for them to communicate on a single machine, it is very difficult to attempt to run and debug across several instances.
What's next for QwyckEm's
We have the code for finding information from the NCAA on college football scores, but we'd need to test to correctly integrate it with QwyckEms, just so it doesn't cause any bugs. Eventually, we would love to continue to develop this into a fully-fleshed website that others can actually use.
Our github page
https://tubaleelo.github.io/Hacklahoma25/
Log in or sign up for Devpost to join the conversation.