My last attempt was 2Do on Android, which is a very nice and usable app on Android. So basically I don't have a trusted system and things slip through the cracks. I try something new for a while and then eventually run into frustration and give up on that. I've gone back and forth and it seems every week or two I give up on the current system and look for something new. Still waiting for it and someday may write it myself. I still think someday we will have the 'one' GTD app. Some examples are Smthngs and MLO where projects are easier. There is much less mental resistance to creating projects here.

There are other systems where a project is no big deal. Just making projects hierarchical would at least let you bury those smaller tasks instead of having all equally visible. You ask yourself, 'Do I really want to make a project for this thing that requires 2 steps?' Unless a project feels big enough you find yourself resisting making projects. The action of making a project here provides some mental resistance. I call this idea of a single list of projects 'heavyweight'. It is certainly right that it is very important to distinguish things that can be done in one action from those that require multiple steps.Д«ut here many apps follow this exact model of a list of projects which I think is an implementation rooted in paper based system. The GTD book makes a heavy emphasis on projects and having a project list. I think this is one area where the GTD book influences app makers the wrong way.

Producteev vs toodledo