Everyone’s feedback/reactions were different, but there were a couple that gave me ideas for improvement. It’s interesting – most of the changes they suggested or implied through their questions are things I’d thought about but decided not to push because of time. Suggestions included:
- adding an audio option for the onscreen text of the main site
- adding music to the second animation
- removing a semi-redundant frame from the second animation
- including a “hint button” for the “do it yourself” labels
- providing another visual representation of a completed gradient
- adding a vertical line as a guide to line up the labels
One question posed after the interactive movie was “how do you know if you’re right?” Well, that’s a fair question, but once again, this was not a game. This was a tutorial with a hands-on component to practice. It’s not designed to be used in classrooms – it’s designed to teach you a strategy that you can use. Normally teachers would read about a strategy and have no opportunity to practice, so this improves that to some degree.
I’m not sure how to provide “feedback” unless the words are pre-selected. Otherwise, working with a partner and using resources is the only way to “check” your work for an “open-ended” activity such as this. This is a drawback when people are expecting the “game” atmosphere. I’ll have to figure out a way to make it clear. I don’t know another solution.
In all it was a great experience – designing and developing. I truly felt as though I was problem-solving at all times. At each point, I had to reflect on where I was, converse with materials, decide how each solution would impact the design and then act (Gal, 1996). One of the reasons I chose IT as a major is because of my abiding interest in multimedia development. In a past life I wanted to create educational games. I’ve kind of gotten away from that – namely because I don’t want to “research” them, which is more the focus of a PhD program. But I will continue to factor in design and development work in my future.
References
- Gal, S. (1996). Footholds for design. In Winograd, T. (Ed.), Bringing Design to Software (pp. 215-227). New York: Addison-Wesley.





