<?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: The shift of the cellphone market from devices to platforms and services: If it were possible to port Fortran on mobile phones .. Motorola would so ..</title>
	<atom:link href="http://www.opengardensblog.futuretext.com/archives/2009/02/the_shift_of_th.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.opengardensblog.futuretext.com/archives/2009/02/the_shift_of_th.html</link>
	<description>Wireless mobility - Innovation - Digital convergence - mobile web 2.0</description>
	<lastBuildDate>Thu, 19 Jan 2012 13:47:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Paul Golding</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2009/02/the_shift_of_th.html/comment-page-1#comment-1724</link>
		<dc:creator>Paul Golding</dc:creator>
		<pubDate>Sun, 08 Feb 2009 12:42:55 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2009/02/the_shift_of_th.html#comment-1724</guid>
		<description>Hi Ajit - good post.
Sometimes it is just down to problems of execution, not ‘getting it.’ There are/were plenty of people in Moto who understand everything you say above and who could create compelling products. Moto is crammed full of clever people. For example, Moto already has in production (and in some current devices) native device APIs in their browser - &lt;a href=&quot;http://developer.motorola.com/technologies/webui/&quot; rel=&quot;nofollow&quot;&gt;http://developer.motorola.com/technologies/webui/&lt;/a&gt;
Motorola&#039;s vision was for a long time dominated by the chimera of &#039;Seamless Mobility&#039; which tried to harmonise their strategy across a broad portfolio of products from IPTV to radios. In the end, they couldn&#039;t do it and became too reliant upon the strength of their badge to sell equipment. I sat in a strategy meeting about how to sell IMS and the final proposition was - &#039;it&#039;s got our logo on it.&#039;
The company got bogged down by insisting that all projects serviced the &#039;Seamless Mobility&#039; mantra of the previous leadership rather than creating compelling products that people actually wanted. Unfortunately, Seamless Mobility was nothing more than a clever phrase, which poor leadership hid behind for too long.
</description>
		<content:encoded><![CDATA[<p>Hi Ajit &#8211; good post.<br />
Sometimes it is just down to problems of execution, not ‘getting it.’ There are/were plenty of people in Moto who understand everything you say above and who could create compelling products. Moto is crammed full of clever people. For example, Moto already has in production (and in some current devices) native device APIs in their browser &#8211; <a href="http://developer.motorola.com/technologies/webui/" rel="nofollow">http://developer.motorola.com/technologies/webui/</a><br />
Motorola&#8217;s vision was for a long time dominated by the chimera of &#8216;Seamless Mobility&#8217; which tried to harmonise their strategy across a broad portfolio of products from IPTV to radios. In the end, they couldn&#8217;t do it and became too reliant upon the strength of their badge to sell equipment. I sat in a strategy meeting about how to sell IMS and the final proposition was &#8211; &#8216;it&#8217;s got our logo on it.&#8217;<br />
The company got bogged down by insisting that all projects serviced the &#8216;Seamless Mobility&#8217; mantra of the previous leadership rather than creating compelling products that people actually wanted. Unfortunately, Seamless Mobility was nothing more than a clever phrase, which poor leadership hid behind for too long.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
