Inspiration: Sketching in Code: the Magic of Prototyping

I found this article on the A List Apart website. The author is making the case that wireframes can’t always communicate interactive features of a web application. Sometimes, there’s no substitute for a coded prototype.

I found this interesting because I’ve been tempted over a few of the prototypes we’ve made for class to just bash out some code, and get the interaction I want. In some cases, especially to test out some very specific interactions, I think this can be useful, if the scope is limited.

My concern with this approach, as the author mentions, is the confusion that prototyping in the delivery medium can bring. We definitely had this problem in one project at work. Prototype was synonymous with ‘soon to be finished project’.

One of the big dangers the author mentions is the tendency to over-engineer the prototype, wasting resources. A coded prototype should do no more than answer a specific question in the fastest method possible.

Advertisements
Inspiration: Sketching in Code: the Magic of Prototyping

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s