<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mockery Blog &#187; terminology</title>
	<atom:link href="http://getmockery.com/blog/archives/tag/terminology/feed" rel="self" type="application/rss+xml" />
	<link>http://getmockery.com/blog</link>
	<description>GetMockery.com company blog - Mockery, UI, and more.</description>
	<lastBuildDate>Fri, 16 Dec 2011 19:48:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What do you call them? Mockups? Prototypes? Wireframes?</title>
		<link>http://getmockery.com/blog/archives/36</link>
		<comments>http://getmockery.com/blog/archives/36#comments</comments>
		<pubDate>Sun, 11 Oct 2009 01:32:59 +0000</pubDate>
		<dc:creator>Joel Anair</dc:creator>
				<category><![CDATA[GUI]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[mockup]]></category>
		<category><![CDATA[prototype]]></category>
		<category><![CDATA[terminology]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[wireframe]]></category>

		<guid isPermaLink="false">http://getmockery.com/blog/?p=36</guid>
		<description><![CDATA[One of the snags I run into most often when I talk to people about Mockery is the terminology involved in designing UIs. What one person calls a mockup (or a mock-up) another person may call a prototype or a wireframe. While they all amount to more or less the same thing, here&#8217;s some clarification [...]]]></description>
			<content:encoded><![CDATA[<p>One of the snags I run into most often when I talk to people about Mockery is the terminology involved in designing UIs. What one person calls a mockup (or a mock-up) another person may call a prototype or a wireframe. While they all amount to more or less the same thing, here&#8217;s some clarification on how I see the terms:</p>
<p>A mock-up is an image of a product used to flesh out ideas and solidify the design, done (ideally) before implementation begins. It isn&#8217;t intended to work at all; it is just a representation of what the finished product should look like.</p>
<p>Naturally, then, some confusion comes in when the term &#8220;prototype&#8221; is used to describe a mockup. A prototype is, to my mind, a functional (albeit crude) implementation of something used to prove it can be done and to test the technology involved. The key bit is that <em>it should work</em>. And that&#8217;s part of the problem with prototypes: the fact that they work means that all too often <em>the prototype becomes the release</em>. It&#8217;s happened to me before, and it&#8217;s reason enough to</p>
<p>Wireframe is a term I hear used synonymously with mockup a lot; it seems that a wireframe is a very light, fast mockup without much or any visual flair.</p>
<p>All in all it doesn&#8217;t really matter, but I do have to explain what a mockup is more often than I would expect. Hopefully getting the word out about Mockery will help.</p>
<p>Anybody have any thoughts on what we should call all of this stuff?</p>
<p><strong>Update: </strong><a title="Melissa Bernais's desciption" href="http://www.melissabernais.com/blog/wireframes-v-mock-ups-v-prototypes/" target="_self">http://www.melissabernais.com/blog/wireframes-v-mock-ups-v-prototypes/</a> describes Melissa Bernais&#8217;s take on this really well. I agree with her on all of these; our definitions of prototype are a little different but not incompatible.</p>
]]></content:encoded>
			<wfw:commentRss>http://getmockery.com/blog/archives/36/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

