<?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: Reflections on Mobile World Congress 2010 – Barcelona</title>
	<atom:link href="http://www.slamobileblog.com/2010/02/23/reflections-on-mobile-world-congress-2010-%e2%80%93-barcelona/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slamobileblog.com/2010/02/23/reflections-on-mobile-world-congress-2010-%e2%80%93-barcelona/</link>
	<description>A blog about the mobile business</description>
	<lastBuildDate>Wed, 01 Jun 2011 07:56:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kevin Smith</title>
		<link>http://www.slamobileblog.com/2010/02/23/reflections-on-mobile-world-congress-2010-%e2%80%93-barcelona/comment-page-1/#comment-55</link>
		<dc:creator>Kevin Smith</dc:creator>
		<pubDate>Wed, 24 Feb 2010 13:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.slamobileblog.com/?p=132#comment-55</guid>
		<description>Hi Toby,

Just to make a clarification - OneAPI was built by technologists in the working groups of the GSMA Access group and the OMA. The requirements for the APIs (i.e. which to concentrate on) came from content publishers and developers on the OneAPI forum and developer barcamps. These helped steer us towards RESTful/JSON APIs that did not require a great deal of knowledge about Telco systems. Based on developer feedback and the pilot in Canada we are teasing out any technical problems and feeding them back into the specification. So it is not a marketing-driven API, however we do ask any implementers to market the fact that they are using it!

Many thanks for your interest and please let us know any feedback.

