Storyboards illustrate a usage scenario of an app, much like a comic strip. They describe when and why a user wants to do something with the app, how he would go about doing it and what he achieves by doing it. We created one for our own project to demonstrate the main usage scenario.
By watching the video presentation of Scott Klemmer on storyboards (and paper prototypes), we learned how to make good storyboards. Storyboarding is all about tasks and includes persons that are actually using the interface. It’s about communicating ideas, not about “pretty pictures”. One of the first things a storyboard should do is illustrate a goal. By the end you want to show how they accomplished what that goal was. A storyboard should convey a setting, a sequence and a situation of satisfaction. Main benefits are that it avoids commitment to a particular user interface and that you can express your ideas in concrete so that everyone in your group understands them.
With this in mind, we drew our first storyboard. It shows us how Toby would love to bake (and eat) pancakes. Unfortunately he ran out of eggs, which is quite essential in the recipe for pancakes. Our “Social Fridge” app helps him to find friends in his circle who have eggs (and possible other ingredients) and who agree to cook/bake together with him. They combine what they have in their fridge and have a great day making and eating pancakes!