[TeMPOraL]

It does, because it's an outliner with a progress bar and some tagging bolted on top. It does look nice though, in a way non-Emacs users might appreciate. I can entirely imagine myself - from the alternate reality where I didn't know about Org Mode - using this for personal projects.

But enough with the criticism. I like how this looks like a nice, self-contained product. And I love that the author understands that tasks are subdivisible to more than one level. I'm really, really fed up with the usual issue trackers and project management tools we use in this industry - all of them limit your tasks to one, at best two levels.

(I wish someone one day would recognize that tasks don't form trees, but directed graphs; Org Mode, being an outliner, doesn't handle this, but I'm surprised no other tool seems to handle it either.)

[solarkraft]

> And I love that the author understands that tasks are subdivisible to more than one level.

Absolutely! This is the first thing I check for trying out a new app. It's amazing that people think one level can be enough for anyone ("oh, but you can add a level by putting these tasks into a list and another one by putting that into a project ..." dude, why?).

> I wish someone one day would recognize that tasks don't form trees, but directed graphs

It's not that nobody realized, project management is not a new field, there are already MS Project and Project Libre.

What seems to be missing is a personal version that's really easy enough to be used for personal projects.

A note about the graph representation:

You're right, it's really not always a tree, which is why I think there should be cross connections. For about 95% of cases however I'd consider a tree sufficient.

A general note about tree based thought management:

I currently use Dynalist (similar to Workflowy) to manage my ideas. I generally love it (though it could also profit from a feature to branch out into a graph).

A part of that is task management as well, with the best motivation to use it being the nesting, but it's lacking a bunch of festures on that front, so I imagine it being petty cool being able to replace it. Eventually though I'd like to be able to keep my tree of thought in a single application. Do you think your app could be extended a bit to support that (it's probably not much, since the general management is almost the same)? If I'm going to pay 5€/month (or what price are you thinking of?) I'd probably want that, as well as very easy complete export in an open format.

[solarkraft]

I made a demo account: [e-mail]:demo.

Is it possible to indent nodes on mobile?

[adriaanmulder]

Only by pinning into the parent task (tapping the bullet point). Making this easier is on my todo list

[useragent86]

> (I wish someone one day would recognize that tasks don't form trees, but directed graphs; Org Mode, being an outliner, doesn't handle this, but I'm surprised no other tool seems to handle it either.)

Does org-edna help any? Although it doesn't help with viewing them as graphs, it may help with making TODOs act like graphs.

[TeMPOraL]

Haven't used it yet, but skimming the documentation, it does seem to look like half of the picture. The other half would be a way to get a critical path analysis out of it, and somehow visualize everything together in a way that makes it easy to notice where you have slack or underutilization.

[chrisweekly]

Yes! See Roam (https://roamresearch.com)

[mbrock]

Tasks could have more logical structure than a dependency graph. You can imagine a kind of programming language for tasks with conditional logic, loops, exceptions, blocking I/O, etc. I don’t know if this has been explored?

[TeMPOraL]

I don't know. But thinking about it, writing code with complex structure usually makes sense only when it's executed more than once. Which leads me to think that the best place to look for insights on representing tasks are code isn't task management, where everything is unique and one-off, but process management, where a whole graph of tasks is executed repeatedly.

[iudqnolq]

How would a directed graph task tracker work?

[TeMPOraL]

Similarly to a regular one - except you could subdivide tasks as much as needed and specify dependency relationships between them. You wouldn't have problems representing all too common situations where one task is a subtask of two other tasks, or where one task has a hard dependency of another task's subtask. You could view tasks to be done as a network, using critical path analysis to get a better picture of how long things are going to take, and how much slack you have in the project.

[bpizzi]

I think Phabricator has implemented this behavior with parent/sub tasks. Tasks in manifest[0] are a node in a network, where a task can refer to multiple parents and sub tasks.

[0] https://secure.phabricator.com/T6526

[TeMPOraL]

I didn't know that. I've heard mixed things about Phabricator before, so I've never really bothered to play with it. I guess this is a good time to check it out. Thanks!

[bpizzi]

Frankly the core applications (code & projects) are not that bad, I've deployed it at $work. There's a too wide functionalities spread to my taste (lots of half-started applications), and no real support for managing deadlines in tasks/project (with ideally resource management).