<?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: 3GSM &#8212; Opera: Empowering Operators By Empowering Users</title>
	<atom:link href="http://mobhappy.com/blog1/2006/02/14/3gsm-opera-empowering-operators-by-empowering-users/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobhappy.com/blog1/2006/02/14/3gsm-opera-empowering-operators-by-empowering-users/</link>
	<description>Russell Buckley and Carlo Longino on mobile technology.</description>
	<lastBuildDate>Tue, 31 Jan 2012 19:56:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Carlo Longino</title>
		<link>http://mobhappy.com/blog1/2006/02/14/3gsm-opera-empowering-operators-by-empowering-users/comment-page-1/#comment-1916</link>
		<dc:creator>Carlo Longino</dc:creator>
		<pubDate>Thu, 16 Feb 2006 06:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://mobhappy.com/blog1/2006/02/14/3gsm-opera-empowering-operators-by-empowering-users/#comment-1916</guid>
		<description>Fair enough, but there are some significant differences between Opera Platform and Bluepulse, not the least of which is Opera&#039;s track record in this space. Another is that Opera is a technology enabler, and isn&#039;t trying to be a content provider, billing provider and take a cut of revenues. Its ability to work within (and improve) the existing ecosystem also makes it far more likely to succeed than a solution which tries to completely circumvent it.

Lowering the bar is another issue, too. While Opera Platform is currently available only on smartphone platforms, that&#039;s because only they can support the technology it uses. Particularly with smartphones making their way into the mass market, that&#039;s a far more compelling implementation than one which takes the opposite approach and supports a baseline technology so it can be deployed on as wide an array of handsets as possible.</description>
		<content:encoded><![CDATA[<p>Fair enough, but there are some significant differences between Opera Platform and Bluepulse, not the least of which is Opera&#8217;s track record in this space. Another is that Opera is a technology enabler, and isn&#8217;t trying to be a content provider, billing provider and take a cut of revenues. Its ability to work within (and improve) the existing ecosystem also makes it far more likely to succeed than a solution which tries to completely circumvent it.</p>
<p>Lowering the bar is another issue, too. While Opera Platform is currently available only on smartphone platforms, that&#8217;s because only they can support the technology it uses. Particularly with smartphones making their way into the mass market, that&#8217;s a far more compelling implementation than one which takes the opposite approach and supports a baseline technology so it can be deployed on as wide an array of handsets as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver Starr</title>
		<link>http://mobhappy.com/blog1/2006/02/14/3gsm-opera-empowering-operators-by-empowering-users/comment-page-1/#comment-1915</link>
		<dc:creator>Oliver Starr</dc:creator>
		<pubDate>Thu, 16 Feb 2006 04:20:52 +0000</pubDate>
		<guid isPermaLink="false">http://mobhappy.com/blog1/2006/02/14/3gsm-opera-empowering-operators-by-empowering-users/#comment-1915</guid>
		<description>Carlo,

Your appreciation of Opera is understandable.  A great product that  I use myself on every mobile phone I own.  I have to comment though about your particular appreciation of the &quot;widget strategy&quot; in light of your very negative sentiments towards another company that also is basing its future development in large part on user developed widgets; bluepulse.

Granted, Opera is a much more mature product with advanced technology, a very large userbase and obvious market support, but notwithstanding their unfortunuate incident with you related to their bad-blog behavior, it seems to me that they should at least be given some measure of credit for doing something you clearly think - at least when suggested by Opera- is worthwhile.

My thought would be that bluepulse is lowering the bar even more, making the development of widgets that much  easier and more accessible to an ever wider segment of mobile users.  This strategy of lowering the bar has had very good results in the past.  After all, making it possible for every 13 year old in the USA to build their own  web page is what made MySpace worth a half a billion dollars...

Oliver Starr
MobileCrunch.com</description>
		<content:encoded><![CDATA[<p>Carlo,</p>
<p>Your appreciation of Opera is understandable.  A great product that  I use myself on every mobile phone I own.  I have to comment though about your particular appreciation of the &#8220;widget strategy&#8221; in light of your very negative sentiments towards another company that also is basing its future development in large part on user developed widgets; bluepulse.</p>
<p>Granted, Opera is a much more mature product with advanced technology, a very large userbase and obvious market support, but notwithstanding their unfortunuate incident with you related to their bad-blog behavior, it seems to me that they should at least be given some measure of credit for doing something you clearly think &#8211; at least when suggested by Opera- is worthwhile.</p>
<p>My thought would be that bluepulse is lowering the bar even more, making the development of widgets that much  easier and more accessible to an ever wider segment of mobile users.  This strategy of lowering the bar has had very good results in the past.  After all, making it possible for every 13 year old in the USA to build their own  web page is what made MySpace worth a half a billion dollars&#8230;</p>
<p>Oliver Starr<br />
MobileCrunch.com</p>
]]></content:encoded>
	</item>
</channel>
</rss>

