When actually getting things done, many people prefer to work in a to-do list, which is a flat (no hierarchy) filtered and sorted view of things to be done. People often find it helpful to work in the outline when analysing and designing their projects. A view showing all tasks in their hierarchical structure is an outline view, a view showing a selected subset (eg tasks in a certain context) in their hierarchical structure is a filtered outline. But position in the outline is not necessarily related at all to what tasks to do next. Position in the outline is helpful for finding a task and it matters for "complete tasks in order" and has a big effect on the calculation of computer-score. Every task has a position somewhere in the outline, alongside of its siblings, above any subtasks, subfolders or sub-folders (collectively "children") and (unless it's at the root) its parent and grandparent etc items (each of which can be a task, folder or project). Personally I don't mind this hugely, but only because having now tried about 10 GTD tools and pretty much hated them all I am *desperate* to find something I can use.Ĩ.OK, it's time to talk about position-in-outline versus position-in-report. Instead the user is required to remember to hit something I have never seen in any other system "Shift/Alt/Right". I can't!Īnother example is that if I want to indent I can't just hit the Tab key to intent the current line. So if I want to break the text of an Action a link into two lines (2 tasks) then. in other systems hitting enter creates a carriage return - i.e. One trivial example is that the use of the Enter key in MLO is odd and is something that new users actually have to learn.
Doit.im vs nozbe how to#
Mainstream users simply will not tolerate things being pretty obvious as to how to use them. And they could do this without ruining the interface for advanced users. And then, over time one could experiment to see how many additional features one could incorporate before the system become too confusing for newbies to use.
Doit.im vs nozbe full#
One answer would be to have a 'Novice mode', with a greatly simplified interface, but also to keep the full existing what you might call 'Expert mode'. The reason for this is that although early adopters are happy to tolerate lots of complexity and difficulties of use, mainstream users absolutely are NOT.īut I was thinking about this problem. Then again I'm no longer holding my breath. With any luck this dev team will get with the 21st century at some point. It should've been to me but I rushed into my purchase and now I'll just live with it. If responsive dev is important to you this might be a deal breaker. It looks just like the iOS 2.0 app and it took much much much too long to get that little bit out.
Doit.im vs nozbe android#
Recently, in the face of MANY MANY requests they caved and produced a few screenshots of the coming 2.0 Android app. The devs do NOT share timelines, dev milestones, roadmaps/future plans nor anything else till it's released. The rest of get to wait with baited breath. You'll have to get selected to be a member of the beta team (which apparently requires quite a bit of involvement - 4+ hrs a week at last check) to have access. There is a Jira bug tracker but that is not for the unwashed masses.
Doit.im vs nozbe free#
There is no one curating the User Voice so it's just a free for all and useless imho. There is a User Voice community but that too is disheveled and an apparent waste of time as decent feature requests get lost in a barrage of ME TOO's to overarching requests like "iPad app!". So much so I've pretty much given up on reporting or asking for anything. Then note which items the devs DO feel compelled to respond to. Then note how often the devs feel compelled to respond. It is similar to the method described in my previous post Getting Organized with Evernote – GTD Task Management.#12 Spend an hour or too reading through this forum/board and see how many requests are open, long standing, repeats etc. This feature makes the whole GTD process extremely productive by reducing the time needed to Process and Organize the tasks. In Android there is a button on the notification area, where by clicking on it you can Smart-Add tasks without opening the application.
This feature exists on the mobile apps as well. As soon as you type these special characters (see table below), a drop down appears with the available values you can enter. It is basically a text box where you would normally type in your task, and by entering some special characters, you can set the task’s Start Date, Context, Project, Priority, and Tags. It allows users to add Collect, Process and Organize tasks within seconds. Smart-Add is a feature that provides additional value to this service.
0 kommentar(er)
