<?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"
	>
<channel>
	<title>Comments on: Our move</title>
	<atom:link href="http://creativebriefing.com/our-move/feed/" rel="self" type="application/rss+xml" />
	<link>http://creativebriefing.com/our-move/</link>
	<description>for the marketer, designer, and entrepreneur</description>
	<pubDate>Sat, 05 Jul 2008 08:47:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Verne</title>
		<link>http://creativebriefing.com/our-move/#comment-2016</link>
		<dc:creator>Verne</dc:creator>
		<pubDate>Mon, 04 Feb 2008 21:57:56 +0000</pubDate>
		<guid isPermaLink="false">http://creativebriefing.com/our-move/#comment-2016</guid>
		<description>Those are great points, Chris, and that's why I really think that both parties need to meet at some midway point. There's much to be done on both ends.

I definitely agree that devices come in so many shapes and sizes these days that the software developers for these devices really need to come together and agree on some sort of standard in mobile browsing.

On the other hand, probably at least 80% of the websites today aren't following already-established standards that would in reality already do wonders for mobile accessibility. 

Will standardized mobile browsers push non-standard-complying websites to clean up their code? Or will standardized websites encourage greater developments in the mobile browsing space? Did the chicken or the egg come first?

Hard to say, but this web designer wants to stop waiting around and just take the first step forward. Hopefully others will join. :)</description>
		<content:encoded><![CDATA[<p>Those are great points, Chris, and that&#8217;s why I really think that both parties need to meet at some midway point. There&#8217;s much to be done on both ends.</p>
<p>I definitely agree that devices come in so many shapes and sizes these days that the software developers for these devices really need to come together and agree on some sort of standard in mobile browsing.</p>
<p>On the other hand, probably at least 80% of the websites today aren&#8217;t following already-established standards that would in reality already do wonders for mobile accessibility. </p>
<p>Will standardized mobile browsers push non-standard-complying websites to clean up their code? Or will standardized websites encourage greater developments in the mobile browsing space? Did the chicken or the egg come first?</p>
<p>Hard to say, but this web designer wants to stop waiting around and just take the first step forward. Hopefully others will join. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Coyier</title>
		<link>http://creativebriefing.com/our-move/#comment-2015</link>
		<dc:creator>Chris Coyier</dc:creator>
		<pubDate>Mon, 04 Feb 2008 21:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://creativebriefing.com/our-move/#comment-2015</guid>
		<description>I think if I had to put the responsibility on either the web designer or the device, I pick the device. I think there are just too many different devices out there, all with different screen sizes, capabilities, and quirks that a web designer can't possibly be responsible for dealing with each one.

This is what standards are for. Ideally, if a designer designs to established standards, the device should be able to take that content and display it well.</description>
		<content:encoded><![CDATA[<p>I think if I had to put the responsibility on either the web designer or the device, I pick the device. I think there are just too many different devices out there, all with different screen sizes, capabilities, and quirks that a web designer can&#8217;t possibly be responsible for dealing with each one.</p>
<p>This is what standards are for. Ideally, if a designer designs to established standards, the device should be able to take that content and display it well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: giz</title>
		<link>http://creativebriefing.com/our-move/#comment-1961</link>
		<dc:creator>giz</dc:creator>
		<pubDate>Mon, 21 Jan 2008 15:35:46 +0000</pubDate>
		<guid isPermaLink="false">http://creativebriefing.com/our-move/#comment-1961</guid>
		<description>electronic leash.</description>
		<content:encoded><![CDATA[<p>electronic leash.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
