<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: How to Create a UX Design Library</title>
	<atom:link href="http://www.uie.com/brainsparks/2010/09/14/uietips-design-library/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2010/09/14/uietips-design-library/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sun, 19 May 2013 02:00:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Jagannath Joshi</title>
		<link>http://www.uie.com/brainsparks/2010/09/14/uietips-design-library/comment-page-1/#comment-153063</link>
		<dc:creator>Jagannath Joshi</dc:creator>
		<pubDate>Tue, 28 Sep 2010 01:16:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=2559#comment-153063</guid>
		<description>Very nice, thank you for sharing a wonderful article. It&#039;s been long time I was checking that, organizing the deliverables. I am kind of to keep the things organized, so this awesome poster reveals beyond my expectation. However, I&#039;m still digging more into this, as, are there any standard folder structure for maintaining guidelines/wireframes/codes etc. 

- Jagannath Joshi</description>
		<content:encoded><![CDATA[<p>Very nice, thank you for sharing a wonderful article. It&#8217;s been long time I was checking that, organizing the deliverables. I am kind of to keep the things organized, so this awesome poster reveals beyond my expectation. However, I&#8217;m still digging more into this, as, are there any standard folder structure for maintaining guidelines/wireframes/codes etc. </p>
<p>- Jagannath Joshi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Belveal</title>
		<link>http://www.uie.com/brainsparks/2010/09/14/uietips-design-library/comment-page-1/#comment-152889</link>
		<dc:creator>Roger Belveal</dc:creator>
		<pubDate>Tue, 14 Sep 2010 22:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=2559#comment-152889</guid>
		<description>Good article.  I’ve been through this and Nathan’s point is right on.   Standardization is what do with what has been already built, proven to work, and deemed reusable or extensible.  Componentizing is a special activity best undertaken by a librarian or specialized team. It is difficult to get it to happen spontaneously.  It takes some deliberate investment and a savvy approach, but is worthwhile.  

A reusable component is like a season pass to Sea World or Six Flags.  No one is willing to invest in it for a single visit.  But it will usually pay for itself after the second or third use.  And after that, every visit is virtually free. 

In the end, developers are users too. If you want them to do something, like design per the standard UI Look and feel, you have to make it easier than the alternative.  A reusable components library can help do that. But like a lot of things in the land of Oz, these things have to be done very carefully or you spoil the magic.

Roger Belveal</description>
		<content:encoded><![CDATA[<p>Good article.  I’ve been through this and Nathan’s point is right on.   Standardization is what do with what has been already built, proven to work, and deemed reusable or extensible.  Componentizing is a special activity best undertaken by a librarian or specialized team. It is difficult to get it to happen spontaneously.  It takes some deliberate investment and a savvy approach, but is worthwhile.  </p>
<p>A reusable component is like a season pass to Sea World or Six Flags.  No one is willing to invest in it for a single visit.  But it will usually pay for itself after the second or third use.  And after that, every visit is virtually free. </p>
<p>In the end, developers are users too. If you want them to do something, like design per the standard UI Look and feel, you have to make it easier than the alternative.  A reusable components library can help do that. But like a lot of things in the land of Oz, these things have to be done very carefully or you spoil the magic.</p>
<p>Roger Belveal</p>
]]></content:encoded>
	</item>
</channel>
</rss>
