Makey Makey Game Controller Challenge!

Although our Makey Makey Game Controller Challenge deals with building an interface solution for a game, it is actually a game in and of itself! A game format consists of a goal, rules, feedback (and voluntary participation… I guess we’re close to being a game since this is something you’re required to participate in!)

Project Goal (Criteria): Design and build a custom controller for a web-browser based game*. Iterate on your design to craft the best possible physical prototype (as judged by yourself and your peers)!

*Game or other browser based interactive content (Drum machine, etc.)

Project Rules (Specified Constraints):

• Materials:
• One Makey Makey controller and accessories including a grounding wrist strap
• Inventory your items with every class session.
• Do your inventory immediately upon receipt of your kit!
• Let your instructor know if you’re missing anything.
• Inventory your items prior to turning in your Makey Makey
• Your checked off inventory is your “ticket” out of class. Get it checked before you leave!
• Your team may not leave until checked. Plan ahead!
• You may use any of our standard “Design-Build” challenge materials we use in class (straws, paper clips, paper, tape, cardboard, tinfoil, etc.)
• You must clean your work space and return all unused items to their appropriate location.
• Select a storage location for any work in progress.
• Throw out any used materials that are no longer part of your effort and not reusable.
• Design Process
• Iterate!:
• Design, implement, test and rework at least 3 times (iterations).
• Design Feedback
• Solicit and receive feedback with each iteration.
• Feedback Format:
• Core design feedback:
• (+) Sustain
• (delta) Change/Improve
• Bonus design feedback considerations:
• (?) Questions
• (!) Ideas
• Solicit Feedback:
• From yourself
• From your colleagues (team)
• From your peers (other teams)
• Document Your Process
• Select a format that best shares your process and product with the class.
• If desired, we can spend some class time brainstorming the optimal format for this experience. Up to the class to decide
• Remember that a picture is worth a thousand words.
• If a picture is worth a thousand words, what is a video worth?
• Story is the split between expectation and outcome. What “story element” can you incorporate into your documentation to make it more interesting?

Project Considerations (Implied Constraints):

• Choose a game that suits the Makey Makey
• Easier - choose a game that works with the existing key inputs (WASDFG, click, space, mouse movement)
• Moar Hacker - reflash the Makey Makey with a custom arduino file for complete control of your keyboard/mouse inputs.
• Figure it out
• Ask at least 3 other people before you ask Mr. Olson. Chances are that one of your colleagues has the answer you’re looking for.

Project Feedback (Score):

• You gain points for:
• Documenting a complete (3 iterations) process
• Building functional prototypes
• Soliciting Feedback
• Sharing your process and product in a presentation
• Scoring well on peer review
• Having a good attitude
• You lose points for:
• Not cleaning your workspace
• Not completing an accurate inventory
• Losing materials
• Having a bad attitude

Example:

A possible experience might look like this (everyone’s journey is their own, but this could be helpful in seeing how to work within the specified criteria and constraints):

• Pick a game you think is fun and promising for this activity
• Brainstorm some controller ideas
• Implement a solution
• Get feedback from your team
• Re-implement a solution
• Get feedaback from your team and other members of our class
• Re-implement a solution
• Get feedback from a class-wide “Gallery Walk”
• Prepare a google docs presentation telling the “story” of your process and showcasing your product (you were taking photos and videos at each step)
• Share this presentation with your instructor/class, parents and friends :)