<?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: Design in the open: baring your wireframes in public</title>
	<atom:link href="http://johnnyholland.org/2009/02/11/design-in-the-open/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnnyholland.org/2009/02/11/design-in-the-open/</link>
	<description></description>
	<lastBuildDate>Mon, 15 Mar 2010 20:14:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mark vernon</title>
		<link>http://johnnyholland.org/2009/02/11/design-in-the-open/comment-page-1/#comment-2772</link>
		<dc:creator>mark vernon</dc:creator>
		<pubDate>Tue, 17 Feb 2009 07:27:41 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=1131#comment-2772</guid>
		<description>We&#039;ve designed iplotz.com as a mockups and wireframing tool to do just what you have been discussing. Currently you can share projects by sending out emails with the URL as a clickable wireframe, or you can ask people to login (free) and view your work and comment on it. 

We are now adding a section to the website where public projects are posted for users to browse, search, view and comment, as well as bid to do the actual design and coding should the wireframer choose.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve designed iplotz.com as a mockups and wireframing tool to do just what you have been discussing. Currently you can share projects by sending out emails with the URL as a clickable wireframe, or you can ask people to login (free) and view your work and comment on it. </p>
<p>We are now adding a section to the website where public projects are posted for users to browse, search, view and comment, as well as bid to do the actual design and coding should the wireframer choose.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pieter Jongerius</title>
		<link>http://johnnyholland.org/2009/02/11/design-in-the-open/comment-page-1/#comment-2183</link>
		<dc:creator>Pieter Jongerius</dc:creator>
		<pubDate>Thu, 12 Feb 2009 23:30:41 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=1131#comment-2183</guid>
		<description>I was totally impressed by this very sympathetic and effective idea of an open process, when it was presented at IxDA Interaction&#039;09 (as covered briefly here: http://johnnyholland.org/magazine/2009/02/live-at-interaction09-day-3/). Still, I wonder how market competition will put a brake on this development. For instance, I would hesitate doing this for an e-commerce initiative. We may only get to implement this in non-competition markets or when time-to-market is minimal. Thoughts on that, anyone?</description>
		<content:encoded><![CDATA[<p>I was totally impressed by this very sympathetic and effective idea of an open process, when it was presented at IxDA Interaction&#8217;09 (as covered briefly here: <a href="http://johnnyholland.org/magazine/2009/02/live-at-interaction09-day-3/)" rel="nofollow">http://johnnyholland.org/magazine/2009/02/live-at-interaction09-day-3/)</a>. Still, I wonder how market competition will put a brake on this development. For instance, I would hesitate doing this for an e-commerce initiative. We may only get to implement this in non-competition markets or when time-to-market is minimal. Thoughts on that, anyone?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakub Linowski</title>
		<link>http://johnnyholland.org/2009/02/11/design-in-the-open/comment-page-1/#comment-2099</link>
		<dc:creator>Jakub Linowski</dc:creator>
		<pubDate>Thu, 12 Feb 2009 00:52:49 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=1131#comment-2099</guid>
		<description>I&#039;m just starting another project which is all about designing in the open - fluidIA. I&#039;ve never done something like this, but the intention is to create a UI prototyping tool and expand concepts from open source into open design. Cheers :)</description>
		<content:encoded><![CDATA[<p>I&#8217;m just starting another project which is all about designing in the open &#8211; fluidIA. I&#8217;ve never done something like this, but the intention is to create a UI prototyping tool and expand concepts from open source into open design. Cheers :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeroen van Geel</title>
		<link>http://johnnyholland.org/2009/02/11/design-in-the-open/comment-page-1/#comment-2066</link>
		<dc:creator>Jeroen van Geel</dc:creator>
		<pubDate>Wed, 11 Feb 2009 20:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=1131#comment-2066</guid>
		<description>I really like this way of working. It&#039;s so open. This is what the web is made for!</description>
		<content:encoded><![CDATA[<p>I really like this way of working. It&#8217;s so open. This is what the web is made for!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Zaki Warfel</title>
		<link>http://johnnyholland.org/2009/02/11/design-in-the-open/comment-page-1/#comment-2057</link>
		<dc:creator>Todd Zaki Warfel</dc:creator>
		<pubDate>Wed, 11 Feb 2009 19:42:52 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=1131#comment-2057</guid>
		<description>We&#039;re actually considering this model for a software application we&#039;re currently redesigning for a client—opening it up a prototype to their customers and let them use it and give feedback prior to development—kind of similar to the drupal.org redesign model.</description>
		<content:encoded><![CDATA[<p>We&#8217;re actually considering this model for a software application we&#8217;re currently redesigning for a client—opening it up a prototype to their customers and let them use it and give feedback prior to development—kind of similar to the drupal.org redesign model.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
