lvrefa.blogg.se - Ticktick vs todoist reddit

#TICKTICK VS TODOIST REDDIT ARCHIVE#
#TICKTICK VS TODOIST REDDIT TV#

To support my generalization, I invent three new concepts (and their functions): GeneralizingĪfter lots of interaction with all the concepts, I can confidently draw out the system design of Todoist. If I don’t let you access the bedroom, you cannot use that TV, but you can still use other things to entertain or study.

#TICKTICK VS TODOIST REDDIT TV#

A TV (a task) can only exist in the bedroom (a project), but it can be used for many use-cases like entertainment or study (label). So if we compare Todoist to a house, then each Project is a room, each task is an appliance and each Label is its use-cases. Also, when I delete a project, all of the tasks inside it ARE DELETED. To my great surprise, I can only assign 1 Project per task, but I can assign many Labels for it. I accidentally figured it out when I tried to assign Projects to tasks. What’s the difference between Projects and Labels + Filters that make it non-archive-able? On the surface, it looks completely similar. Meanwhile, we can create and delete Projects, Filters, and Labels.

#TICKTICK VS TODOIST REDDIT ARCHIVE#

We cannot delete, create or archive them. In the meantime, with Filters, I can group tasks that belong to the project “Personal” and have a due date of “Today” and are labeled “Urgent”.įrom this table, I can immediately see that Today and Inbox are two unchanged components in Todoist. While Projects, Labels, Today, Inbox let me view the tasks that have ONE SAME ATTRIBUTE, Filters let me view by MANY.įor example, when I click on project “Personal”, I can see all tasks that are assigned to that project. Filters are a little bit more powerful than the restĪnother thing that catches my attention: Filters. In SQL terms, it’s like having a where query: Select tasksĢ. In other words, Todoist is a giant task list, and each of them is a different way to view my tasks. There’s a repeated pattern in the functionĪll of these concepts are used to group tasks that have the same contextual meaning.

Inbox: Group tasks that are not assigned any Projectsġ.

Today: Group tasks that have due date = today.

tasks with label = Urgent, and due date = today).

Filters: Group tasks by many conditions (i.e.

Labels: Group tasks by similar Labels that I have assigned to them.

Projects: Group tasks by similar Project that I have assigned to them.

To understand the functions of each concept, let’s see what happens when I click on each of them: For example with “kettle”, we can carry, throw, smash, heat up…(actions) The action is what we can do with the concept. For example, if we want to contain water (function), we invent “kettle”, “cup”, “bowl” (concepts). The function is the mission that this concept is “born” to solve. Let’s go through the troublesome concepts that jump-scared me since my first day:Įach object in conceptual design is defined by 2 things: function and action. The ones I intentionally exclude are either self-explanatory or too minor to mention. I will only list out the terms that confuse me.

Describe the action we can take with each concept.

List all the terms that confuse me (hereby called concept) in Todoist.

I love the idea behind Conceptual Design because it breaks complicated matters into the most atomic level. Therefore I decided to apply Conceptual Design to break down Todoist’s system to truly understand the product. For example, can I use Labels for the purpose of Projects, instead?Īnd the answer to that question is nowhere to be found. Since I’m not in their shoes (and will never be), my natural reaction to such an explanation would be: “can you switch the concept for one another?”. People explained the difference between, say, Project and Label using their own examples.

Ironically, what I found was exactly what Todoist provided. So I turned to Reddit, where all the smart minds of the Internet gathers, looking for the answer. This method doesn’t give me a high-level, abstractive understanding of each feature, and of the product as a whole.

However, the examples are just some use-cases, not all, that a feature can be used to solve. I understand that Todoist writers want to keep it simple and down-to-earth for the mass audience, hence their use of mere examples to describe a feature.