MonkeyMeet

Inspiration

Our inspiration lies in the struggle of trying to organize meetings between people with vastly different availabilities and the shortcomings of current schedulers available online. All of our members have seen a need to use these schedulers to organize a gathering, whether it be for study groups or birthday celebrations or practices for a dance team. However, current scheduling websites such as LettuceMeet or When2Meet have outdated, clunky UI and poor systems for scheduling new meetings within the same group of people. We wanted to create a much more efficient and organized alternative to these website, one that we would all be able to use to make scheduling gatherings much less stressful.

What it does

MonkeyMeet is a scheduling website that, unlike competitors, allows you to centralize multiple schedules under one user account for easy access and allows you to re-use a schedule for a group instead of creating an entirely new schedule. A user is able to join multiple groups, consisting of different members as needed. Up to twenty users can join a group, where easy-to-differentiate user schedules, the ability to view planned meetings, and easy access to editing meetings/schedule dates help to keep group activity organized and up-to-date. This structure will allow for users to keep plans organized with multiple groups indefinitely and helps prevents the confusion of managing numerous different links from different services.

How we built it

MonkeyMeet was developed with the T3 stack (tRPC, Tailwind CSS, TypeScript) using Drizzle. Turso (SQLite) was used for database management, and the front-end of the application was built using React.js. We chose tRPC to be able to easily develop typesafe APIs and to have the opportunity to learn something new.

Challenges we ran into

The main challenge we ran into was a lack of documentation. The T3 stack is fairly new, so our members struggled to troubleshoot the issues that arose and to find resources to learn from. Additionally, some members did not have have a strong foundational background in technologies related to this stack. Both of these challenges led to issues while programming, and one member of our team ended up taking on a large amount of work to make up for knowledge differences.

Accomplishments that we're proud of

An accomplishment that we are proud of is being able to create something that is [fully] functional with a stack that none of us had any knowledge on prior to the hackathon. Although it was very frustrating at times, we are proud that we were resilient enough to see our project through to the end.

What we learned

All of our members learned a lot about not only the T3 stack, but also the technologies that work concurrently with it. Several members were able to learn parts of the stack and new technologies that they had never worked with before. Altogether, we were all able to improve our skills in full-stack development by creating MonkeyMeet.

What's next for MonkeyMeet

In the future, we plan to continue to polish MonkeyMeet's functionality and improve cosmetics that we were unable to complete during the hackathon's time limit. We want MonkeyMeet to become an appealing alternative to other scheduling apps, and we hope that we will be able to deploy MonkeyMeet and have it reach a large number of users.