Good app with one VERY BIG misassumption

In general, the application is great. But - I have some routines that require from me to use cyclic dates, anchored at the completion date. And here the madness begins - I don’t know why the authors think that it is natural to make users learn.

The rules are logical, but they make users:
- learn them, as there is no other way to perform the task,
- remember them, because otherwise users always need to go to the tutorial, usually while ON THE GO,
- enter enormously long schemes (again, on the go!), instead of just letting them simply choose the dates.

An example from your tutorial:
- every 3 months starting 10 April - seems legit, but instead, I would just prefer to choose due date and then: "repeat every: 3 months”
- every! 3 months starting 10 April - this one is MUCH harder to recall - because it is NOT natural to consider this ! as completion date indicator at all!

And in Polish, this sheme lacks logic even more.

Authors should read Krug’s „Don’t make me think” and NNG usability heuristics. For misunderstood "Match between system and the real world” you abuse the following ones:
- User control and freedom (I simply cannot achieve what I want to without diving deep into the manual)
- Consistency and standards (does this one need any explanation?)
- Error prevention (this scheme causes a lot of errors)
- Recognition rather than recall (you make users recall the commands or see the manual every time they want to add a recurring task)
- Flexibility and efficiency of use (does it need any explanation?)
- Help users recognize, diagnose, and recover from errors (the app makes users the weak part of the system, and they need to go through the manual over and over again to recover from errors).

FlashGPL about Todoist: To-Do List & Tasks, v6.2.2