OmniFocus 3
Overview
OmniFocus is a task management application for Mac, iPhone, and iPad. Version 3 focused on giving people more flexibility in how they organized and viewed their work.
We replaced contexts with tags, expanded custom perspectives, brought calendar events into the Forecast timeline, and introduced customizable inspectors on iOS. Across these changes, the goal was to preserve the depth people valued while making everyday interactions easier to manage.
My role
I led research and design for the release, managing a team of five UX designers, UI designers, and researchers.
I worked with the CEO and product manager to define the scope and priorities. Throughout development, I partnered with engineering on implementation and worked closely with QA and support to coordinate feedback from testers and customers.
My responsibilities included research planning, design strategy, design operations, and UX and UI direction.
The challenge
OmniFocus supported detailed task management, but some of its established patterns were limiting how people could work.
Each action could have only one context. Custom perspectives needed more flexible filtering. Forecast showed tasks and calendar events in separate sections, making it difficult to understand how they fit together throughout the day.
On iOS, the inspector presented 12 controls for an action. People who needed only a few of those controls still had to navigate the full set.
We needed to make these workflows more flexible while keeping outlines readable, controls accessible, and familiar concepts understandable.
Approach
Research and customer requests helped us identify four priorities: tags, custom perspectives, Forecast, and iOS inspectors.
As we explored solutions, we worked through the details in sketches, whiteboard sessions, and design iterations. Questions that initially seemed small—what to call tags, how many to display, or where calendar events belonged—had a substantial effect on the experience.
Feedback from testers, customers, QA, and support helped us refine the work. We paid particular attention to how each change fit into the existing application and what it meant for people already comfortable with OmniFocus.
The work
Replacing contexts with tags
Moving from one context to multiple tags sounded straightforward. Once we began designing it, several questions emerged: Should we retain the familiar name? How should tags appear throughout the application? How many could we show before they interfered with reading tasks?
Use the language customers already understood
Contexts had been part of OmniFocus since its inception, but the concept was often difficult to explain. Customers requesting more flexible organization usually called the feature “tags.”
We adopted that term rather than carrying the old name into the new model. After release, we received very few requests to return to contexts.
Keep the outline easy to scan
Tags appeared in navigation, the main outline, and the inspector. We initially tried carrying the tag iconography from the sidebars into the outline, but repeating those icons made task lists visually cluttered.
We moved to simple, single-color capsules in the outline and inspector. The capsules separated tags from task text without competing with it, and using the same treatment in both places connected the task’s display with its editing controls.
Give tags a limit within each row
The outline supported two layouts, and the design needed to work in both.
We experimented with showing every tag in the fluid layout, but heavily tagged actions became too tall and made the outline harder to scan. Instead, the available width determined how many tags appeared. An overflow indicator provided access to the rest.
This let people assign the tags they needed while keeping the task list manageable.
Making custom perspectives more flexible
Custom perspectives let people build focused views of their tasks. Our research showed that experienced users wanted more control over the rules behind those views.
We expanded filtering to support combinations of criteria such as availability, status, dates, estimated duration, tags, and project information.
On Mac, we used the native predicate editor framework as the foundation for configuring those rules. People could build views around specific needs—for example, available tasks that would take less than 15 minutes, or work associated with a particular set of tags.
The expanded perspectives were warmly received by advanced users and became a frequent topic of discussion in the OmniFocus community.
Bringing tasks and calendar events into one timeline
Forecast was one of the application’s most-used views. It showed upcoming tasks and could also display calendar events, but those events appeared in a separate section.
Customers described the friction this created. Their tasks and meetings happened throughout the same day, yet the interface required them to compare two lists.
We integrated calendar events into the Forecast outline alongside tasks. To keep the two distinguishable, we used a calendar icon carrying the event’s existing calendar color.
The combined timeline made the relationship between scheduled events and due tasks easier to see while preserving familiar calendar cues.
Letting people configure the iOS inspector
The iOS inspector offered 12 controls for an action. That flexibility was useful, but feedback showed that people did not want every option presented every time they edited a task.
We designed a way to reorder the controls and hide less frequently used fields. Hidden options remained accessible when needed.
This allowed people to put their most-used controls first and reduce the amount they had to scan. It preserved the application’s capabilities while giving users more control over their editing experience.
Results
OmniFocus 3 exceeded OmniFocus 2’s sales and active-user numbers.
- Daily active users increased by 12% on Mac and 17% on iOS.
- The iOS application spent six weeks as a top-25 grossing app on the App Store.
- The Mac application spent four weeks as a top-25 grossing app on the App Store.
Customer feedback was particularly positive around customizable inspectors and the expanded perspectives. The transition from contexts to tags also received few requests to restore the previous terminology.