<?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: UI Design Guidelines for Responsive Design</title>
	<atom:link href="http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/</link>
	<description>Useful resources and inspiration for creative minds</description>
	<lastBuildDate>Wed, 22 May 2013 07:14:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: adam</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-435605</link>
		<dc:creator>adam</dc:creator>
		<pubDate>Tue, 09 Apr 2013 12:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-435605</guid>
		<description><![CDATA[Thanks for the link.. i am sure you will love -- www.uxzeal.com]]></description>
		<content:encoded><![CDATA[<p>Thanks for the link.. i am sure you will love &#8212; <a href="http://www.uxzeal.com" rel="nofollow">http://www.uxzeal.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Smith</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-433469</link>
		<dc:creator>Tony Smith</dc:creator>
		<pubDate>Fri, 08 Mar 2013 12:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-433469</guid>
		<description><![CDATA[Thank you so much for great article.Responsive website design might turn out as a great way to progressively enhance even small budget projects for mobile devices.]]></description>
		<content:encoded><![CDATA[<p>Thank you so much for great article.Responsive website design might turn out as a great way to progressively enhance even small budget projects for mobile devices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-432756</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Tue, 26 Feb 2013 23:19:51 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-432756</guid>
		<description><![CDATA[Nice write up overall, first off.  But I have a bone to pick, and it isn&#039;t just you that is doing this.  I have seen a ton of write up&#039;s lately talking about &#039;retina displays&#039; and acting as if they are unique to Apple.   Apple wasn&#039;t the first company to have a hi-res screen.  Further more, there are multiple devices with much higher ppi than any of the Apple &#039;retina displays&#039;.

If you are going to write an article and make these blanket claims, could we at least do a little research first on the &#039;facts&#039; you are throwing out there, especially something as basic as claiming only one tablet or one company has a &#039;retina&#039; level display (btw, retina is marketing, not a real technical term).  Every major player is making ulra-hi-res devices, from phones all the way to computers.  Heck, the highest ppi device is 100+ ppi above the iPhone, and 200+ above the iPad.]]></description>
		<content:encoded><![CDATA[<p>Nice write up overall, first off.  But I have a bone to pick, and it isn&#8217;t just you that is doing this.  I have seen a ton of write up&#8217;s lately talking about &#8216;retina displays&#8217; and acting as if they are unique to Apple.   Apple wasn&#8217;t the first company to have a hi-res screen.  Further more, there are multiple devices with much higher ppi than any of the Apple &#8216;retina displays&#8217;.</p>
<p>If you are going to write an article and make these blanket claims, could we at least do a little research first on the &#8216;facts&#8217; you are throwing out there, especially something as basic as claiming only one tablet or one company has a &#8216;retina&#8217; level display (btw, retina is marketing, not a real technical term).  Every major player is making ulra-hi-res devices, from phones all the way to computers.  Heck, the highest ppi device is 100+ ppi above the iPhone, and 200+ above the iPad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrea</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-431772</link>
		<dc:creator>Andrea</dc:creator>
		<pubDate>Tue, 29 Jan 2013 17:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-431772</guid>
		<description><![CDATA[Hi,
thank you for sharing such interesting thoughts!
I&#039;m reading more and more about the increasing need to create different interfaces for different devices; and I can&#039;t help asking myself a question: how shall we manage the inevitably related increased budget with our clients?
The creation of different interfaces means more production time and, in turn, more budget for the clients.
Thinking about how difficult it is to have them take the cost of the only desktop version, I think it will be a great challenge to educate them to the new multi-design needs and the related increased budgets.
Here in Italy, it&#039;s not unusual to be asked to design for desktop, tablet and smartphone without increasing the bill!
How do you think abotu that ? Which strategies should be considered as to this issue?]]></description>
		<content:encoded><![CDATA[<p>Hi,<br />
thank you for sharing such interesting thoughts!<br />
I&#8217;m reading more and more about the increasing need to create different interfaces for different devices; and I can&#8217;t help asking myself a question: how shall we manage the inevitably related increased budget with our clients?<br />
The creation of different interfaces means more production time and, in turn, more budget for the clients.<br />
Thinking about how difficult it is to have them take the cost of the only desktop version, I think it will be a great challenge to educate them to the new multi-design needs and the related increased budgets.<br />
Here in Italy, it&#8217;s not unusual to be asked to design for desktop, tablet and smartphone without increasing the bill!<br />
How do you think abotu that ? Which strategies should be considered as to this issue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Pietrusky</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-431625</link>
		<dc:creator>Tim Pietrusky</dc:creator>
		<pubDate>Sat, 26 Jan 2013 20:23:07 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-431625</guid>
		<description><![CDATA[I think that you should not think in &quot;devices&quot;. It could be anything... a computer in a car, a fridge or glass. You can&#039;t predict what your users are using.]]></description>
		<content:encoded><![CDATA[<p>I think that you should not think in &#8220;devices&#8221;. It could be anything&#8230; a computer in a car, a fridge or glass. You can&#8217;t predict what your users are using.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kayla</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-431619</link>
		<dc:creator>Kayla</dc:creator>
		<pubDate>Sat, 26 Jan 2013 16:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-431619</guid>
		<description><![CDATA[Excellent point -- my personal computer is even a touchscreen and I failed to mention this! I think the biggest concern would still be on tablets/mobile though, because on a desktop, even if its touchscreen, there is a keyboard and mouse option, which is usually the primary input source anyway. Of course, you make an excellent point -- it doesn&#039;t hurt to think about touchscreens on desktop to improve the user experience if they are using them at any given time, and how that implementation will likely grow in the future. 

We can say the same with retina display too -- with the new Macbook having retina display as well. Put the focus on implementing it with mobile, but we should always be reminded that retina, touchscreen, and more are all coming to desktops soon!]]></description>
		<content:encoded><![CDATA[<p>Excellent point &#8212; my personal computer is even a touchscreen and I failed to mention this! I think the biggest concern would still be on tablets/mobile though, because on a desktop, even if its touchscreen, there is a keyboard and mouse option, which is usually the primary input source anyway. Of course, you make an excellent point &#8212; it doesn&#8217;t hurt to think about touchscreens on desktop to improve the user experience if they are using them at any given time, and how that implementation will likely grow in the future. </p>
<p>We can say the same with retina display too &#8212; with the new Macbook having retina display as well. Put the focus on implementing it with mobile, but we should always be reminded that retina, touchscreen, and more are all coming to desktops soon!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kayla</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-431618</link>
		<dc:creator>Kayla</dc:creator>
		<pubDate>Sat, 26 Jan 2013 16:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-431618</guid>
		<description><![CDATA[I tend to do use separate mobile and desktop stylesheets, while still using the same pages. For large images that are relevant to the design, I use background image that can easily be swapped out on desktop/mobile. So, when using completely separate stylesheets, on mobile only the mobile stylesheet is downloaded, referencing only the mobile background images. For all other images (using an img tag), there are of course plenty of responsive images plugins (JS) available that  will help do the job. :)]]></description>
		<content:encoded><![CDATA[<p>I tend to do use separate mobile and desktop stylesheets, while still using the same pages. For large images that are relevant to the design, I use background image that can easily be swapped out on desktop/mobile. So, when using completely separate stylesheets, on mobile only the mobile stylesheet is downloaded, referencing only the mobile background images. For all other images (using an img tag), there are of course plenty of responsive images plugins (JS) available that  will help do the job. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maverick</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-431497</link>
		<dc:creator>maverick</dc:creator>
		<pubDate>Fri, 25 Jan 2013 14:14:02 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-431497</guid>
		<description><![CDATA[Good article! 
However, you should add one thing to your list, since for me that&#039;s one of the greatest drawback of the &quot;Responsive Web Design&quot;.
Be careful when you decide to change something between 2 breakpoints (hiding content, adding content, changing display...) because sometimes, the final user can be really lost if there&#039;s too much differences between 2 versions of the same page. 
Besides, I believe that the user should always be able to choose his favorite kind of display (layout/menu/etc.), and if he wants to see the desktop version on his mobile phone, he should be able to do it. With RWD and especially due to media-queries, user is not anymore able to choose the version of a website he wants... What a pity :(]]></description>
		<content:encoded><![CDATA[<p>Good article!<br />
However, you should add one thing to your list, since for me that&#8217;s one of the greatest drawback of the &#8220;Responsive Web Design&#8221;.<br />
Be careful when you decide to change something between 2 breakpoints (hiding content, adding content, changing display&#8230;) because sometimes, the final user can be really lost if there&#8217;s too much differences between 2 versions of the same page.<br />
Besides, I believe that the user should always be able to choose his favorite kind of display (layout/menu/etc.), and if he wants to see the desktop version on his mobile phone, he should be able to do it. With RWD and especially due to media-queries, user is not anymore able to choose the version of a website he wants&#8230; What a pity :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emok</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-431373</link>
		<dc:creator>emok</dc:creator>
		<pubDate>Thu, 24 Jan 2013 12:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-431373</guid>
		<description><![CDATA[awesome]]></description>
		<content:encoded><![CDATA[<p>awesome</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Bauer</title>
		<link>http://tympanus.net/codrops/2013/01/21/ui-design-guidelines-for-responsive-design/comment-page-1/#comment-431332</link>
		<dc:creator>Sarah Bauer</dc:creator>
		<pubDate>Wed, 23 Jan 2013 22:18:41 +0000</pubDate>
		<guid isPermaLink="false">http://tympanus.net/codrops/?p=13660#comment-431332</guid>
		<description><![CDATA[Very thoughtful analysis of UI design guidelines for responsive web. I&#039;d add that it&#039;s important while designing for smart phones to strike a balance between assumptions about the &quot;mobile context&quot; and the burgeoning demographic of users accessing the Internet solely from a mobile device. Those users (31 percent of Americans as of June 2012), may need access to all the desktop content, not just a pared down &quot;mobile&quot; version.  Things to think about as designers create new ways to deliver content through these channels. 

Check out Karen McGrane&#039;s article &quot;Uncle Sam Wants You (To Optimize Your Content for Mobile)&quot; over at A List Apart for more stats and insights!

Cheers
Sarah Bauer
Navigator Multimedia]]></description>
		<content:encoded><![CDATA[<p>Very thoughtful analysis of UI design guidelines for responsive web. I&#8217;d add that it&#8217;s important while designing for smart phones to strike a balance between assumptions about the &#8220;mobile context&#8221; and the burgeoning demographic of users accessing the Internet solely from a mobile device. Those users (31 percent of Americans as of June 2012), may need access to all the desktop content, not just a pared down &#8220;mobile&#8221; version.  Things to think about as designers create new ways to deliver content through these channels. </p>
<p>Check out Karen McGrane&#8217;s article &#8220;Uncle Sam Wants You (To Optimize Your Content for Mobile)&#8221; over at A List Apart for more stats and insights!</p>
<p>Cheers<br />
Sarah Bauer<br />
Navigator Multimedia</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 7/25 queries in 0.016 seconds using disk: basic
Content Delivery Network via codropspz.tympanus.netdna-cdn.com

 Served from: tympanus.net @ 2013-05-22 10:01:27 by W3 Total Cache -->