Sage | Devpost

Inspiration

We as a team noticed that being burdened with scheduling and delegating time for tasks was one of the biggest issues we dealt with in school, both in terms of misplacing time on low-priority tasks, and in being

What it does

The user creates tasks, with each task having the parameters of name, priority, due date, and progress. After putting in all the tasks, our custom algorithm organizes the tasks in order and returns a schedule for the day to follow

How we built it

First we discussed ideas for what the project would be based off of the prompt, and after considering what we struggle with in our daily lives, we came up with the idea and decided on creating an app in typescript using electron, and then after that we started planning features and setting them up in order of priority of implementation, then we all cooperated on figma to create the UI design that would be implemented using Tailwind CSS, and after that we started working on the algorithm. Finally, when we finished both the frontend and backend separately, we merged them together so that both work in unison to create a fully functional app

Challenges we ran into

One of the biggest struggles we dealt with was having to work around our unpredictable schedules, which meant we had to squeeze more work into shorter periods of time, something we had attempted to avoid but ultimately had to overcome

Accomplishments that we're proud of

None of us mainly work with Typescript, and we all had little to no experience in the technologies we were working with, so it is something we take pride in that we managed to optimally use several of the most modern and future proof technologies to make our app as good as we could

What we learned

We learned how to use typescript, as well as implementing it in nextjs, tailwind css, and electron, and this has resulted in us wanting to cooperate on more projects

What's next for Sage

We plan on working further to polish the UI to a maximum quality mainstream production app, as well as implementing some of the features we had considered but were ultimately too complex or time-consuming for a 2-day hackathon, as we all see potential in the idea behind the app, and are, as a result deeply invested in