<?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: Android&#8217;s Growth Rate and How It Actually Hurts The App Market</title>
	<atom:link href="http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/</link>
	<description>App Discovery, Mobile Content, Trends in Tech</description>
	<lastBuildDate>Sat, 11 Feb 2012 05:39:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ted</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-26970</link>
		<dc:creator>Ted</dc:creator>
		<pubDate>Sat, 16 Apr 2011 17:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-26970</guid>
		<description>I think all the Android devs here are barking up the wrong tree as to attempting to explain away the fragmentation issues inherent in Android. You can build a non-hardware-specific app that will work on all devices but that&#039;s extremely limiting. If that&#039;s what your app is supposed to do then sure but why should I suffer a penalty in reaching an audience for developing a robust app that takes advantage of hardware necessary for the app&#039;s purpose?

Most people have the fragmentation issue confused. For one, iOS 4.3 not being compatible with a handset manufactured in 2008 is not an example of fragmentation - that&#039;s a red herring used primarily by Android fanatics to explain away the fragmentation issue. Additionally, jailbroken devices are not officially supported so that&#039;s hardly Apple&#039;s fault or concern and they do not market the platform as open so that&#039;s different than the standard set by Google by allowing all sorts of custom ROMs and builds. There are brand new Android handsets being shipped with outdated OS versions, on a variety of different devices with random quality and materials with differing specs, and different types of skins and different UI/UX. More importantly, those handsets lack an upgrade path until the carriers and/or OEMs get around to it. That&#039;s fragmentation.

As a specific example, a dev here said that a phone will adapt the app to its resolution, essentially stretching or squashing the app interface to fit. Or better yet (as I saw myself on an EVO), black bars hug the UI like a widescreen movie when there is more physical space than the app can handle. This is just a crappy user experience no matter how you slice it. The dev can create higher res versions but that&#039;s the rub -- they have to do it for very screen size if they want it to be universal.

On the flip side, unlike the author, I believe Apple will increase the physical screen size of the iPhone in future iterations so that will need to be dealt with on the iOS side as well. However, given the explanation of fragmentation in my previous paragraph, it is decidedly not the same thing and nowhere near the same effect or extreme multitude of simultaneous versions like on the Android side. 

