Build a rough prototype that exercises one key aspect of what your project will do. Spend no more than three days building the prototype. Use whatever materials are fastest, easiest to use, and convey the idea well enough that another person can try it out and offer useful feedback.
Bring your prototype to class and we’ll take turns trying out one another’s prototypes and offering constructive feedback.
The idea prototyped today does not need to be your final idea. We are practicing a skill which you can apply later to other ideas.
- a) space exploration game – create a map of planets, create 6 planet cards each describing the planet, cost to travel to it, potential gain/risk. Player has 10 fuel cards. Player chooses to travel to a planet and trades in fuel cards. Objective is to offer medical services to as many aliens as possible and return to your home planet. Player turns over selected planet card to read outcome of visiting that planet. You may either draw your own planet artwork or borrow images from other sources (do credit sources).
- b) generate kaleidoscope images from web camera input – here you might find actual working examples online. Of course you would code your own version, but you have the advantage of a real working system to show and gather feedback to learn how you might improve/modify the concept.
- c) computer generates music in response to a user singing into a mic – you give a mic to another person and invite them to sing. You simulate the program’s processing and play music using one of three instruments. This type of prototype is known as a “Wizard of Oz” prototype since you in effect hide behind a curtain and do the things that the program would do.
With many prototypes, you can actually agree to change the rules while interacting with another person if you find a better way.
Post an entry to this topic that summarizes the feedback received and how you might improve the prototype.