<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Present-Future Sketching</title>
	<atom:link href="http://wireframes.linowski.ca/2009/12/present-future-sketching/feed/" rel="self" type="application/rss+xml" />
	<link>http://wireframes.linowski.ca/2009/12/present-future-sketching/</link>
	<description>Because every IA has something funky up their sleeve</description>
	<lastBuildDate>Wed, 28 Jul 2010 06:45:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Francisco</title>
		<link>http://wireframes.linowski.ca/2009/12/present-future-sketching/comment-page-1/#comment-9840</link>
		<dc:creator>Francisco</dc:creator>
		<pubDate>Sun, 10 Jan 2010 01:11:05 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=1906#comment-9840</guid>
		<description>Hello I would like to share my experience at work with a similar method to the one you describe. 
We have designed some applications for one of the Archos Android device. In order to do it, we did some paper prototyping. When we used an A4, it was very easy to draw new concepts, but it was also very easy to get unreadable elements in the UI. One of our collaborators created a simple mockup of the android interface in the correct measures, so that we could draw in the size of the screen. It has been very useful. 
 
&lt;a href=&quot;http://twitpic.com/xftzm&quot; target=&quot;_blank&quot;&gt;http://twitpic.com/xftzm&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Hello I would like to share my experience at work with a similar method to the one you describe.<br />
We have designed some applications for one of the Archos Android device. In order to do it, we did some paper prototyping. When we used an A4, it was very easy to draw new concepts, but it was also very easy to get unreadable elements in the UI. One of our collaborators created a simple mockup of the android interface in the correct measures, so that we could draw in the size of the screen. It has been very useful. </p>
<p><a href="http://twitpic.com/xftzm" target="_blank">http://twitpic.com/xftzm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Lillo</title>
		<link>http://wireframes.linowski.ca/2009/12/present-future-sketching/comment-page-1/#comment-9523</link>
		<dc:creator>Alex Lillo</dc:creator>
		<pubDate>Mon, 04 Jan 2010 16:51:18 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=1906#comment-9523</guid>
		<description>Just like Ondrej says, I&#039;ve done something similar in small redesigns, without even notice or  emphasize this effect. First I wireframe the existing website, and with this information I start playing to create the new one. 
 
Maybe a screenshot layer could be a better idea for presenting the work to the client, mainly for those who are&#039;nt fluent with wireframes. </description>
		<content:encoded><![CDATA[<p>Just like Ondrej says, I&#039;ve done something similar in small redesigns, without even notice or  emphasize this effect. First I wireframe the existing website, and with this information I start playing to create the new one. </p>
<p>Maybe a screenshot layer could be a better idea for presenting the work to the client, mainly for those who are&#039;nt fluent with wireframes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ondrej</title>
		<link>http://wireframes.linowski.ca/2009/12/present-future-sketching/comment-page-1/#comment-9227</link>
		<dc:creator>Ondrej</dc:creator>
		<pubDate>Wed, 30 Dec 2009 13:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=1906#comment-9227</guid>
		<description>I have used such approach for less complex redesigns, where most of the page stays the same and just some part of the page changes. For more complex redesigns it makes the result looking too messy, even if you make the underlying original very light and black&amp;white. But from my experience most of the redesings are much more complex than just changing some small part of the page or adding something new (keeping the size and position of the rest), and then it is better to present the changes  for example with manually made fade-in transition from the old design screenshot to the new design screenshot. 
 
Nevertheless this present-future redesign using overlay can be easily done with a combination of the Firefox plug-in FireShot (to capture the entire page - not limited by the visible area) and Axure RP, where the screenshot is placed in the page template as the &quot;locked&quot; background with some amount of transparency (to make it lighter than the new changes). </description>
		<content:encoded><![CDATA[<p>I have used such approach for less complex redesigns, where most of the page stays the same and just some part of the page changes. For more complex redesigns it makes the result looking too messy, even if you make the underlying original very light and black&amp;white. But from my experience most of the redesings are much more complex than just changing some small part of the page or adding something new (keeping the size and position of the rest), and then it is better to present the changes  for example with manually made fade-in transition from the old design screenshot to the new design screenshot. </p>
<p>Nevertheless this present-future redesign using overlay can be easily done with a combination of the Firefox plug-in FireShot (to capture the entire page &#8211; not limited by the visible area) and Axure RP, where the screenshot is placed in the page template as the &quot;locked&quot; background with some amount of transparency (to make it lighter than the new changes).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
