#OMNIFOCUS CONTEXT VS PROJECT HOW TO#
#OMNIFOCUS CONTEXT VS PROJECT FULL#
#OMNIFOCUS CONTEXT VS PROJECT ANDROID#
#OMNIFOCUS CONTEXT VS PROJECT FREE#

If there are more than two devices (eg a desktop, phone and tablet) you have to set up sync between two of them (say, the desktop and phone) and then exclude the phone and reconfigure the desktop to sync with the tablet. If your mobile device is out of range of the wifi then sync will have to wait till it's back in range. Wifi syncs between two devices on the same IP subnet. mobile and desktop apps can sync by either wifi or cloud sync facilities. When the task has landed where I want it, I let go of the arrow.ДЎ0. At the same time, the task jumps up or down the listing as its position in the sort order changes. The slider starts to move and the importance numbers start to climb or dive. Again, there are a lot of methods - my favorite is to sort the list by importance then, click on the importance slider and hold down the left arrow or the right arrow on the keyboard. Sometimes there is a legitimate need to move a task around in the outline, but usually when people ask about this, they are wanting to move a task up or down in a sorted list. 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.

#OMNIFOCUS CONTEXT VS PROJECT 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.

#OMNIFOCUS CONTEXT VS PROJECT 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.

#OMNIFOCUS CONTEXT VS PROJECT 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.

#OMNIFOCUS CONTEXT VS PROJECT 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. #12 Spend an hour or too reading through this forum/board and see how many requests are open, long standing, repeats etc.

Omnifocus context vs project