Inspiration
During lockdown our friend group started to drift apart due to the difficulty of scheduling things with people whose schedules are diverging. As a solution to this problem, we decided to create Social Motion.
What it does
Social motion people to upload their schedules and add their friends, which then allows Social Motion to output a list of people currently not busy and available to hang/party/ect. Eventually Social Motion is intended to expand its functionality into other scheduling capabilities to keep it relevant as lockdowns end and normal scheduling resumes.
How we built it
First, we focused on building a backend to interface with the database and designing our frontend. Once this was finished, we began implementing the frontend and bugfixing the backend as we went.
Challenges we ran into
The initial scope we laid out for ourselves was far too large for a two day hackathon. Therefore, we had to scale back our aims and keep some of the scope for implementation after the hackathon. Additionally, much of the language and technologies we used to create this, many of us were either were unfamiliar with, or had not used in a long time, so we had to learn/relearn much of it.
Accomplishments that we're proud of
Creating so much content and so much code in the two days of our first Hackathon was incredibly rewarding. Additionally, being able to learn new skills and identify useful areas to improve was also useful.
What we learned
All of us developed skills in the languages and frameworks used, such as JS, SQL, database management, NextJS, and more. We also learnt lessons as to better order of development, as some of our choices were rather sub-optimal.
What's next for Social Motion
We intend to expand the functionality back up to the original scope and beyond in the next few months, to eventually make this a full functioning app.
Built With
- amazon-web-services
- mysql
- nextjs
- react
- sass
- tailwind
- typescript
- vercel
Log in or sign up for Devpost to join the conversation.