For the course "User Interface Design", I was tasked with creating a smartphone application that extended some of its functionality to a smartwatch (like an Apple Watch or LG C).
1. People will likely use the smartphone or the smartwatch to complete a task (not used together)
2. The smartwatch has a crown that can be pressed or rotated forwards or backwards (and no other buttons)
Create a mobile & watch application that allows people to search and follow recipes at home. The application must have the following functions:
I first crafted a simple persona of an ideal user for this application, who I named Asha. Following this, I used the Jobs to Be Done framework to flesh out they key task she wanted to accomplish. You can see the specifics below:
With this framework, I determined the three core needs for Asha:
1. Asha needs step-by-step visual guidance that she can control (such as a video she can play or pause).
2. Asha needs to quickly assess the level of difficulty and the amount of time it will take to cook a recipe.
3. She needs clearly worded instructions that she can quickly see and understand while performing other cooking tasks.
In researching similar applications, some common interaction patterns became discernible. This lead to the creation of this initial diagram of a user flow.
Determining an initial user flow helped inspire some low-fidelity prototyping. In particular, I drew some sketches of the first few mobile and smart watch screens:
Following some sketches, I created a medium-fidelity version of the prototype.
Utilizing this prototype, I then did guerilla testing with university students to gather some feedback.
Some key concerns they noted were:
Incorporating the feedback from my testing, I created a high-fidelity version of the prototype.
Here are two user flows of the high-fidelity prototype of the mobile and watch applications.
With the Apple Watch in particular, it became clear that copy had to be both clear and minimal in order to communicate the recipe steps effectively. As the interface is quite a bit smaller on the watch, I had to rely on less text and use more expressive icons. This differed from the smartphone, where I was able to incorporate more detailed graphics and text.
The jobs to be done framework changed my thinking and approach to design. Prior to it, I always used personas to inform what was being designed. However, with the Jobs-To-Be-Done analysis, I was able to go beyond a general persona and be more intentional in terms of what sort of tasks the user wanted to get done.
Using the persona approach in conjunction with the job stories framework allowed me to focus what people do when faced with certain situations and challenges. As a result, I learned to approach my design work differently, by being able to specifically hone in on how people react and shape the environment that they live in.