What is this project?

The Idea

We always found that we end up asking ourselves "Where did all of my time go?" The weeks seems to fly by as we are wrapped up in classes, meetings, and work and hardly have a spare moment to ourselves. We, along with many others have become victims of our own work and our concepts of relaxing and leisure have been tainted by the constant need to feel productive. While we recognize our problem and its effects, we still have a hard time finding time to fit in activities we enjoy doing and fighting the feeling of "slacking off" when we do get a free second. To help address this problem, we created TimeTracker.

Why TimeTracker?

TimeTracker allows users to add activities they know they want to set aside time for. The idea behind initializing these before hand is to reduce or eliminate the feeling of nonproductive when engaging in these activities. If someone identifies an activity ahead of time to put on the list, surely this will encourage them that it is worth their time. Also, TimeTracker is not a reminder application. We felt strongly that flexibility with people's busy schedules was an essential characteristic and thus, with just a click of the mouse, progress can be updated. Progress on our webapp is based on percentages relative to the goals set by the users. This way, a user can update their progress easily and it doesn't depend on anything else other than the time spent on an activity which ensures that it is compatible with any schedule.

Evolution

Python and Terminal

We stared out by writing a program that prompted the user to answer specific questions and stored user input in a list. This became very limiting quickly since we could only ask the user one question at a time and it had to achieve through a series of simple questions. Being able to only store one piece of information at a time and asking the user question by question was not a very efficient way to collect data.

Flask and HTML

After drafting a primarily version of our idea, we moved on to integrating flask. We gained familiarity with using Flask-Forms and writing in HTML. This version was in improvement from the first; however we still didn't have a database to store the information and the add time buttons that appeared on the screen had no function. From here, we looked into establishing a database, creating a login system, and dressing it up with bootstrap.

Google Sites

Report abuse