Thought about this as well.
What’s stopping me is that it would help with / encourage note taking, while not helping or event distracting from “getting things done”. And note taking is not the focus of Everdo.
Descriptions on tasks and projects were intended to capture some quick relevant information, but they are not going to be comprehensive enough to replace more specialized tools. Or be used for content creation purposes (which is why markdown was created in the first place)
In other words, you will almost always want to use a different medium for reference materials anyway. I personally use either plain markdown files in a git folder or a google doc of some sort if collaboration is necessary. Then I just create a link to it from Everdo, so that it’s easily accessible. I could explain this setup in more detail if you’d like.
Hope this provides some justification for why it was decided to keep task descriptions simple.
A couple of questions for you:
- what particular features of markdown would you find most useful in the context of task descriptions?
- can you make a case demonstrating how markdown syntax would benefit your productivity (vs not having it)