Final Prototype
January 28, 2009, 12:42 am
Filed under: Uncategorized

Start Flash Prototype


User test videos
January 19, 2009, 1:05 pm
Filed under: Uncategorized

First Test

Second Test

We made 5 user tests, but we only recorded 2 with our video camera. As you can see, the users were able to deal very good with the tasks. But both are confused, because we didn’t implement an interactive list for recipes.

User test with prototype
January 19, 2009, 10:55 am
Filed under: Uncategorized

Three new Heuristics:

  • Try to keep the design on the mobile and on the fixed device, as equal as possible

  • Give the user the possibility for choosing meal/recipe fast and spontaneous

  • Give the user suggestions for good / healthy meal without thinking a lot about it

Task for the user test on the fixed device

  • Look what’s on this weeks meal plan

  • Go back to the home screen

  • Now you want to search a recipe, which is good before you go swimming. But because you are on diet, you want some low fat meal also

Task for user test on the mobile device

  • Look on your shopping list
  • Look if “Two cups fresh shelled peas” are already in your fridge

Problems during the Test:

One of the main problems just affects the prototype itself. The users criticized that the recipes arent’ updated interactive, when you add a new filter/criterium. This was a bit confusing

Software Prototype
January 12, 2009, 11:29 am
Filed under: Uncategorized

Start Flash Prototype

Paper Prototype
January 5, 2009, 9:17 am
Filed under: Uncategorized

The paper prototype consists of five different screens:

  1. “Main Screen” always visible in the kitchen.
  2. “Week Plan” displays the planed meals.
  3. “Recipes” database with straightforward ways to display some special recipes.
  4. “Shopping List” shows what’s still missing and when it is needed.
  5. “Recipe Details” includes all steps to actually cook the meal.

The same screens should also be available on the mobile device. We decided to use the iPhone for our first (non paper) prototype. The user interface elements of the iPhone are most adapted to small screen size. After the reading through the “iPhone Human Interface Guidelines” (iPhone Dev Center – the decision to keep the interface between the fixed device and the the mobile device consistent was made. We tried to take typical iPhone elements to the large scale touch screen, resulting in the following images:

1.The “Main Screen” including root level menu structure and the next recipe to be cooked.

2. “Week Plan” includes drag and drop support to rearrange the meals and possibilities to add and remove recipies. The recipes also get a special label if all necessary ingredients are available.


3. “Recipes” includes a typical iPhone like Tab Bar at the bottom to select different views of the same data model. The user should be able to rate recipes, check the cooking counter and find out about new and healthy meals.


4. The “Shopping List”, shows which ingredients are still needed. This list will of course be synced with the mobile device.


5. “Recipe Details”


The same screens and additionally the possibility to display two images to the fridges content are also available on the mobile device (PostIt(tm) Notes should match the iPhone screen size):


User testing using the paper prototype was quite fun. We started with the fixed device and our users became excited when they later realized that everything they did in the kitchen can also be done on the go. “Its all on your iPhone”. During the tests we came across two improvements.
The first problem is that there should be a way to cook an “unplanned meal”, which is not listed in the week plan. We first thought about a new button labeled “I’m hungry”, but the realized that parts of what we need are already included in the recipes database. It just has to be extended in a way to search for recipes which only need the available ingredients.
The second problem concerns the images of the fridge on the mobile device. It was very cumbersome to get an overview about what’s inside the fridge and remove these items from the shopping list where appropriate. Our solution to this problem is that all items of the shopping list will be displayed over the fridge images in succession. The user can now quickly decide if a certain ingredient is already at home.

Design principles
December 18, 2008, 11:35 pm
Filed under: Uncategorized
  • “Make adequate nutrition as easy as eating fast food!”
  • “Let the user combine his knowledge about good food with the knowledge of the device”
  • “Support the user, don’t boss him”

Conclusions and knowledge from the Interview and free talk about the project
December 18, 2008, 11:29 pm
Filed under: Uncategorized
  • The problem of bad nutrition is not due to stupid or uninformed people, it is because people are simply to lazy for a adequate nutrition.
  • Often people are not only to lazy to cook, they are also to lazy to only think about what they can cook.
  • Nearly everbody remembered situations where they went shopping spontaneously ( after work/university etc. ) and had no ideas about recipes or whats in their fridge
  • Some would prefer automatic object recoginition for the fridge, so recipe suggestions would be easyier to realize