Best,
Kevin Smith (OneAPI project leader, Vodafone)</description>
		<content:encoded><![CDATA[<p>Hi Toby,</p>
<p>Just to make a clarification &#8211; OneAPI was built by technologists in the working groups of the GSMA Access group and the OMA. The requirements for the APIs (i.e. which to concentrate on) came from content publishers and developers on the OneAPI forum and developer barcamps. These helped steer us towards RESTful/JSON APIs that did not require a great deal of knowledge about Telco systems. Based on developer feedback and the pilot in Canada we are teasing out any technical problems and feeding them back into the specification. So it is not a marketing-driven API, however we do ask any implementers to market the fact that they are using it!</p>
<p>Many thanks for your interest and please let us know any feedback.</p>
<p>Best,<br />
Kevin Smith (OneAPI project leader, Vodafone)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Ardagh-Walter</title>
		<link>http://www.slamobileblog.com/2010/02/23/reflections-on-mobile-world-congress-2010-%e2%80%93-barcelona/comment-page-1/#comment-54</link>
		<dc:creator>Steve Ardagh-Walter</dc:creator>
		<pubDate>Wed, 24 Feb 2010 11:03:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.slamobileblog.com/?p=132#comment-54</guid>
		<description>Yes - this year will be interesting ... and Toby I think you may be right in predicting that operators fail to grow the OneAPI opportunity sufficiently fast.

The risks to OneAPI and development of a &quot;two sided market&quot; include the logic of a limited product development capacity (the urgent vs the important : lots of competing projects with higher short-term returns); the lack of MNO returns from applications business to date; and the necessary change in approach from competition with other MNOs to cooperation

This last point might though play in the MNOs favour : the impulse to differentiate from competitors also drives the handset OEMs, OS vendors and over the top competitors.    There will be no single winner in the mobile OS &#039;war&#039; (so he says, confidently ...), nor will a single OEM or internet consumer brand sweep all before it.  So _if_ MNOs can drive a single layer of standardisation, they will ultimately be in a much stronger place than they seem to be right now.</description>
		<content:encoded><![CDATA[<p>Yes &#8211; this year will be interesting &#8230; and Toby I think you may be right in predicting that operators fail to grow the OneAPI opportunity sufficiently fast.</p>
<p>The risks to OneAPI and development of a &#8220;two sided market&#8221; include the logic of a limited product development capacity (the urgent vs the important : lots of competing projects with higher short-term returns); the lack of MNO returns from applications business to date; and the necessary change in approach from competition with other MNOs to cooperation</p>
<p>This last point might though play in the MNOs favour : the impulse to differentiate from competitors also drives the handset OEMs, OS vendors and over the top competitors.    There will be no single winner in the mobile OS &#8216;war&#8217; (so he says, confidently &#8230;), nor will a single OEM or internet consumer brand sweep all before it.  So _if_ MNOs can drive a single layer of standardisation, they will ultimately be in a much stronger place than they seem to be right now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip</title>
		<link>http://www.slamobileblog.com/2010/02/23/reflections-on-mobile-world-congress-2010-%e2%80%93-barcelona/comment-page-1/#comment-53</link>
		<dc:creator>Philip</dc:creator>
		<pubDate>Tue, 23 Feb 2010 23:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.slamobileblog.com/?p=132#comment-53</guid>
		<description>Hi Toby

Thanks for the debate provoking comments.

I agree re OneAPI .. this should be the Operators killer differentiator making their infrastructure available for developers to use - low cost, fast and easy to work with. Operators need to grasp the opportunity and move at internet speeds. Remember ... most people don&#039;t have fancy smartphones yet so operators have a real opportunity eg using their billing relationship , location data, profiling etc.

2010 will be an interesting year.

Philip</description>
		<content:encoded><![CDATA[<p>Hi Toby</p>
<p>Thanks for the debate provoking comments.</p>
<p>I agree re OneAPI .. this should be the Operators killer differentiator making their infrastructure available for developers to use &#8211; low cost, fast and easy to work with. Operators need to grasp the opportunity and move at internet speeds. Remember &#8230; most people don&#8217;t have fancy smartphones yet so operators have a real opportunity eg using their billing relationship , location data, profiling etc.</p>
<p>2010 will be an interesting year.</p>
<p>Philip</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby</title>
		<link>http://www.slamobileblog.com/2010/02/23/reflections-on-mobile-world-congress-2010-%e2%80%93-barcelona/comment-page-1/#comment-52</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Tue, 23 Feb 2010 15:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.slamobileblog.com/?p=132#comment-52</guid>
		<description>What I find interesting about this is that everyone is pretty much in agreement that Mobile is going to be the next big computing platform - and everyone wants control of that platform.  Out of this, there seem to be three and a half major players:

- Apple
- Microsoft
- OneAPI (Incumbents).
- Google (1/2 due to inexperience).

Here&#039;s the funny bit:  Logically, I think OneAPI should be the clear favourite.  Massive resources + extremely large customer base + must win situation.

...but practically, I don&#039;t think they have much of a chance.  Too much politics plus software driven by marketing people who only understand the technology they can hold - which can never be used to predict the future.  

If the battle comes down to Apple, Google and MSFT, then we will likely see multiple winners because the solution is an OS.  ...but I think the big losers will be the Opcos. 

10 years ago, who would have thought Apple would be such a threat to the entire telecommunications industry?  ...Steve Jobs apparently.  :-)</description>
		<content:encoded><![CDATA[<p>What I find interesting about this is that everyone is pretty much in agreement that Mobile is going to be the next big computing platform &#8211; and everyone wants control of that platform.  Out of this, there seem to be three and a half major players:</p>
<p>- Apple<br />
- Microsoft<br />
- OneAPI (Incumbents).<br />
- Google (1/2 due to inexperience).</p>
<p>Here&#8217;s the funny bit:  Logically, I think OneAPI should be the clear favourite.  Massive resources + extremely large customer base + must win situation.</p>
<p>&#8230;but practically, I don&#8217;t think they have much of a chance.  Too much politics plus software driven by marketing people who only understand the technology they can hold &#8211; which can never be used to predict the future.  </p>
<p>If the battle comes down to Apple, Google and MSFT, then we will likely see multiple winners because the solution is an OS.  &#8230;but I think the big losers will be the Opcos. </p>
<p>10 years ago, who would have thought Apple would be such a threat to the entire telecommunications industry?  &#8230;Steve Jobs apparently.  <img src='http://www.slamobileblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

