The Schedule Maker

Inspiration

The lack of productivity and increase of distraction in the world.

What it does

It gives the user a strong, well built sense of accomplishment as they advance from novice to nobility by completing daily goals. So, it serves a dual purpose of proudness and completing all your tasks

How we built it

We started with designing the home page with had a button and lead to the actual schedule, this home page would also contain the details about becoming a higher class. Then, we designed the page that the button would take you to. It consisted of the schedule in which the user would input all their goals for the day and then once they were completed they would come back to check it off, giving them ten points per objective completed. Afterwards, the user had an additional option to take their previous amount of points and spin a while. The goal of doing this was to add a sot of gambling that would make the game addicting so the user would continue to come back to the app. It would also ensure that they are getting all their daily tasks done. The spinner would make it so that they could either, based on what they landed on, gain or lose points. Each spin costed ten points.

Challenges we ran into

One of the teachers said that the fun in the hackathon was running into problems; if that's the case we had a very enjoyable time. The first problem that we ran into was that we could not decide what language/ program to use. We jumped back and fourth between Swift, Swift UI, Figma,HTML. JS, python, and more. Our second problem was that our syntax was really bad. So we would have to google some command midway. This lead to another problem, we were not always 100% sure on how to use it correctly, and repplit( the website we were using to type HTML/ JS code) would not tell us when we had an error or used a command incorrectly. Resulting in us having to decipher issues that we didn't know existed on our own. Another issue was that HTML is not the easiest code to parse/ read through, so after we had typed a lot and tried to go backwards into the code to fix errors or add things it took a massive amount of our time. Something that added to the tediousness of this is that our code was somewhat disorganized, with many excess functions and code. It was also very jumbled and was a real challenge to find things. All of these things compounded on to each other and made each problem even more difficult to solve.

Accomplishments that we're proud of

Considering the difficulty of each problem, we were very proud collectively when we solved each of them. The sense of proudness we got is similar to the sense of pride that the user of our interface will get when they reach royalty level in points. Also, HTML was not a language everyone in the team was totally familiar with so being able to still do a lot without even understanding the language is something to be very happy about.

What we learned

The main thing we learned was about problem solving and more about the coding language, HTML. Coding also requires a certain way of thinking in order to break past limiters, and we learnd more about that thinking process. As well, teamwork and team members were a huge advantage over the inconveniences we faced. This project could definitely not have been done without any one of our members.

What's next for The Schedule Maker

What's next for the schedule maker is actually the first idea for the schedule maker. We had originally made a design that would make it so that each user would get points and could buy stickers/ emojis that they can use on iMessages. This is a popular new thing for apps, and would have been a very good motivator for people to get their jobs done. Imagine getting work done and having an exclusive feature that you could do while talking to friends.