When I first see LittleBits, I thought there was no way I could know how to get this to work. There are so many little parts in the set and me usually not good at building little parts together. However, the practice we did in the studio helped a lot. We first tried to find all the parts and check them on a sheet of paper, then we got to play around a little bit with LittleBits and tried building some prototypes our own. From these practices, we acknowledged with different parts' functionality and how to connect them together. Then we start to build our own prototypes, my partner helped me a lot on understanding how this works, and we finally generated the prototypes we wanted.
One problem we encountered during this prototyping process was how to make our final prototype works as close to how we want it to work in the real life as possible. For example, our scenario is somebody has a roommate that plays music really loud. We were thinking to build a device that can automatically turn the music down when its volume is getting to a certain upper limit, instead of just giving roommate a warning, we want to take the initiative to prevent the music ever gets to0 loud. But how can this actually work in the real life? People play music on different devices, it would take a lot of experiments and research or even scientific innovations to finally build a device like that. However, I think ideation and prototyping are somewhat about thinking boundlessly, even though we might not able to achieve what we want right now, but we never will if we never even thought about it.
Wildcard problem: What skills did you learn from this problem?
This is my first time building a prototype by hand with "mechanical" parts. I thought it was pretty cool that I learned so many different ways of prototyping from this class. I really value having this skill of prototyping, I think it will be very helpful for me in the future.