As computing becomes more ubiquitous in our objects, designers need to be more aware of how to design meaningful interactions into electronically enhanced objects. At the University of Washington, a class of junior Interaction Design majors is exploring this question. These pages chronicle their efforts.

Thursday, April 14, 2011

Week 3: Sensors + I/O diagram

Emily + Mitch


Situation

When refrigerators get full, items get lost and spoil while their owner is unaware. We wanted to create an object that would display cues when an item goes out of date or is past its prime consumption time. With Ardunio, tupperware, bottles, and lids have the capability to host these cues.

We are still indecision about what this output should be but brainstorms we've had are listed below.


I/O Diagram

INPUT DECISIONS OUTPUT
time how much time has elapsed? increase affordance (*output cues) as more time passes

temperature is the temp. over 40 degrees? if yes: decrease acceptable save time; if no: remain dormant

light is the food sitting out/in light? if yes: decrease acceptable save time; if no: remain dormant

light is the fridge dark? if yes: stay in off state; if no: turn on affordance


food type is the [food category] out of date? if yes: turn on affordance (highest state); if no: stay dormant


Output Cues

+ rotting food-rotting container: To communicate that food has been spoiled the container looses strength and rigidity similar to rotting food or becomes squishy because a balloon fills with air.

+ signal light: Once the fridge has been open a light is shined from the top of the container onto the food. Green being safe to red being spoiled.

+ chroma change: If the food is unsafe the plastic of the container has changed color; from clear, safe to eat to dark unsafe to eat. The color change would spread like mold over a surface.





No comments:

Post a Comment