<?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: Multi-Device Adaptation vs. Optimization</title>
	<atom:link href="http://www.uie.com/brainsparks/2012/07/18/uietips-adaptation-vs-optimization/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2012/07/18/uietips-adaptation-vs-optimization/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Fri, 24 May 2013 16:22:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Bo Simmons</title>
		<link>http://www.uie.com/brainsparks/2012/07/18/uietips-adaptation-vs-optimization/comment-page-1/#comment-229723</link>
		<dc:creator>Bo Simmons</dc:creator>
		<pubDate>Mon, 06 Aug 2012 21:48:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=7548#comment-229723</guid>
		<description>Jared thanks again for helping us with good ways of speaking to clients.  We are in the middle of a couple of projects that will use responsive solutions.  I feel there one more angle related to curating and maintaining content that is worth mentioning.  Client stakeholders at 2 out of 3 of these projects have concerns with their limited resources and ability to carve up and maintain specialized content for mobile, even if those are only slight differences in the content. 

To follow your packing for a trip scenario a little further, my wife would rather travel with her entire closet than make decisions about what not to have with her – she needs it all even if she can only wear a few things.  As we discussed and planned these projects, it was clear that the clients wanted a more mobile friendly solution but were unable / unwilling to support more effort related to content. The responsive solution quickly became the best compromise approach with the minimal wear and tear on content changes both initially and ongoing.  This approach also allowed us to press a mobile 1st philosophy and we are selectively fixing key pages that have wordy- text heavy content on the desktop site so the page will perform better on the mobile responsive solution.  

Thanks,
Bo Simmons
Cool Blue Interactive 
Atlanta Ga.</description>
		<content:encoded><![CDATA[<p>Jared thanks again for helping us with good ways of speaking to clients.  We are in the middle of a couple of projects that will use responsive solutions.  I feel there one more angle related to curating and maintaining content that is worth mentioning.  Client stakeholders at 2 out of 3 of these projects have concerns with their limited resources and ability to carve up and maintain specialized content for mobile, even if those are only slight differences in the content. </p>
<p>To follow your packing for a trip scenario a little further, my wife would rather travel with her entire closet than make decisions about what not to have with her – she needs it all even if she can only wear a few things.  As we discussed and planned these projects, it was clear that the clients wanted a more mobile friendly solution but were unable / unwilling to support more effort related to content. The responsive solution quickly became the best compromise approach with the minimal wear and tear on content changes both initially and ongoing.  This approach also allowed us to press a mobile 1st philosophy and we are selectively fixing key pages that have wordy- text heavy content on the desktop site so the page will perform better on the mobile responsive solution.  </p>
<p>Thanks,<br />
Bo Simmons<br />
Cool Blue Interactive<br />
Atlanta Ga.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
