<?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: Is Mobile Diversity A Good Thing?</title>
	<atom:link href="http://www.appdots.com/blog/2009/03/30/is-mobile-diversity-a-good-thing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.appdots.com/blog/2009/03/30/is-mobile-diversity-a-good-thing/</link>
	<description>Programming for Mobile Platforms</description>
	<lastBuildDate>Mon, 18 May 2009 14:56:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Shiraz</title>
		<link>http://www.appdots.com/blog/2009/03/30/is-mobile-diversity-a-good-thing/comment-page-1/#comment-11</link>
		<dc:creator>Shiraz</dc:creator>
		<pubDate>Tue, 31 Mar 2009 03:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.appdots.com/blog/?p=217#comment-11</guid>
		<description>I believe MS is more concerned with the end user and less so with the 3rd party developers. That is a philosophy that will more than likely change in the not too distant future in light of the success of the iPhone and the App store. 

As to original design philosophy of Windows Mobile: Think they were trying to extend the standard Windows desktop/server experience to the mobile arena. Would have worked fine if the hardware manufacturers played along. Having all hardware built from the ground up with the OS is novel for a PC. I personally don&#039;t think it has done anything other than make Macs more expensive, but when you&#039;re limited by the level of hardware you have available building OS and hardware hand in hand winds up benefiting the developers considerably.

Of course, if hardware manufacturers worked on standardized drivers for their hardware running Windows Mobile, quite a bit of this head ache could be eliminated from the developer plate. Update the app to work with BLAH set of drivers and in theory, you&#039;re good to go.

Rambling again. Microsoft tries the clusterbomb approach to market share. Dumb it/Cheap it down to the point where Joe Average can acquire/use your product. Way more Joe Averages out there.</description>
		<content:encoded><![CDATA[<p>I believe MS is more concerned with the end user and less so with the 3rd party developers. That is a philosophy that will more than likely change in the not too distant future in light of the success of the iPhone and the App store. </p>
<p>As to original design philosophy of Windows Mobile: Think they were trying to extend the standard Windows desktop/server experience to the mobile arena. Would have worked fine if the hardware manufacturers played along. Having all hardware built from the ground up with the OS is novel for a PC. I personally don&#8217;t think it has done anything other than make Macs more expensive, but when you&#8217;re limited by the level of hardware you have available building OS and hardware hand in hand winds up benefiting the developers considerably.</p>
<p>Of course, if hardware manufacturers worked on standardized drivers for their hardware running Windows Mobile, quite a bit of this head ache could be eliminated from the developer plate. Update the app to work with BLAH set of drivers and in theory, you&#8217;re good to go.</p>
<p>Rambling again. Microsoft tries the clusterbomb approach to market share. Dumb it/Cheap it down to the point where Joe Average can acquire/use your product. Way more Joe Averages out there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brett</title>
		<link>http://www.appdots.com/blog/2009/03/30/is-mobile-diversity-a-good-thing/comment-page-1/#comment-10</link>
		<dc:creator>brett</dc:creator>
		<pubDate>Tue, 31 Mar 2009 01:14:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.appdots.com/blog/?p=217#comment-10</guid>
		<description>Microsoft gives the ODM (original device manufacturer) options and it is up to them to run with whatever form factors they can get the OS on.  It is a customer oriented thought process, but if developers are stuck supporting 15 different device formats, customer experience with software may vary from device to device.  That is bad for the entire platform in my opinion, but I&#039;m not sure what the answer is.</description>
		<content:encoded><![CDATA[<p>Microsoft gives the ODM (original device manufacturer) options and it is up to them to run with whatever form factors they can get the OS on.  It is a customer oriented thought process, but if developers are stuck supporting 15 different device formats, customer experience with software may vary from device to device.  That is bad for the entire platform in my opinion, but I&#8217;m not sure what the answer is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: justin</title>
		<link>http://www.appdots.com/blog/2009/03/30/is-mobile-diversity-a-good-thing/comment-page-1/#comment-9</link>
		<dc:creator>justin</dc:creator>
		<pubDate>Mon, 30 Mar 2009 16:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.appdots.com/blog/?p=217#comment-9</guid>
		<description>I wonder if Microsoft thinks they&#039;re doing us a favor when they separate out everything into 20 different &quot;confusing&quot; versions?</description>
		<content:encoded><![CDATA[<p>I wonder if Microsoft thinks they&#8217;re doing us a favor when they separate out everything into 20 different &#8220;confusing&#8221; versions?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
