-
Notifications
You must be signed in to change notification settings - Fork 0
Application Overview
The “Productivity App” is a web-based application designed to enhance the user’s productivity. The app is based on productivity applications like Asana and Habitica:
The app will have different sections:
- Todo section
- Dailies section
- Learnings section
- Blog section
Each of the first 3 sections will combine user input data, tracking of the users progress and visualization of the user’s data.
The Todo section will have a todo list UI where the user can add their todos for the day. The user will be able to add todos so they appear on a todo list right beneath the todo input. The user will be able to submit todos by clicking on a "Add todo" button or by pressing enter. The todos text will have a 40 character limit. The user will be able to mark a todo as complete, in which case it will disappear from the todo list and will appear on the completed list. The user will also be able to remove the todos by clicking on a delete button on the todo, in which case the todo will disappear completely.
The user will be able to edit the texts of every todo after having input it. The user will also be able to re-order the todos on the list, dragging them up and down as he wants.
The user’s number of completed todos for the day will also be displayed somewhere in the UI and also next to it will be displayed the average number of completed todos per day. This way the user will be able to know if he has completed more todos than on an average day.
Also somewhere on the UI close to the previous 2 elements there will be a third element. This element will be a percentage increase/decrease indicator that will display the percentage comparison between the user’s current number of completed tasks and the average number of completed tasks per day.
If the user has completed 10% more tasks than the average day a “+10%” text will be displayed. If he has completed 25% more than the average a “+25%” text will be displayed. The same applies in case the user has completed 10% less or 25% less than the averages.
The percentage steps that will be calculated will be: 5%, 10%, 15%, 20%, 25%, 50%, 75%, 90% 100%.
Dailies are user’s todos that are all the same day by day and the user has to complete them once every single day. A daily task might be to workout, to meditate, to perform gratitude practice, to feed the cats. Like Habitica’s dailies, our dailies need to be performed once per day.
The dailies section will involve an input field and a dailies list, just like the todos. The difference being that when a daily is set as completed it remains in the dailies list only that is now displayed grayed out or inactive. Once the next day starts(to be determined what constitutes next day start) the daily will become active again and it will be possible for the user to set it to complete again.
Dailies will also display a streak counter which will display for how many days in a row the user has completed that specific daily.
Learnings are things users have learned during a specific period of time(to be determined what a specific period of time is) that can help him improve his productivity. Learnings can be:
- Do yoga everyday to relax
- Make schedules for weekend work
- Make a weekly schedule
- Check weekly schedule everyday to keep on track
- Do not work on tasks outside the ones on the weekly schedule
- Play less video games
- Watch less tv
- Etc
The point is to add these learnings on how to make the day or the week more productive after the determined period of time, in order to improve on the next period of time that is coming. If we are talking about 1 week being the period of time, perhaps the user watched too much tv or binged on a netflix series this week. He would then go and add a learning method like “watch less tv” to his learnings.
The learnings will be added with an input field similar to todos and dailies.
The difference will be the following: when todos and dailies are displayed in a list beneath the input fields the learnings will be displayed on a table. On one part of the table will be the learning text or the learning itself “wake up earlier”, “watch less tv”, “go more for walks to clear your head”, etc. On the other part of the table will be a number that will represent how many times the learning has occurred to the user.
Let’s say a user finds out one week he can be more productive if he wakes up earlier so he adds a “wake up earlier” learning. The learning would be added as:
- Wake up earlier: 1
If for whatever reason in the coming week or a week after that the user again has a week where he considers he would’ve been more productive if he had woken up earlier then he can add the learning again. This time the learning will increase 1 point and be displayed as:
- Wake up earlier: 2
The idea is to add repeated learnings in order to show the user habits that could improve his productivity that he hasn’t yet integrated into his routine.
The learnings will be ordered not in the order they were inputted but will be ordered with the learnings with most points first.
If for example week after week the learning “Do not go to sleep so late” or “Don’t party so much on the weekend” comes out then those learnings will increase in value and be displayed at the top of the learnings table showing the user where he should focus on.
Also besides the learning table there will be a learning chart. This will be a bar chart displayed from highest to lowest and from left to right the learnings along with their values.
This way the user will be able to quickly assess which learnings have the most values, and therefore which learnings have repeated most times and which need to be corrected or receive more attention on the part of the user.
The blog section will include periodical writings redacted and uploaded by the user on a subject about productivity and enhancing productivity. It can be a new technique the user has discovered to be more productive for longer. It can be a discussion on a youtube video on will-power. It can be a review about a book on how to work smarter, not harder. It can be anything as long as it is tied to the loose thread of productivity.