We created a tool we'd like to send back in time to our previous selves to help us work on this hackathon. It would have cleared up misunderstandings and eliminated duplication of efforts.
Like many previous hackathons before this one, our team was beset by fits and false starts. One person enthusiastically supported a method of building a piece of the project and then flaked out and never showed up again. Another person only spoke when asked direct questions but never asked the other members about their role in the project.
As patience grew thin and nerves began to fray, we shared horror stories like "This isn't going so well but it could be worse." One of our team members was in a hackathon where all the prize money was sent to one person. That person never paid anyone else on the team. Who does that? Now it doesn't matter because we've got a solution to that problem and we included it in this "magical, time machine, hackathon solution."
What it does
Our application has a few functions with the primary goal of easing the process of finding and creating teams, increasing transparency and accountability among hacker teams, as well as helping teams reach their goal of final submission.
See app here https://fly-tv-leelakrishnan.vercel.app/ See App video here: https://www.youtube.com/watch?v=V_g3QdggliQ&feature=youtu.be or Here https://www.canva.com/design/DAE65GfgIcM/fEG16Oaf80oxCAA-ELuGqg/watch?utm_content=DAE65GfgIcM&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton Please read this ReadMe https://github.com/leelakrishnan/FlyTV/blob/main/README.md for more information.
This includes: Setting up a profile, which you can use to apply to teams, as well as a function to view the project dashboards of other teams to evaluate whether you want to join them. Teams can be created, as well as have the ability to accept or reject applicants for their team. The profile is meant to reduce the repetitiveness of filling out profiles to apply for hackathons, meaning a user can use this application to participate in several teams for several hackathons.
A team info to encourage teams to think about their shared mission and vision statements and define if they are still looking for team members.
An option to add a Github Repo, Git Project Management link, and a Project Guide via the page Project Man to encourage efficient working and structure.
Multi sig wallet, which improves trust and transparency in the teams and avoids mishaps where one team member can "steal" prize money without sharing with team members.
A dynamically created Gathertown space, which we generate using GatherTown API. We want to encourage teams to use this setting while working to make teamwork in different timezones more collaborative. Teams can edit their GatherTown spaces.
An option to Mint their Project to an NFT Storage after the completion of submission as proof of work for their efforts during a hackathon. This is also useful for hackathons that do not have a space to showcase projects.
A DAO to make create and vote on proposals for the team project. The voting structure encourages teams to easily make decisions without having to coordinate meetings but also increases transparency in the collaboration and decision-making process of project development. Each team member receives 100 Tokens, which they can use to propose ideas. Whoever implements the idea then receives that token.
A Fun Page that includes a meme generator for fun, which we encourage teams to use to lighten up the mood or warm-up before meetings and share a few laughs.
How we built it
We used a wide variety of tech stacks. This includes NextJS for the frontEnd, Web3Auth for authentification, Solidity for the smart contracts, Moralis for the database and IPFS storage, NFT Storage for minting projects, Rinkeby as a testnet, GatherTown API for the dynamically created GatherTown space
Challenges we ran into
We created this application due to the challenges we faced in previous hackathons and team group work. It would have been lovely to have this type of tool before we started. Our biggest challenges included onboarding and losing multiple team members during the process, as well as not having accountability for who does tasks. We did not have a designer or front-end CSS skilled member in the team. The ideation phase was grand, but we had difficulty scoping down the project, as they were so many features we wanted to implement. Especially the decision making of what features to implement was difficult. We attempted to create a voting Excel to make decisions, but due to the text load and inability of some people to take the time to go through other people's work, properly use this tool. Hence the DAO function, which is a much more simplified version should encourage more efficiency in this regard.
Accomplishments that we're proud of
This application and the core team we were able to build.
What we learned
The more the merrier is not always the best for hackathon teams. Teams should be limited to a size of 3-4 people. Group work is hard, but especially hard online with different time-zones and different skill levels as well as different levels of determination and willingness to work.
What's next for Flight V
Flight V has many features that have not been realized. We created the project to be open-source so that anyone can contribute and add to an application that could improve all our experiences of hackathons.
Log in or sign up for Devpost to join the conversation.