search

proming / android-shuffle

Automatically exported from code.google.com/p/android-shuffle
0 stars 0 forks source link

Swap position of Project and Action #35

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I propose swapping the position of Project and Action on the "Add Action"
screen and on the display of actions, or at least providing an option in
settings to allow users to swap them.  For GTD purists, project is usually
the thing you think of first (e.g., "Get blender"), while next action
requires some additional thought: (e.g., "Read reviews on Amazon").  Thus,
when adding an item to the inbox, it is more natural to put the project
"get blender" in the first field, and then when you have some time later
you can fill in the next action.  Similarly, when reviewing your list of
actions, it is more natural to see "Get Blender" as the big label, and
"Read reviews on Amazon" as a smaller entry below it.  I find it strange to
see "Read reviews on Amazon" first, because I then have to figure out what
that is in reference to.  You can also reverse the logic of the inbox:
clean up inbox will leave projects that do not yet have next actions.

Original issue reported on code.google.com by tkryn...@gmail.com on 31 May 2009 at 7:34

GoogleCodeExporter commented 8 years ago 
I agree with the point about creating projects before actions, but I like the
"actions lists" as it is today.

Original comment by saravkr...@gmail.com on 7 Feb 2010 at 2:42

GoogleCodeExporter commented 8 years ago 
I'd like to have levels of actions, for this reason. Some tasks end up being 
more than one action. It would be nice to have a way to convert a current 
action to a "subproject", on a phone four levels should be enough.

Original comment by davidfsn...@gmail.com on 16 Aug 2010 at 12:34

GoogleCodeExporter commented 8 years ago 
I second the first comment. The "project first" logic in creating tasks is much 
more sensible.

Original comment by wkrakow...@gmail.com on 26 Nov 2010 at 11:26

GoogleCodeExporter commented 8 years ago 
I don't agree with this - the need is there, but a better solution would be 
converting tasks into projects (Issue 78 
http://code.google.com/p/android-shuffle/issues/detail?id=78 ) and/or having 
multiple levels of projects/tasks.

I believe there should be no effort required in first capturing a task idea - 
having to stop and think "is this a project or a task?" inhibits capture. You 
do that later when cleaning out your inbox. And possibly multiple times as you 
work on an action and find it requires something else first.

Original comment by SecretCo...@gmail.com on 14 Apr 2011 at 9:18