This app enables the Telos Labs team to keep track of good habits and have a record of the days they're succeeding in completing any given task.
-
Ruby v2.6.6
-
Ruby on Rails v6.0.3.3
-
PostgreSQL v10.14
-
Bootstrap (including jQuery and Popper.js)
-
The app can create different activities (habits)
-
Each activity provides the option to pick a date and mark the activity as completed on the selected date
-
The app keeps track and provides records of: Which activities were completed on any given date. On which dates any specific activity was marked as completed
Currently, the app allows users to log an activity during dates before the activity's creation and posterior to the present date. Ideally, this would not be allowed, but for demo purposes, it is now enabled so you can test logging activities on different dates without having to wait for a few days to pass so you have a wide range of days to log activities.
The app includes a “current streak” feature which lists the logged activity for every habit in the last 5 days. This feature takes into account the date the activity was created, if the activity is less than 5 days old, the feature will only show the currently available data.
If an activity is marked as complete on a date from before the date the activity was created, that record won't be taken into account for the current streak indicator.
I used 3 models for the creation of this app: habit, day and log.
I took this decision so that the app can retrieve information in a bidirectional way. The app can get which dates are attached to a specific activity, meaning which dates were this activity logged, and it is also able to get activities logged on any specific day, this way enabling the user to check how productive any given day was. The log model works as a join table between day and habit.
By doing it this way, adding a new user model in the future becomes simple. All the habits that belong to a certain day can be assigned to that given day, disregarding which user is the actual owner of the habit. Showing the correct habits to the current user would be just a matter of adding an extra layer of filtering to the habits belonging to the selected date.
To keep the app simple and to try to stick to the 15 hrs time frame, I decided to currently not allow habits to be updated or deleted, the same goes with days, but in a fully-fledged app, the days would automatically be deleted when there were no habits linked to them, without the need of user interaction.
I also decided to make use of Bootstrap to create a good looking front end fast, without having to invest so much time in it so that I can focus more on the backend.