Lastly, I want to say that Thorren is absolutely right about user usage and expectations. I would go one further and say that a very large majority are the simple type of user. Given this, is the open flexibility and comparatively dizzying amount of choice really right for such a user? They would hardly care for it if they never really knew. A consistent experience is best for this type (or any type that values getting a task done versus fussing and administering their device).</description>
		<content:encoded><![CDATA[<p>I think all the Android devs here are barking up the wrong tree as to attempting to explain away the fragmentation issues inherent in Android. You can build a non-hardware-specific app that will work on all devices but that&#8217;s extremely limiting. If that&#8217;s what your app is supposed to do then sure but why should I suffer a penalty in reaching an audience for developing a robust app that takes advantage of hardware necessary for the app&#8217;s purpose?</p>
<p>Most people have the fragmentation issue confused. For one, iOS 4.3 not being compatible with a handset manufactured in 2008 is not an example of fragmentation &#8211; that&#8217;s a red herring used primarily by Android fanatics to explain away the fragmentation issue. Additionally, jailbroken devices are not officially supported so that&#8217;s hardly Apple&#8217;s fault or concern and they do not market the platform as open so that&#8217;s different than the standard set by Google by allowing all sorts of custom ROMs and builds. There are brand new Android handsets being shipped with outdated OS versions, on a variety of different devices with random quality and materials with differing specs, and different types of skins and different UI/UX. More importantly, those handsets lack an upgrade path until the carriers and/or OEMs get around to it. That&#8217;s fragmentation.</p>
<p>As a specific example, a dev here said that a phone will adapt the app to its resolution, essentially stretching or squashing the app interface to fit. Or better yet (as I saw myself on an EVO), black bars hug the UI like a widescreen movie when there is more physical space than the app can handle. This is just a crappy user experience no matter how you slice it. The dev can create higher res versions but that&#8217;s the rub &#8212; they have to do it for very screen size if they want it to be universal.</p>
<p>On the flip side, unlike the author, I believe Apple will increase the physical screen size of the iPhone in future iterations so that will need to be dealt with on the iOS side as well. However, given the explanation of fragmentation in my previous paragraph, it is decidedly not the same thing and nowhere near the same effect or extreme multitude of simultaneous versions like on the Android side. </p>
<p>Lastly, I want to say that Thorren is absolutely right about user usage and expectations. I would go one further and say that a very large majority are the simple type of user. Given this, is the open flexibility and comparatively dizzying amount of choice really right for such a user? They would hardly care for it if they never really knew. A consistent experience is best for this type (or any type that values getting a task done versus fussing and administering their device).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ahhchuu</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-22303</link>
		<dc:creator>ahhchuu</dc:creator>
		<pubDate>Tue, 08 Mar 2011 01:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-22303</guid>
		<description>Am I the only one here wondering why people keep saying open source == free? Because, that is not true...

Also, cheers to Thorren. :) You are a very level headed person. And that is coming from an Android users/developer. ;) Keep on enjoying your iPhone.</description>
		<content:encoded><![CDATA[<p>Am I the only one here wondering why people keep saying open source == free? Because, that is not true&#8230;</p>
<p>Also, cheers to Thorren. <img src='http://blog.appboy.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  You are a very level headed person. And that is coming from an Android users/developer. <img src='http://blog.appboy.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  Keep on enjoying your iPhone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Android Fragmentation in Cold Hard Numbers</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-17856</link>
		<dc:creator>Android Fragmentation in Cold Hard Numbers</dc:creator>
		<pubDate>Tue, 18 Jan 2011 08:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-17856</guid>
		<description>[...] Reasons Android Just Surpassed iPhone in SalesThree iPhone 4 DisappointmentsAndroid&#039;s Growth Rate and How It Actually Hurts The App Market5 Reasons the Samsung Galaxy Tab Will Struggle to Compete with the iPadFive Fundamental Flaws of The [...]</description>
		<content:encoded><![CDATA[<p>[...] Reasons Android Just Surpassed iPhone in SalesThree iPhone 4 DisappointmentsAndroid&#039;s Growth Rate and How It Actually Hurts The App Market5 Reasons the Samsung Galaxy Tab Will Struggle to Compete with the iPadFive Fundamental Flaws of The [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Windows Phone 7: The Good, The Bad, and&#8230; You Decide!&#160;&#124;&#160;Mobile &#124; Social Media &#124; Newest Technologies by Tech N&#039; Marketing</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-8795</link>
		<dc:creator>Windows Phone 7: The Good, The Bad, and&#8230; You Decide!&#160;&#124;&#160;Mobile &#124; Social Media &#124; Newest Technologies by Tech N&#039; Marketing</dc:creator>
		<pubDate>Fri, 23 Jul 2010 14:02:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-8795</guid>
		<description>[...] the experience. Now, if you have read my writing, chances are you have come across my thoughts on Android fragmentation, but he was talking like Android is a failure of a platform. He did not even address the Android [...]</description>
		<content:encoded><![CDATA[<p>[...] the experience. Now, if you have read my writing, chances are you have come across my thoughts on Android fragmentation, but he was talking like Android is a failure of a platform. He did not even address the Android [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Page not found</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-8297</link>
		<dc:creator>Page not found</dc:creator>
		<pubDate>Tue, 06 Jul 2010 07:00:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-8297</guid>
		<description>[...] Reasons Android Just Surpassed iPhone in SalesThree iPhone 4 DisappointmentsAndroid&#039;s Growth Rate and How It Actually Hurts The App MarketFive Fundamental Flaws of The iPad5 Features that Would Have Truly Made the iPad A &quot;Magical&quot; Device6 [...]</description>
		<content:encoded><![CDATA[<p>[...] Reasons Android Just Surpassed iPhone in SalesThree iPhone 4 DisappointmentsAndroid&#039;s Growth Rate and How It Actually Hurts The App MarketFive Fundamental Flaws of The iPad5 Features that Would Have Truly Made the iPad A &quot;Magical&quot; Device6 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iPhone4-Apps sind iPad-kompatibel und umgekehrt</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-7806</link>
		<dc:creator>iPhone4-Apps sind iPad-kompatibel und umgekehrt</dc:creator>
		<pubDate>Tue, 15 Jun 2010 14:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-7806</guid>
		<description>[...] Die Android-Plattform, die auf vielen verschiedenen Modellen mit unterschiedlichen Ausstattungen und Display-Gr&#246;&#223;en vertreten ist und zus&#228;tzlich noch mit unterschiedlichen OS-Versionen auf den Ger&#228;ten zu k&#228;mpfen hat, wird stark von Fragmentierung bestimmt. Das ist ein Problem f&#252;r das App-&#214;kosystem: [...]</description>
		<content:encoded><![CDATA[<p>[...] Die Android-Plattform, die auf vielen verschiedenen Modellen mit unterschiedlichen Ausstattungen und Display-Gr&#246;&#223;en vertreten ist und zus&#228;tzlich noch mit unterschiedlichen OS-Versionen auf den Ger&#228;ten zu k&#228;mpfen hat, wird stark von Fragmentierung bestimmt. Das ist ein Problem f&#252;r das App-&#214;kosystem: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ben</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-7789</link>
		<dc:creator>ben</dc:creator>
		<pubDate>Mon, 14 Jun 2010 09:56:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-7789</guid>
		<description>As an Android developer i must say that there is no issues if you don&#039;t plan to use any device specific feature ...

I&#039;m only concern about the upgrade rate, which depends on telcos</description>
		<content:encoded><![CDATA[<p>As an Android developer i must say that there is no issues if you don&#8217;t plan to use any device specific feature &#8230;</p>
<p>I&#8217;m only concern about the upgrade rate, which depends on telcos</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hillel Fuld</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-7762</link>
		<dc:creator>Hillel Fuld</dc:creator>
		<pubDate>Sun, 13 Jun 2010 03:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-7762</guid>
		<description>Just a quick thank you to all of you for commenting, happy to see the post evoked such emotion and debate...</description>
		<content:encoded><![CDATA[<p>Just a quick thank you to all of you for commenting, happy to see the post evoked such emotion and debate&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DaveMTL</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-7755</link>
		<dc:creator>DaveMTL</dc:creator>
		<pubDate>Sun, 13 Jun 2010 00:00:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-7755</guid>
		<description>As others have mentioned, both OSs are very good. The thing that worries me is that a buddy of mine bought a Sony phone recently and mentioned he had Android 1.6 on it... My reply was &quot;what? aren&#039;t they at 2.1 or 2.2?&quot;. Apparently it has a GUI layer custom to that phone. Sony will eventually upgrade to 2.2. Am I the only one who sees danger in that? That is what I hated of the past. It appears telcos may be starting to &quot;customize&quot; as well (see Rogers Social thing). Same phone but &quot;customized&quot; for a given telco. Hardware aside, the OS should be uniform and upgradeable. Just a thought.</description>
		<content:encoded><![CDATA[<p>As others have mentioned, both OSs are very good. The thing that worries me is that a buddy of mine bought a Sony phone recently and mentioned he had Android 1.6 on it&#8230; My reply was &#8220;what? aren&#8217;t they at 2.1 or 2.2?&#8221;. Apparently it has a GUI layer custom to that phone. Sony will eventually upgrade to 2.2. Am I the only one who sees danger in that? That is what I hated of the past. It appears telcos may be starting to &#8220;customize&#8221; as well (see Rogers Social thing). Same phone but &#8220;customized&#8221; for a given telco. Hardware aside, the OS should be uniform and upgradeable. Just a thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdamC</title>
		<link>http://blog.appboy.com/2010/06/androids-growth-rate-and-how-it-actually-hurts-the-app-market/comment-page-1/#comment-7738</link>
		<dc:creator>AdamC</dc:creator>
		<pubDate>Sat, 12 Jun 2010 04:32:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appboy.com/?p=3575#comment-7738</guid>
		<description>The issue I believe is android users expect open apps in other words free apps.

So where do the developers stand financially?

One more thing, good luck to the developers.</description>
		<content:encoded><![CDATA[<p>The issue I believe is android users expect open apps in other words free apps.</p>
<p>So where do the developers stand financially?</p>
<p>One more thing, good luck to the developers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

