<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: The darker side of Android</title>
	<atom:link href="http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/</link>
	<description>Distilling market noise into market sense.</description>
	<lastBuildDate>Tue, 09 Mar 2010 09:11:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andreas Constantinou</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60648</link>
		<dc:creator>Andreas Constantinou</dc:creator>
		<pubDate>Thu, 09 Oct 2008 22:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60648</guid>
		<description>Ajit - I hope to do a comparison on Download! vs Android Market vs AppStore vs BREW Shop in the near future. I &#039;ll hold my judgement till then :)

Andreas</description>
		<content:encoded><![CDATA[<p>Ajit &#8211; I hope to do a comparison on Download! vs Android Market vs AppStore vs BREW Shop in the near future. I &#8216;ll hold my judgement till then <img src='http://www.visionmobile.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajit Jaokar</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60643</link>
		<dc:creator>Ajit Jaokar</dc:creator>
		<pubDate>Thu, 09 Oct 2008 17:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60643</guid>
		<description>thanks. I also did something similar a while ago. Agree complex topic. But what about the free bit? I think mobile apps are tending to free .. 

see 
LBS for £1.79? Vicinity app on the iPhone. What does it say for the Context - location based services business/ revenue model?
http://opengardensblog.futuretext.com/archives/2008/10/lbs_for_179_vic.html

If things start to get free(even LBS type apps) - then it needs a fundamantal rethink .. and I dont have any answers - just the observation that the evidence on Android and iPhone both leans to free mobile apps .. 

Having said that, even if an app is £2 and there are 100,000 downloads, it is still a good model for the developer ** assuming ** they get to keep 70%. Thats the really worrying thing re Android - revenue share i.e. if we are talking of free then many of the consideratuons(like fragmentation, support etc) don matter that much! thoughts? kind rgds Ajit</description>
		<content:encoded><![CDATA[<p>thanks. I also did something similar a while ago. Agree complex topic. But what about the free bit? I think mobile apps are tending to free .. </p>
<p>see<br />
LBS for £1.79? Vicinity app on the iPhone. What does it say for the Context &#8211; location based services business/ revenue model?<br />
<a href="http://opengardensblog.futuretext.com/archives/2008/10/lbs_for_179_vic.html" rel="nofollow">http://opengardensblog.futuretext.com/archives/2008/10/lbs_for_179_vic.html</a></p>
<p>If things start to get free(even LBS type apps) &#8211; then it needs a fundamantal rethink .. and I dont have any answers &#8211; just the observation that the evidence on Android and iPhone both leans to free mobile apps .. </p>
<p>Having said that, even if an app is £2 and there are 100,000 downloads, it is still a good model for the developer ** assuming ** they get to keep 70%. Thats the really worrying thing re Android &#8211; revenue share i.e. if we are talking of free then many of the consideratuons(like fragmentation, support etc) don matter that much! thoughts? kind rgds Ajit</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Constantinou</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60642</link>
		<dc:creator>Andreas Constantinou</dc:creator>
		<pubDate>Thu, 09 Oct 2008 17:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60642</guid>
		<description>Thanks Ajit - openness is indeed a very complex issue. Here&#039;s how I break it down:
1. Openness for developers
a. API-level openness for developing downloadable AND core applications
b. tools openness: cost of tools, both in terms of one of cost, but also development costs, testing efffort needed
c.route-to-market openness, i.e. access to a centrallised channel for certification, distribution, provisioning, and billing
d. post-sales channel openness, i.e. having an open channel to the user using your app

2. Openness for handset OEMs
a. access to read AND modify source code (this has lots of parameters - see West and O&#039;Mahony, 2008)
b. access to hardware boards, for quickly bringing up new devices

3. Openness for network operators
a. ability to request customisation changes, without impacting time-to-market or cost (both are usually impacted, but because OEMs in purpose introduce lengthier TTMs as a negotiation strategy)

Probably 1-2  more aspects which escaped the braindump.. I think this justifies a new post :)

Andreas</description>
		<content:encoded><![CDATA[<p>Thanks Ajit &#8211; openness is indeed a very complex issue. Here&#8217;s how I break it down:<br />
1. Openness for developers<br />
a. API-level openness for developing downloadable AND core applications<br />
b. tools openness: cost of tools, both in terms of one of cost, but also development costs, testing efffort needed<br />
c.route-to-market openness, i.e. access to a centrallised channel for certification, distribution, provisioning, and billing<br />
d. post-sales channel openness, i.e. having an open channel to the user using your app</p>
<p>2. Openness for handset OEMs<br />
a. access to read AND modify source code (this has lots of parameters &#8211; see West and O&#8217;Mahony, 2008)<br />
b. access to hardware boards, for quickly bringing up new devices</p>
<p>3. Openness for network operators<br />
a. ability to request customisation changes, without impacting time-to-market or cost (both are usually impacted, but because OEMs in purpose introduce lengthier TTMs as a negotiation strategy)</p>
<p>Probably 1-2  more aspects which escaped the braindump.. I think this justifies a new post <img src='http://www.visionmobile.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajit Jaokar</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60641</link>
		<dc:creator>Ajit Jaokar</dc:creator>
		<pubDate>Thu, 09 Oct 2008 17:00:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60641</guid>
		<description>very interesting article Andreas! Been travelling so I missed it. Agree with all you say - and also that its been a bit disappointing so far with Android. We have been covering this topic in our respective blogs .. and we know ofcourse that &#039;an open source operating system doesn’t mean an open phone&#039; is true. But the converse question is more interesting as well: What constitutes an Open phone? I had a long article I am working with(Openness in general and also relating to phone) - and have been thinking of this for a while. Seek your thoughts. If you take a purist stance, then openmoko is potentially a candidate(since it includes HW and SW combined). And leads to a even more broader question - would an open phone be commercially accepted/useful? The problem of fragmentation can be solved by uniting around a certain paradigm (and that need not be a phone). More interetingly - it appears to me that Google is going for a pricepoint of free(ie ad funded) apps

see
Android - iPhone revenue models: Can 70 plus 30 equal free? - Is the future of mobile apps free or fee based?
http://opengardensblog.futuretext.com/archives/2008/09/android_-_iphon.html

So, if you look at the whole pic, then the approach seems to be to provide a Good enough/free app - so no customer support hassles etc. 

In that context, it is disappointing since developers wont get anything if it is free .. but Google still gets ad revenue(and I refer to one of your excelent older posts - every element of the Android stack becomes a Web 2.0 element - or something like that ..) i..e we get targetted advertising like Gmail with metadata derieved from every element of the stack ..

A long comment! and late in the night at Hong Kong and gotta go early morning to China .. but hope you find it useful inspite of ite rambling nature! kind rgds Ajit</description>
		<content:encoded><![CDATA[<p>very interesting article Andreas! Been travelling so I missed it. Agree with all you say &#8211; and also that its been a bit disappointing so far with Android. We have been covering this topic in our respective blogs .. and we know ofcourse that &#8216;an open source operating system doesn’t mean an open phone&#8217; is true. But the converse question is more interesting as well: What constitutes an Open phone? I had a long article I am working with(Openness in general and also relating to phone) &#8211; and have been thinking of this for a while. Seek your thoughts. If you take a purist stance, then openmoko is potentially a candidate(since it includes HW and SW combined). And leads to a even more broader question &#8211; would an open phone be commercially accepted/useful? The problem of fragmentation can be solved by uniting around a certain paradigm (and that need not be a phone). More interetingly &#8211; it appears to me that Google is going for a pricepoint of free(ie ad funded) apps</p>
<p>see<br />
Android &#8211; iPhone revenue models: Can 70 plus 30 equal free? &#8211; Is the future of mobile apps free or fee based?<br />
<a href="http://opengardensblog.futuretext.com/archives/2008/09/android_-_iphon.html" rel="nofollow">http://opengardensblog.futuretext.com/archives/2008/09/android_-_iphon.html</a></p>
<p>So, if you look at the whole pic, then the approach seems to be to provide a Good enough/free app &#8211; so no customer support hassles etc. </p>
<p>In that context, it is disappointing since developers wont get anything if it is free .. but Google still gets ad revenue(and I refer to one of your excelent older posts &#8211; every element of the Android stack becomes a Web 2.0 element &#8211; or something like that ..) i..e we get targetted advertising like Gmail with metadata derieved from every element of the stack ..</p>
<p>A long comment! and late in the night at Hong Kong and gotta go early morning to China .. but hope you find it useful inspite of ite rambling nature! kind rgds Ajit</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Wood</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60348</link>
		<dc:creator>David Wood</dc:creator>
		<pubDate>Tue, 30 Sep 2008 14:09:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60348</guid>
		<description>For another article on a roughly similar theme, see &quot;Google’s Android Market Guarantees Problems for Users&quot; at http://www.roughlydrafted.com/2008/08/29/googles-android-market-guarantees-problems-for-users/</description>
		<content:encoded><![CDATA[<p>For another article on a roughly similar theme, see &#8220;Google’s Android Market Guarantees Problems for Users&#8221; at <a href="http://www.roughlydrafted.com/2008/08/29/googles-android-market-guarantees-problems-for-users/" rel="nofollow">http://www.roughlydrafted.com/2008/08/29/googles-android-market-guarantees-problems-for-users/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Constantinou</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60317</link>
		<dc:creator>Andreas Constantinou</dc:creator>
		<pubDate>Mon, 29 Sep 2008 20:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60317</guid>
		<description>Surya,

Good questions. 

Fragmentation by design: I meant two things by this:
a) My guess is that Google is counting on diversity (as in biodiversity) for the survival of the fittest stack.
b) simply that Google knows that people can create binary incompatible Androids from the &#039;master&#039; APL2 stack, therefore it&#039;s &#039;designed&#039; for fragmentation.

Dalvik: we won&#039;t know for sure whether Dalvik code will be covered under APL2 until the v1.0 is released in source code form. Mike Jennings did say that Dalvik would be also licensed under APL2, but I &#039;m not holding my breath. Dalvik holds the key to binary runtime compatibility.

David, 

thanks for the tip on IE6. We &#039;ve had compatibility issues with IE6 before, and we &#039;ll fix the comments snag asap.

Andreas</description>
		<content:encoded><![CDATA[<p>Surya,</p>
<p>Good questions. </p>
<p>Fragmentation by design: I meant two things by this:<br />
a) My guess is that Google is counting on diversity (as in biodiversity) for the survival of the fittest stack.<br />
b) simply that Google knows that people can create binary incompatible Androids from the &#8216;master&#8217; APL2 stack, therefore it&#8217;s &#8216;designed&#8217; for fragmentation.</p>
<p>Dalvik: we won&#8217;t know for sure whether Dalvik code will be covered under APL2 until the v1.0 is released in source code form. Mike Jennings did say that Dalvik would be also licensed under APL2, but I &#8216;m not holding my breath. Dalvik holds the key to binary runtime compatibility.</p>
<p>David, </p>
<p>thanks for the tip on IE6. We &#8216;ve had compatibility issues with IE6 before, and we &#8216;ll fix the comments snag asap.</p>
<p>Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Wood</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60307</link>
		<dc:creator>David Wood</dc:creator>
		<pubDate>Mon, 29 Sep 2008 14:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60307</guid>
		<description>Hi Andreas - Am I the only person whose PC browser (IE6 running on Win XP) resolutely fails to display more than the first 3 lines of each response to articles in this blog? // dw2-0

PS Opera Mini on my Nokia E61i makes a *much* better job of displaying the comments!</description>
		<content:encoded><![CDATA[<p>Hi Andreas &#8211; Am I the only person whose PC browser (IE6 running on Win XP) resolutely fails to display more than the first 3 lines of each response to articles in this blog? // dw2-0</p>
<p>PS Opera Mini on my Nokia E61i makes a *much* better job of displaying the comments!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Surya</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60268</link>
		<dc:creator>Surya</dc:creator>
		<pubDate>Sun, 28 Sep 2008 19:48:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60268</guid>
		<description>Hi Andreas,

Great article once again. Just had a question on the point about &quot;fragmentation by design&quot;. 

When you say &quot;by design&quot;, do you mean Google has intentionally set things up so that fragmentation happens? How would Google benefit from this?

On the other hand, if Google is not hoping for fragmentation, why are they sticking with the Apache license? Why can&#039;t they modify the license such that Dalvik cannot be modified without feeding back into the main code stream?

Please excuse me if my questions are ignorant..

Regards.</description>
		<content:encoded><![CDATA[<p>Hi Andreas,</p>
<p>Great article once again. Just had a question on the point about &#8220;fragmentation by design&#8221;. </p>
<p>When you say &#8220;by design&#8221;, do you mean Google has intentionally set things up so that fragmentation happens? How would Google benefit from this?</p>
<p>On the other hand, if Google is not hoping for fragmentation, why are they sticking with the Apache license? Why can&#8217;t they modify the license such that Dalvik cannot be modified without feeding back into the main code stream?</p>
<p>Please excuse me if my questions are ignorant..</p>
<p>Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rekzkarz</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60191</link>
		<dc:creator>rekzkarz</dc:creator>
		<pubDate>Fri, 26 Sep 2008 22:57:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60191</guid>
		<description>Hi Stefan &amp; Andreas &amp; Raddedas &amp; Fred,

I like the title of the article, although frankly, I think the dark side is much darker than that, like Google doing a lot of tracking &amp; pulling data/stats and more -- and helping world govts do the same (but don&#039;t all phone co&#039;s do that now anyway???).

While early adopters/buyers will likely be stuck with a closed phone (to some extent) for awhile, the beauty of the &#039;net is that most phones get cracked wide open by the world community of disgruntled engineers (aka hackers), and bitTorrent is still around so people can share in the wealth.

While Google is making an open source phone OS with a foolish attempt to keep the marketplace in it&#039;s control, I hope that the &#039;real free market&#039; -- hackers (ie freedom fighters), pirates (aka copiers), and bittorrent (aka &#039;freedom of speech&#039; as software) -- will eventually re-open things in time.

Some of you may notice I re-interpreted all those names (hackers, pirates, etc).  I think we must reclaim our language from the double-think of corp-biased media.  The real pirates of 2008 are the corporate CEOs, the political spin artists, the media moguls cutting off freedom of the press, the freelance mercenaries working for the CIA, the drug cartels, the mafia, etc -- and it seems like most of those are the SAME people!

WAKEUP and smell the coffee (which is often produced with child labor and slave labor wages in poor countries).

rekzkarz.com
aka Ari</description>
		<content:encoded><![CDATA[<p>Hi Stefan &amp; Andreas &amp; Raddedas &amp; Fred,</p>
<p>I like the title of the article, although frankly, I think the dark side is much darker than that, like Google doing a lot of tracking &amp; pulling data/stats and more &#8212; and helping world govts do the same (but don&#8217;t all phone co&#8217;s do that now anyway???).</p>
<p>While early adopters/buyers will likely be stuck with a closed phone (to some extent) for awhile, the beauty of the &#8216;net is that most phones get cracked wide open by the world community of disgruntled engineers (aka hackers), and bitTorrent is still around so people can share in the wealth.</p>
<p>While Google is making an open source phone OS with a foolish attempt to keep the marketplace in it&#8217;s control, I hope that the &#8216;real free market&#8217; &#8212; hackers (ie freedom fighters), pirates (aka copiers), and bittorrent (aka &#8216;freedom of speech&#8217; as software) &#8212; will eventually re-open things in time.</p>
<p>Some of you may notice I re-interpreted all those names (hackers, pirates, etc).  I think we must reclaim our language from the double-think of corp-biased media.  The real pirates of 2008 are the corporate CEOs, the political spin artists, the media moguls cutting off freedom of the press, the freelance mercenaries working for the CIA, the drug cartels, the mafia, etc &#8212; and it seems like most of those are the SAME people!</p>
<p>WAKEUP and smell the coffee (which is often produced with child labor and slave labor wages in poor countries).</p>
<p>rekzkarz.com<br />
aka Ari</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Hookway</title>
		<link>http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/comment-page-1/#comment-60121</link>
		<dc:creator>Ben Hookway</dc:creator>
		<pubDate>Thu, 25 Sep 2008 20:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/2008/09/the-darker-side-of-android/#comment-60121</guid>
		<description>Hi Andreas, Nice article. Do you have any insight into the hardware that is going to be needed to run a reasonable Android implementation? I hear the T-Mobile device is running a Qualcomm chip with a 526MHz processor - heavyweight stuff.</description>
		<content:encoded><![CDATA[<p>Hi Andreas, Nice article. Do you have any insight into the hardware that is going to be needed to run a reasonable Android implementation? I hear the T-Mobile device is running a Qualcomm chip with a 526MHz processor &#8211; heavyweight stuff.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
