<?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: Why it&#8217;s Bad to Port Your (Mobile) Interface Without Optimization for the Platform</title>
	<atom:link href="http://www.peterpixel.nl/writings/why-its-bad-to-port-your-mobile-interface-without-optimization-for-the-platform/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterpixel.nl/writings/why-its-bad-to-port-your-mobile-interface-without-optimization-for-the-platform/</link>
	<description></description>
	<lastBuildDate>Fri, 26 Feb 2010 14:48:07 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: peterpixel</title>
		<link>http://www.peterpixel.nl/writings/why-its-bad-to-port-your-mobile-interface-without-optimization-for-the-platform/comment-page-1/#comment-22269</link>
		<dc:creator>peterpixel</dc:creator>
		<pubDate>Thu, 06 Aug 2009 18:02:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterpixel.nl/writings/?p=507#comment-22269</guid>
		<description>Thanks for the comment! 

Yeah, I agree with you that there are certainly possibilities to achieve a certain uniformity across platforms... it&#039;s just that amongst platforms where input varies, it is usually a bad idea to copy the interface.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment! </p>
<p>Yeah, I agree with you that there are certainly possibilities to achieve a certain uniformity across platforms&#8230; it&#8217;s just that amongst platforms where input varies, it is usually a bad idea to copy the interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evert</title>
		<link>http://www.peterpixel.nl/writings/why-its-bad-to-port-your-mobile-interface-without-optimization-for-the-platform/comment-page-1/#comment-22245</link>
		<dc:creator>Evert</dc:creator>
		<pubDate>Wed, 05 Aug 2009 12:04:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterpixel.nl/writings/?p=507#comment-22245</guid>
		<description>There are a few possibilities when it comes to designing &amp; developing for different mobile platforms and browsers. A general solution is to group different types of mobiles in groups. Jacob Nielsen wrote a piece on how you could group the different mobile phones. Then make a different interaction design for each of these groups but keep all the functionalities intact. For the developing part, there are a few atlases with all mobile phones and there user-agent id, you could group on those. A other possibility is to group based on css media queries. &quot;screen&quot;, &quot;mobile&quot;, viewport width and height etc. You adjust the interface by css and keep the xhtml and others intact. With this solution you should really mind the use of Javascript as most of the older mobile browsers dont support full javascript or even html.

Find out more in my thesis (Dutch) on http://brisdom.com/graduation/</description>
		<content:encoded><![CDATA[<p>There are a few possibilities when it comes to designing &amp; developing for different mobile platforms and browsers. A general solution is to group different types of mobiles in groups. Jacob Nielsen wrote a piece on how you could group the different mobile phones. Then make a different interaction design for each of these groups but keep all the functionalities intact. For the developing part, there are a few atlases with all mobile phones and there user-agent id, you could group on those. A other possibility is to group based on css media queries. &#8220;screen&#8221;, &#8220;mobile&#8221;, viewport width and height etc. You adjust the interface by css and keep the xhtml and others intact. With this solution you should really mind the use of Javascript as most of the older mobile browsers dont support full javascript or even html.</p>
<p>Find out more in my thesis (Dutch) on <a href="http://brisdom.com/graduation/" rel="nofollow">http://brisdom.com/graduation/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
