CS 247B: Task Flows and Sketchy Screens

Dhruvik Parikh
2 min readMar 2, 2021

--

After sketching up a variety of prototype ideas for our sleep aid application, including a phone application, reminder system, calendar integration, and smartwatch application, we decided to move forward with Wynd, an Apple Watch application that syncs with your Apple Health and tracks your activity to send you helpful wind-down reminders during the evening. It also lets you track your activity completion and sleep quality, and checks in with you on a monthly basis so you can update your goals and view your progress.

In planning the application design, we split the user flows into 5 main sections:

  • Setup and goal setting
  • Stats tracking and recalibration
  • Overactivity notifications
  • Evening reminders
  • Winding down and waking up

The latter three are meant to be daily flows, whereas the first two occur only occasionally (when we send a recalibration notification or they manually recalibrate). In this article, I’ll focus on stats tracking and recalibration.

Stats tracking and recalibration: task flow

Task flow for stats tracking and recalibration

The user can enter this flow through two separate actions. One is the automated notification that we send on a monthly notification, to remind them to view their progress and update their goals. The other is by pressing the “view stats” button on the app homepage, which lets them enter the flow at will. From the stats tracking page, they can swipe through the various activities and goals that they have inputted, and press the “recalibrate” button to transport back to the initial settings page for that goal. From that setup page, they can also add new goals.

Sketchy screens

Sketchy screens for stats tracking and recalibration

We also started sketching out the wireframes for what this flow would look like in the watch app. The main design consideration here was to optimize for limited action in each screen, to a maximum of two buttons and a single swipe action, to accommodate the small screen size. We also wanted to visualize the stats in a simple and intuitive way, so we avoided complex graphs and opted for a minimalistic calendar view.

--

--

No responses yet