HCDE Prototyping Sprint

Testing Process
The first experience of using littleBits is quite pleasing. We first distinguish all the inputs, which are battery and power outlet, the connectors which are wires, switches and output, including alarm, music player, lightbulb and more. The concept of connecting parts together to make a working system is pretty easy because the colors distinguish of each part is really helpful while building and revising the steps. We considered the process as a linear system, which starts with a power input, triggered by a condition then give a feedback. For example, we connected a USB power input, a button switch, and a light together, whenever we push the button, the light is going to light up, once we release the bottom, the light went off. We could make even more difficult interaction system by connecting multiple conditioning switches and outputs.

video of the prototyping:

Checking every part from the kit.
Trying to trigger all the outputs.
Test out the switches.

Reflect a bit on your experience.
Although we tried all the switches, but still not completely understand their functions. For instance, I’m not clear about how to use the switch that can change different channels. I would love to try all the combinations of possible switches and outputs because I feel like in real life situation, simple trigger and output may not be enough to fulfill feasibility, desirability and usability all in once. Because feasible, desirable, usable are the characteristics essential, embed those concepts while we brainstorming the idea would be much more efficient.

After came up the prototype, what should we do to modify our idea?
 — — — We need to apply the usability test and run user research. Based on the testing results, we proposed and apply some changes. The whole user testing and modifying process should follow ethics: respect, beneficent, justice.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.