Before getting into the question, I wanted to give you a small prologue. As designers we should understand the users; for whom we are designing the product. I this case, the target audience of the visualizations. For me there are three kinds of people:

1. The Citizens Living in Japan - These people live in Japan. They have their families, land, apartments… there. For them it is almost impossible to think about ‘leaving Japan’. The Japanese goverment has to support them in case of any emergencies. In simple word they are under sole protection of the Japanese Government. They can’t much on their own. Any alarm, real or false creates panic. Which can lead to another disaster of its own on.
2. The Expats – These are the people I say if any signs of danger, can get out of the country. The major thing they need to sacrifice for their safety is their ‘tie’, can be emotional, monetory, any other ties with Japan. In short they are the people that can afford to leave the country.
3. The Outside World – The rest of the world (like me and most you), who need these visualizations or facts just to be in a state ‘being informed’. For them, not much decision or actions should be taken after knowing Fukushima’s state.

So the question I want to ask to the designers, when they say they are going to make a better visualization — for which of the above users are you going to design?

In the platform the users have to rate recipes others have posted. Why do we need a rating system? When you are given with 100s of books, movies, products‚…, you need some measure to select one or more from the pile. People uses rating as a common tool for this. On websites it has become a democratical way to decide what content or product is of higher quality.

Popular Rating Mechanisms

Voting: In the web sites like digg, stackoverflow, quora etc. one can give thumbs up or thumbs down for a piece of article. If we look at the type of content these sites are handling are news articles, opinion (question & answers) etc. The votes are like ‘I agree to the article or I don’t agree’, ‘I like or I don’t like’, ‘I recommend this or I don’t recommend this’, so on. Its a binary opinion, discarding the ‘I don’t care’ state of being not voting.

Stars: It has it roots for the printed reviews like Michellin Guide. Commonly 3 stars or 5 stars. When it comes to websites 5 stars is more common. Since this techniques is prevailing since many years the people understands right away. It somehow gained an affordance of grading over the course of time with users.

Score Based: Similar to starts but here the range of rating go beyond 5. Usually on a scale of 1 to 10, 1 to 100 etc. In the website this done either by a scroll range bar or type in.

I Like Button: The Facebook introduced a new and simple grading mechanism, which you either like or not.

Coming to Recipes

My friend @cherianthomas told me chefs are artists and each of their recipes are their art pieces. I agree with him. So how do people rate art pieces? Coming to paintings you may say I like the stars shining giving the light to the town…, blah blah. You will just bring out you emotion. Coming to food you will also have similar kind of emotions. The food and the recipe from which it is made are two seperate entities. The recipe is like a tool which one used to prepare a dish. All the emotions when you eat a dish will just for the dish you ate. So here we just need to rate the tool, that is the ‘recipe’.

If I give you three hammers and ten nails to fix. Say a claw hammer, a sledge hammer and mallet. Which one do you use for nailing? I would pick claw hammer for that purpose, because it just works on nail. See here a utilitarian object of the hammer comes into play. Similarly when you speak about recipes, it should be doable for me, the context, re-usable,… these kind of parameters churned in your brain simply makes you say things like: “I’ve tried this recipe, didn’t work because of so and so… I won’t cook this again”, “It was easy, sure I can use this recipe for breakfast”,…

These are the kind of opinions I need to collect. Then their summaries I have to represent effectively. Which is actually can be done in many ways. Can be with heat bar, stars, textual,… From these I chose stars rating control. If implemented well you just need to see & one click. No dragging, thinking which number to give, multiple. I would call this simple. Other simple ones are voting up/down & ‘I like’ which I rejected because of the bandwidth of opinions possible are not enough.

Say I have five kind of opinions for example:

• I won’t cook again
• May be, may be not
• I may cook again
• I will cook again
• Its become one of my favorite

These can be easily mapped to the 5 stars rating. So the two sides of a rating mechanism: collection & representation is handled.

Interaction with control is simple. Almost simple enough to say just Read & Click

Also the stars rating snippet can be used in different sizes and colors depending on the context without losing the meaning

This is a part of the thought process which I had while I’m working on the rating and resulted in finalizing on stars rating for recipes. Do share your views on this.

After long time got a chance to see a good rain

Canon EOS Kiss Digital X | Canon EF 50mm f/1.8 II | 1/160 s | f10 | ISO100

Tables at Uto Kulm Restaurant, Üetliberg, Switzerland

Canon EOS Kiss Digital X | Canon EF-S18-55mm F3.5-5.6 USM | 1/60 s | f13 | ISO400

I liked the texture of the pavement, which is very common in Zürich.