<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Google&#8217;s Android Fragmentation Problem Persists: AdMob</title>
	<atom:link href="http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 01:30:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Finally! 58.8% of Android Handsets Run a Recent OS Version</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249455</link>
		<dc:creator><![CDATA[Finally! 58.8% of Android Handsets Run a Recent OS Version]]></dc:creator>
		<pubDate>Wed, 21 Jul 2010 14:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249455</guid>
		<description><![CDATA[&lt;p&gt;[...] which is now four releases behind the most current release, known as Froyo. As recently as March, Android devices were distributed fairly equally between versions 1.5, 1.6 and 2.x. Such fragmentation between different versions results in a varied user experience and applications [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] which is now four releases behind the most current release, known as Froyo. As recently as March, Android devices were distributed fairly equally between versions 1.5, 1.6 and 2.x. Such fragmentation between different versions results in a varied user experience and applications [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everything You Need to Know About Froyo</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249454</link>
		<dc:creator><![CDATA[Everything You Need to Know About Froyo]]></dc:creator>
		<pubDate>Tue, 29 Jun 2010 15:05:28 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249454</guid>
		<description><![CDATA[&lt;p&gt;[...] and with Froyo, there are now four versions of the OS in the wild: 1.5, 1.6, 2.1 and 2.2. Some call it a legacy issue while others like me believe this situation to be a fragmentation challenge. Call it what you want, [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] and with Froyo, there are now four versions of the OS in the wild: 1.5, 1.6, 2.1 and 2.2. Some call it a legacy issue while others like me believe this situation to be a fragmentation challenge. Call it what you want, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Android Daily Activations Top 160,000; All Verizon Droids Will Get Froyo</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249453</link>
		<dc:creator><![CDATA[Android Daily Activations Top 160,000; All Verizon Droids Will Get Froyo]]></dc:creator>
		<pubDate>Wed, 23 Jun 2010 19:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249453</guid>
		<description><![CDATA[&lt;p&gt;[...] the Android operating system faster than handset makers can design, build and sell such phones, a relatively new handset can be stuck running an older version of Android for some time. Indeed, the just-announced Droid X will have neither Froyo nor Flash support when it becomes [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] the Android operating system faster than handset makers can design, build and sell such phones, a relatively new handset can be stuck running an older version of Android for some time. Indeed, the just-announced Droid X will have neither Froyo nor Flash support when it becomes [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 3 Reasons Nokia Isn&#8217;t Attracting More Mobile Developers</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249452</link>
		<dc:creator><![CDATA[3 Reasons Nokia Isn&#8217;t Attracting More Mobile Developers]]></dc:creator>
		<pubDate>Wed, 16 Jun 2010 02:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249452</guid>
		<description><![CDATA[&lt;p&gt;[...] eight E-series handsets, the unique N900 and a few more smartphones coming soon. It reminds of the current Google Android fragmentation issues, but far worse. The various Nokia smartphones all run Symbian S60 &#8212; except for the N900, [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] eight E-series handsets, the unique N900 and a few more smartphones coming soon. It reminds of the current Google Android fragmentation issues, but far worse. The various Nokia smartphones all run Symbian S60 &#8212; except for the N900, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is Anyone Home at the Android Market or Has Google Gone Fishin&#8217;?</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249451</link>
		<dc:creator><![CDATA[Is Anyone Home at the Android Market or Has Google Gone Fishin&#8217;?]]></dc:creator>
		<pubDate>Tue, 08 Jun 2010 22:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249451</guid>
		<description><![CDATA[&lt;p&gt;[...] problem, although some at Google call it a &#8220;compatibility&#8221; issue. At last check, Android handset usage was equally split between Android 1.5, 1.6 and 2.x. Each new version of Android brings potential API changes and while it&#8217;s up to developers to [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] problem, although some at Google call it a &#8220;compatibility&#8221; issue. At last check, Android handset usage was equally split between Android 1.5, 1.6 and 2.x. Each new version of Android brings potential API changes and while it&#8217;s up to developers to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonesable</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249450</link>
		<dc:creator><![CDATA[Jonesable]]></dc:creator>
		<pubDate>Wed, 19 May 2010 12:53:34 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249450</guid>
		<description><![CDATA[&lt;p&gt;Im into tech, love android, hate the fragmentation. I understand the sentiment of a varied market and understand that ALL android devices cant carry the lastest version (hardware spec wise and business wise) , but from Cupcake to Eclair ,the Android version discrepency is frustrating as a consumer. Other Android lovers like to say fragmentation isnt a big issue but looking at the big picture and the future of Android I think it is...but I&#039;m hopeful Froyo will take steps to correct it and carriers and makers cooperate accordingly.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Im into tech, love android, hate the fragmentation. I understand the sentiment of a varied market and understand that ALL android devices cant carry the lastest version (hardware spec wise and business wise) , but from Cupcake to Eclair ,the Android version discrepency is frustrating as a consumer. Other Android lovers like to say fragmentation isnt a big issue but looking at the big picture and the future of Android I think it is&#8230;but I&#8217;m hopeful Froyo will take steps to correct it and carriers and makers cooperate accordingly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why the iPhone Platform is Still the Best Game in Town</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249449</link>
		<dc:creator><![CDATA[Why the iPhone Platform is Still the Best Game in Town]]></dc:creator>
		<pubDate>Fri, 14 May 2010 19:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249449</guid>
		<description><![CDATA[&lt;p&gt;[...] A very stable platform with extremely predictable release cycles. Can the same be said for Android after just one year? Who knows when the next device will be making its way to consumer, what version of the OS it will [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] A very stable platform with extremely predictable release cycles. Can the same be said for Android after just one year? Who knows when the next device will be making its way to consumer, what version of the OS it will [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B.M.</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249448</link>
		<dc:creator><![CDATA[B.M.]]></dc:creator>
		<pubDate>Thu, 13 May 2010 00:03:52 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249448</guid>
		<description><![CDATA[&lt;p&gt;big diff between apple and android is:
Apple needs to make a big fat gross margin on their unit sales to please Wall Street; whereas,
Android sellers like Moto, Samsung, and HTC only need to make a small margin and don&#039;t take on the cost of marketing the phones very much.  So Android phones are going to end up being cheaper than iPhones, and more open to design changes.&lt;/p&gt;

&lt;p&gt;THAT is why Apple will ultimately lose.  That and not enough variety.  Still waiting for an iPhone with physical QWERTY to rival RIMM&#039;s functionality.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>big diff between apple and android is:<br />
Apple needs to make a big fat gross margin on their unit sales to please Wall Street; whereas,<br />
Android sellers like Moto, Samsung, and HTC only need to make a small margin and don&#8217;t take on the cost of marketing the phones very much.  So Android phones are going to end up being cheaper than iPhones, and more open to design changes.</p>
<p>THAT is why Apple will ultimately lose.  That and not enough variety.  Still waiting for an iPhone with physical QWERTY to rival RIMM&#8217;s functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249447</link>
		<dc:creator><![CDATA[Chris]]></dc:creator>
		<pubDate>Wed, 12 May 2010 18:14:20 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249447</guid>
		<description><![CDATA[&lt;p&gt;Luckily, there&#039;s a group of computer programmers who have successfully ported the Android 2.1 OS over to the HTC Hero (Sprint), which is what I&#039;ve got. Before I was aware of this venture, I begrudgingly sputtered along on 1.5...&lt;/p&gt;

&lt;p&gt;About 2 months ago when I learned of the successful port, I happily &quot;took the plunge&quot; and flashed my phone to 2.1. I haven&#039;t looked back since. My HTC Hero is now running 2.1 and is fully functional. The difference in performance was unbelievable.. and as far as I&#039;ve seen so far, apps written for earlier OS versions are completely compatible with 2.1.&lt;/p&gt;

&lt;p&gt;Bye-bye fragmentation...&lt;/p&gt;

&lt;p&gt;P.S. - If any of you folks are in the same boat I was.. waiting impatiently for your OS upgrade on your Sprint HTC Hero, then go google &quot;Fresh Kitchen Android&quot;. Do a bit of reading on their site, and update your phone. You won&#039;t be disappointed.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Luckily, there&#8217;s a group of computer programmers who have successfully ported the Android 2.1 OS over to the HTC Hero (Sprint), which is what I&#8217;ve got. Before I was aware of this venture, I begrudgingly sputtered along on 1.5&#8230;</p>
<p>About 2 months ago when I learned of the successful port, I happily &#8220;took the plunge&#8221; and flashed my phone to 2.1. I haven&#8217;t looked back since. My HTC Hero is now running 2.1 and is fully functional. The difference in performance was unbelievable.. and as far as I&#8217;ve seen so far, apps written for earlier OS versions are completely compatible with 2.1.</p>
<p>Bye-bye fragmentation&#8230;</p>
<p>P.S. &#8211; If any of you folks are in the same boat I was.. waiting impatiently for your OS upgrade on your Sprint HTC Hero, then go google &#8220;Fresh Kitchen Android&#8221;. Do a bit of reading on their site, and update your phone. You won&#8217;t be disappointed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dpeeps</title>
		<link>http://gigaom.com/2010/04/27/googles-android-fragmentation-problem-persists-admob/#comment-249446</link>
		<dc:creator><![CDATA[dpeeps]]></dc:creator>
		<pubDate>Wed, 12 May 2010 17:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=116202#comment-249446</guid>
		<description><![CDATA[&lt;p&gt;where this really comes into play is with hardware. not now, because we&#039;re only talking from 1.5 to 2.1. But at some point, this becomes the same exact issue microsoft faced. Their OS was on so much different hardware that they had to consider that when doing any development of the OS. At some point Google just has to say, 1.5 isn&#039;t valid, you can&#039;t use it, sell it on new devices, things like that. because the fact of the matter is, 2.1 is very real now, they&#039;re doing work on the next version, and there are devices not slated till the end of this year that plan on being released with 1.5. so either android os becomes just so huge to support so many different hardware configurations/devices, or they find some way, in working with the carriers, who should stay out of the software business anyways, to just provide those core OS updates through google. most average consumers though have a hard time figuring out that they&#039;re really just holding a very tiny computer in their hands, but as things change, and smartphones continue to grow, and people start to have smaller devices than a laptop, that will change.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>where this really comes into play is with hardware. not now, because we&#8217;re only talking from 1.5 to 2.1. But at some point, this becomes the same exact issue microsoft faced. Their OS was on so much different hardware that they had to consider that when doing any development of the OS. At some point Google just has to say, 1.5 isn&#8217;t valid, you can&#8217;t use it, sell it on new devices, things like that. because the fact of the matter is, 2.1 is very real now, they&#8217;re doing work on the next version, and there are devices not slated till the end of this year that plan on being released with 1.5. so either android os becomes just so huge to support so many different hardware configurations/devices, or they find some way, in working with the carriers, who should stay out of the software business anyways, to just provide those core OS updates through google. most average consumers though have a hard time figuring out that they&#8217;re really just holding a very tiny computer in their hands, but as things change, and smartphones continue to grow, and people start to have smaller devices than a laptop, that will change.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
