Take a look at a previous post I did about tags vs contexts here, though the post is nearly 7 years old. Tags would likely consolidate things and remove the need for sub-contexts. Meanwhile, the & Flow : – Laptop context is excellent for clearing regularly. The context is useful when I focus on a project but is not very useful as a standalone list. The latter is useful for short tasks while the former is used for larger tasks that could be done at the laptop. For example, I have a context for and another called & Flow : – Laptop. Currently, I do use certain workarounds for what are tag-like features. In fact, using tags could be quite excellent. I worry it might be too easy to create tags and not follow up on them. There is a benefit to contexts in that one needs to be very streamlined in thinking through where a task best resides and how and where you’ll access it. Contrast that to tags in which multiple can be assigned to any task. There can only be one context assigned to a task. It’s also the feature I’m most nervous about. Tags are likely what’s most tantalizing for most users. According to Ken, they are aiming for a Testflight in Quarter 1 of this year! Tags
#Omnifocus 3 reminders manual#
OmniFocus 3 looks like its getting tags, manual sorting, flexible scheduling, flexible notifications, a collaboration option, and more. The latest one has Omni’s CEO, Ken Case, discussing his thoughts on the Omni Group 2018 Road Map. They include visions for OmniOutliner, OmniGraffle, OmniPlan, and of course, OmniFocus.Īlso, I just discovered that the Omni Group has a podcast. The Omni Group has put together a their plan for the next year.
0 kommentar(er)
