routinimine

Finding your chronotype today makes tomorrow's work routine all play!

Comment

Inspiration

Over the last few weeks, I've seen the same ads popping up for sites promising better productivity when you download them and find your chronotype with them. These ads usually work on me and I usually find myself downloading these apps to see if I can actually find them (which I usually cannot since many mobile apps advertise only features locked behind a paywall). So, I decided to take matters into my own hands and made a very short quiz for people to find their chronotypes and their natural schedule as a result. This means that people can get this helpful insight into their programs without having to spend any of their actual money on it, and there is more information provided if they need it, as well as schedules that would help them out well.

What it does

routinimine is an app with the goal of finding a user's chronotype and a calendar closest to their biological one as a result. The user takes a short quiz that makes them think about their existing work choices and where/ how they feel most comfortable working and this gives them the result of their most likely calendar.

How we built it

routinimine was built using Swift and SwiftUI on XCode. After making a few sketches on paper, I booted up XCode and got to coding. StackOverflow was consulted many a time (honestly Devpost should add a way to add StackOverflow as a team partner because PHEW). After messing around with function placement, point systems, questions, and classes, routinimine was born! Many SwiftUI files were created and deleted, and many parentheses were typed, and I went to bed around 6 times since I started the last half of this project 3 hours ago, but who's counting?

Challenges we ran into

There were many challenges associated with this project. From changing the idea halfway through Day 1 to managing to miss all of the workshops I wanted to attend because of the PST time gap to having to attend an Indian party on the night of Day 2 (THEY'RE SO FUN BUT TAKE SO DANG LONG) and starting halfway through the project at 11 PM not even close to getting where I wanted to be, it seemed like routinimine was filled with these. I didn't want to submit something for this Hackathon that I did not think went with my original vision for the app: mostly based on chronotypes and getting your lives together with routines "made for you". There was also this mistake with the GitHub remote repo, and since I forgot to commit to the remote repositories as well, I had to scrap my first repository and create a new origin repository. There was also this weird thing going on with XCode where the errors would not disappear automatically when I resolved them so I had to give the entire thing a run every time I fixed an error even when I knew it was fixed so yeah, that was fun.

Accomplishments that we're proud of

I'm mostly just proud of submitting this project and having fun with it. I have been on a break from Hackathons for the last few months because my schedule has just been very busy all of a sudden, and I don't know if I'm fully back yet or not, but getting something finished really means so so so much to me. There were so many errors involved in this process and the lagginess of XCode made everything 10X worse (IT WOULDN'T LET ME INITIALIZE VARIABLES AT ALL! 😒) and so many times I considered ending this and going to bed, but I kept pushing. As I'm sitting here, writing my heart out in this posting section, knowing that I have some more experience under my belt feels incredible, and I can't thank you guys enough for such a creative theme that let me actually introspect and choose something that sorta relates to me. Me realizing I should have just put all of this in the Challenges section instead 😃 but N E ways 😎

What we learned

There were so many things I learned from this endeavor. I was able to grab a better footing in SwiftUI and mobile app development in general. I met many, many, many stupid errors along the way but I'd like to think I took it all very gracefully (as gracefully as I could as a 'Bear' chronotype at 1:30 AM). I also learned that planning and prepping before you start a project is not a complete waste of time since it can save you at least some of the many headaches that come with creating a project.

What's next for routinimine

The next thing for routinimine would be to add a more interactive schedule feature. This was initially part of the plans for this app, however, it fell through due to time constraints and a lack of relevant experience since this was my first real SwiftUI project. However, I would like to change this soon and not being able to find the right resources in time just makes me want to learn how to do this even more. I also think that everyone would agree with me when I say that the UI is garbage. I couldn't put enough time into it, so I would also 100% change that next, making it more personal and more likely to draw people in instead of just being so bland. I also hope that I can make a more accurate quiz with expert-asked questions since the questions right now are mostly just what I found from my own research on this topic.

P.S- Sorry about the video! My family was asleep. I also left another video link in the "try it out" section so you can see the program being demo'ed another time (PLEASE READ DESCRIPTION).

Built With

Share this project:

Updates