This is the top-level dashboard screen for the Motorola Tasks app. When there are 0 tasks in the system, the screen shows this message explaining the app's general purpose. (Motorola Atrix 2, Summer 2012)
This is the top-level dashboard screen for the Motorola Tasks app. We wanted to bubble up tasks to this screen so that the user could immediately see actionable items without having to dive into a specific section. (Motorola Atrix 2, Summer 2012)
This is the Task List Screen following a common template design regardless of category. At this level, we tried to highlight the most important data for each task item, including whether it was starred, whether there was an alarm on the due date, whether it had any tags, etc. (Motorola Atrix 2, Summer 2012)
The user triggers this popup window by touching the title area at the top of the screen. The popup allows the user to easily pivot to one of the other top level categories, such as Overdue, Due Today, etc. In addition, the user can show or hide completed tasks. (Motorola Atrix 2, Summer 2012)
Here is an example of a Task List template screen showing tasks grouped by priority (High, Normal, Low). (Motorola Atrix 2, Summer 2012)
The user can assign one or more "tags" to each task item. Tags allow the user to more easily organize tasks into logical groups and are fully user editable. (Motorola Atrix 2, Summer 2012)
This is an example of a single task item in view mode. We exposed the three most commonly used actions in the top toolbar, with other actions available in the Menu. Even in view mode, though, the user can touch the checkbox to mark the item as done. (Motorola Atrix 2, Summer 2012)
This is the default view for a new task item. We tried to minimize the number of fields shown so that a user entering a quick reminder wouldn't be overwhelmed with all of the "advanced" types of fields. (Motorola Atrix 2, Summer 2012)
This is the Task Edit Form with the panel displaying the advanced fields under the "More" button expanded. (Motorola Atrix 2, Summer 2012)
This is the general tag management screen where the user sees all tags she uses on any task. She can create new ones or delete unused ones. (Motorola Atrix 2, Summer 2012)
We build the Tasks app to support outbound task sharing in the first version. Any task could be exported to an .ICS file and shared by email or SMS. (Motorola Atrix 2, Summer 2012)
The Tasks app came with a Home Screen widget fully supporting Motorola's innovative widget resizing features (two years before native Android). (Motorola Atrix 2, Summer 2012)
gLike
Motorola Tasks App (2010)

I was the lead UI designer for the MOTOBLUR Tasks app in late 2010. I conceived of the UI design, including IA, and worked closely with a graphic designer on the visual aspects. The original goal of the Tasks app was to provide a modest but very functional To Do app which would be appealing to a wide range of users from casual to people who follow one of the big task management methodologies. The first version of the app did not support third party app sources, but the goal was to eventually fold in support for such cloud/remote services as Outlook Tasks and Remember the Milk. Note how the Tasks app UI shares many common UI patterns with the Calendar and Apps Launcher with the Groups feature, which was definitely intentional. These pictures were taken on a Motorola Atrix 2 in Summer 2012 and the design has remained largely unchanged. (Android)

A more complete professional portfolio is on my personal web site:
www.AnthonyDHand.com

View Website
Anthony Hand
Sr. User Experience Designer at DTS, Inc. San Jose, CA