This article on prototyping went into much further detail than the previous article that we had to read a few weeks ago about Paper Prototyping, but I was able to use some of my knowledge gained from that experience to better understand this article.
(But I'm still not sure what a wireframe is!)
While some of the benefits of prototyping are rather obvious; allowing us to see problems more clearly, makes it easier to receive feedback from users, there are other less straightforward benefits. For instance, it fosters collaboration, helps designers and developers consider what is possible to create, and it helps clients and users to gain similar understanding.
What I really appreciated about this article was the negative aspects of prototyping that the author provided. These are things that I wouldn't normally think of. The idea of fidelity, which I found a bit confusing at first, seems rather important. Particularly if paper prototyping is being used, the final product could end up looking quite different than the prototype, leading to possible misconceptions.
Subscribe to:
Post Comments (Atom)
Wireframes... Well, yeah. A thorough blue print might be a good analogy. Though I have heard people argue what they consider to be a true wireframe. Do not feel too overwhelmed by the vocabulary involved, but consider these as mockups to varying degrees.
ReplyDelete