<?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 Android Too Open or Not Open Enough?</title>
	<atom:link href="http://www.loconet.ca/2009/12/22/is-android-too-open-or-not-open-enough/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.loconet.ca/2009/12/22/is-android-too-open-or-not-open-enough/</link>
	<description>Constantly learning</description>
	<lastBuildDate>Mon, 05 Jul 2010 15:45:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mjschmidt</title>
		<link>http://www.loconet.ca/2009/12/22/is-android-too-open-or-not-open-enough/comment-page-1/#comment-334</link>
		<dc:creator>mjschmidt</dc:creator>
		<pubDate>Tue, 22 Dec 2009 14:16:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.loconet.ca/?p=155#comment-334</guid>
		<description>Great article! You have done a great job of summing this up, and have made some concise points about the problem. Given the experience many of us have had with Rogers&#039; tech support and management over the past month, I must conclude that Rogers didn&#039;t do enough research and preparation before taking on Android. Quite simply; they don&#039;t understand Android.

They boast about the training their CSRs, techs, and sales staff receive, but the truth is, they mistake updates and bug fixes, they seemed not be aware of the availability of OS upgrades from HTC, and in some cases upper management wasn&#039;t even sure whom among them was responsible for Android within Rogers!

In hindsight, they should have created a small working group dedicated to becoming internal experts on Android; a group that could be called on by any manager to explain what it is and how it works, and to properly train other staff.</description>
		<content:encoded><![CDATA[<p>Great article! You have done a great job of summing this up, and have made some concise points about the problem. Given the experience many of us have had with Rogers&#8217; tech support and management over the past month, I must conclude that Rogers didn&#8217;t do enough research and preparation before taking on Android. Quite simply; they don&#8217;t understand Android.</p>
<p>They boast about the training their CSRs, techs, and sales staff receive, but the truth is, they mistake updates and bug fixes, they seemed not be aware of the availability of OS upgrades from HTC, and in some cases upper management wasn&#8217;t even sure whom among them was responsible for Android within Rogers!</p>
<p>In hindsight, they should have created a small working group dedicated to becoming internal experts on Android; a group that could be called on by any manager to explain what it is and how it works, and to properly train other staff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Puleen Patel</title>
		<link>http://www.loconet.ca/2009/12/22/is-android-too-open-or-not-open-enough/comment-page-1/#comment-333</link>
		<dc:creator>Puleen Patel</dc:creator>
		<pubDate>Tue, 22 Dec 2009 10:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.loconet.ca/?p=155#comment-333</guid>
		<description>Excellent write-up, I think you summed up the entire situation and quite possibly a workable solution in here. The hope is that Rogers, HTC and possibly Google are listening!

I should make it clear though that when you say, &quot;Wouldn’t all parties want to make sure that the eco-system remains strong and growing to benefit from it economically in the long-term? I’m not sure some organizations see it that way.&quot;, and applying this to Rogers would not make sense. Historically, by analyzing various patterns of the decisions Rogers makes they are almost always made towards a short-term, tactical goal. They proclaim bringing &quot;Revolution&quot; to Canada, for what seemed to be so at the time in order to: 1) Boast of being the first to bring Android to Canada and 2) Capture/Increase market share (marginal increase) of users like you and I into a continual source of revenue stream.

While this is great, looking back at it now and connecting the dot, it is abundantly clear that the move was purely tactical with no strategic path of 1) Continuing he Revolution, or 2) Continuing to evolve in the Android eco system.

When corporate greed takes over, doing the right thing seems wasteful of resources and provides little in terms tangible value add. In my personal opinion, this seems to be the case repeatedly with Rogers. I am sure many other loyal yet dissatisfied customers would agree.</description>
		<content:encoded><![CDATA[<p>Excellent write-up, I think you summed up the entire situation and quite possibly a workable solution in here. The hope is that Rogers, HTC and possibly Google are listening!</p>
<p>I should make it clear though that when you say, &#8220;Wouldn’t all parties want to make sure that the eco-system remains strong and growing to benefit from it economically in the long-term? I’m not sure some organizations see it that way.&#8221;, and applying this to Rogers would not make sense. Historically, by analyzing various patterns of the decisions Rogers makes they are almost always made towards a short-term, tactical goal. They proclaim bringing &#8220;Revolution&#8221; to Canada, for what seemed to be so at the time in order to: 1) Boast of being the first to bring Android to Canada and 2) Capture/Increase market share (marginal increase) of users like you and I into a continual source of revenue stream.</p>
<p>While this is great, looking back at it now and connecting the dot, it is abundantly clear that the move was purely tactical with no strategic path of 1) Continuing he Revolution, or 2) Continuing to evolve in the Android eco system.</p>
<p>When corporate greed takes over, doing the right thing seems wasteful of resources and provides little in terms tangible value add. In my personal opinion, this seems to be the case repeatedly with Rogers. I am sure many other loyal yet dissatisfied customers would agree.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
