What Did I Do?
After being exposed with LittleBits for the first time, I was given the task to build a test prototype to figure out how the kit works. Then, my partner and I decided on a problem to solve — feline obesity — and came up with three solutions. We used LittleBits to attempt to prototype our solutions, and the process consisted of endless trial-and-error, for neither my partner nor I was familiar with the prototyping kit. I believe it could have gone better if we took more time to learn about the major functions and limitations of the kit before being given a short amount of time to build and test three different prototypes. With each functional prototype we built, we recorded the prototype at work along with the solution it was intended to solve.
Here is the link to my work.
Since my partner and I couldn’t decide on our problem and three solutions prior to the prototyping session, we spent the greater amount of time deciding on and adjusting our solutions based on our experiences with LittleBits as we went along. We were not thoroughly aware of LittleBits’ limitations, which made it harder for us to understand which solutions would be possible to solve through something we could physically prototype only using the kit. It wasn’t until the end of the session that we realized we could have certain parts of the prototype “represent” an intended function.
How Did My Prototype Compare to My Original Concept?
My original concept to solve the problem of feline obesity was a step counter for a pet cat that only dispenses food when the cat has walked a certain number of steps. While I could build the prototype well enough to explain the basic intended concepts, it wasn’t detailed enough to show certain limitations. For example, one limitation of my cat step counter is the feasibility — how can the device design be comfortable for the cat? Since my prototype didn’t show the actual design of the counter, it failed to present a very important factor.