[smeej]

I'm a huge fan of https://momentum.earth.

It's the best GTD system I've seen online, and the infinite sub-tasking/grouping, where each grouping can be set to be done either sequentially or in parallel, either surfacing the next task or all the tasks in the "Next" list automatically is amazing.

Throw in the review settings, and the big picture areas of responsibility? And end-to-end encryption?

It's amazing.

[hammyhavoc]

Can you do 'blocking' tasks? E.g. Can't paint a wall until the task to move a container is done, but can't do that until the container is empty, so the sequence is derived from blocking tasks.

Is it collaborative?

[smeej]

Tasks are all handled as the same kind of object, but I'm going to call any task with a subtask a "project," and any task without any subtasks just a "task."

The way I would do this would be to basically treat "move the container" as a project and "empty container" as the first sequential subtask.

If you have: - Move container (sequential) | --Empty container

empty container will show up in the "Next" list because it's the "first" (only) subtask in the project. As soon as it's completed, the parent task, "Move container" will automatically show up on "Next" because it's now a task in its own right, not a project with subtasks.

This matches my intuitive way of thinking about how tasks relate to each other (do the parts, and when the last part is done, complete the project), but it's not done by naming something a "blocking" task.

Edited to add: I've not tried using it collaboratively, but I don't think that functionality exists. GQueues might be a better fit for that.

[pirate787]

I'm looking at it, there's an "away" status for tasks waiting on someone else. Also tasks can be sequential so that's naturally blocking. Doesn't appear to be collaborative. It's a very nice interface and I'm seriously considering it. My friction is that I have a bunch of work projects that I'm not sure if I should dump them into momentum, which seems more personally aimed.