Outliner Software Forum RSS Feed Forum Posts Feed

Subscribe by Email

CRIMP Defined

 

Tip Jar

OmniFocus

View this topic | Back to topic list

Posted by Chris Thompson
Jan 11, 2008 at 07:02 PM

 

What you’re describing is actually the original UNIX philosophy… many small programs which interact with your data in various ways using a variety of common facilities provided by the OS.  One of the nice things about OS X is that it does tend to draw on this philosophy.  For example, should it matter whether you’re viewing your list of todos in Mail, or in iCal, or in TimeLog, or Bento, or OmniFocus?  Each presents a different view, but the underlying data is the same (well, OmniFocus has to sync, but the next (Leopard only) version may not have to).  Let programs slice and dice data in ways they’re good at, then share it, rather than being monolithic cathedrals.

Regarding OmniFocus, I’m somewhat split.  I think the user interface is a little heavy right now.  It’s a version 1.0 product of course, so it will be improved.  It will definitely appeal to the class of people who used Ecco as a project management or GTD tool.  It’s more structured than Ecco, which is a bit of a tradeoff, but I think the idea is to use OmniOutliner for unstructured data with columns and OmniFocus for lightweight project/task management.

Though OmniFocus has its pros, I personally prefer Things:
http://culturedcode.com/things/
It’s much more unstructured than OmniFocus, and still lacks some important features (it’s in beta), but the user interface is extraordinarily well thought out, and its support for arbitrary, hierarchical tagging allows you to develop your own workflows.  I’m a sucker for these kinds of unstructured apps (which is probably why I always loved Ecco).

—Chris


Randall Shinn wrote:
>I sometimes think of software programs as
>personal assistants. OS X’s model seems to treat software applications as team
>members who are allowed to communicate directly with each other. Windows’s model
>seems to treat software applications as individual workers who can only communicate
>through a middle manager (the registry) who thrives on creating barriers between
>individuals via arcane permissions and rules.
> >The OS X approach ultimately seems
>far more productive because it allows for easier development of specialized
>programs like OmniFocus that interact effortlessly with your other personal
>assistants.