<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: What&#8217;s this&#8230; Android on Shaky Ground?</title>
	<link>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/</link>
	<description>mobile marketing perspectives and analysis</description>
	<pubDate>Mon, 22 Mar 2010 12:41:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Ajay</title>
		<link>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-11022</link>
		<dc:creator>Ajay</dc:creator>
		<pubDate>Mon, 06 Jul 2009 01:19:18 +0000</pubDate>
		<guid>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-11022</guid>
		<description>You're giving them too much credit, there's no way that they want to hobble the desktop through fragmentation.  Besides, it's not like mobile devices can handle that much computation anyway so the more you offload to the server through thin clients, the better.  Fragmentation is a given in all technology, you'd like to avoid needless fragmentation but innovation only comes in through people trying new things and "fragmenting" a platform.  The alternative is Windows, where only Microsoft can decide what innovation is worthwhile, and the resulting stagnation.  I think it's to Google's credit that they chose such a liberal license like Eclipse and they will reap the rewards for doing so.  As for security, they've clearly not been as proactive as one'd hope but with an open source OS, they can now have many security firms looking for such flaws.  If they put up some kind of bug reward program, I'm sure they can get plenty of people looking for these holes for them.</description>
		<content:encoded><![CDATA[<p>You&#8217;re giving them too much credit, there&#8217;s no way that they want to hobble the desktop through fragmentation.  Besides, it&#8217;s not like mobile devices can handle that much computation anyway so the more you offload to the server through thin clients, the better.  Fragmentation is a given in all technology, you&#8217;d like to avoid needless fragmentation but innovation only comes in through people trying new things and &#8220;fragmenting&#8221; a platform.  The alternative is Windows, where only Microsoft can decide what innovation is worthwhile, and the resulting stagnation.  I think it&#8217;s to Google&#8217;s credit that they chose such a liberal license like Eclipse and they will reap the rewards for doing so.  As for security, they&#8217;ve clearly not been as proactive as one&#8217;d hope but with an open source OS, they can now have many security firms looking for such flaws.  If they put up some kind of bug reward program, I&#8217;m sure they can get plenty of people looking for these holes for them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Losing Focus on Android SDK In Favor of Mobile Web Apps’ Offline Functionality? (Part II) &#124; mobilestance.com</title>
		<link>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6394</link>
		<dc:creator>Google Losing Focus on Android SDK In Favor of Mobile Web Apps’ Offline Functionality? (Part II) &#124; mobilestance.com</dc:creator>
		<pubDate>Mon, 02 Mar 2009 12:47:13 +0000</pubDate>
		<guid>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6394</guid>
		<description>[...] What&#8217;s this&#8230; Android on Shaky Ground?  [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] What&#8217;s this&#8230; Android on Shaky Ground?  [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. Enrique Ortiz</title>
		<link>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6207</link>
		<dc:creator>C. Enrique Ortiz</dc:creator>
		<pubDate>Wed, 11 Feb 2009 22:24:37 +0000</pubDate>
		<guid>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6207</guid>
		<description>True that Android adds to the fragmentation game/issue. And that device manuf will do their own things. But there is where the OHA comes in -- OHA defines the "official" Android. In addition, Android is not fully open yet so Google still has a good grab on what Android is/means.</description>
		<content:encoded><![CDATA[<p>True that Android adds to the fragmentation game/issue. And that device manuf will do their own things. But there is where the OHA comes in &#8212; OHA defines the &#8220;official&#8221; Android. In addition, Android is not fully open yet so Google still has a good grab on what Android is/means.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SOSiPhone.com (Le Blog) &#187; Archive du blog &#187; Android, plate-forme qui va fragmenter le marchè ?</title>
		<link>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6184</link>
		<dc:creator>SOSiPhone.com (Le Blog) &#187; Archive du blog &#187; Android, plate-forme qui va fragmenter le marchè ?</dc:creator>
		<pubDate>Sat, 07 Feb 2009 16:02:34 +0000</pubDate>
		<guid>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6184</guid>
		<description>[...] d&#8217;incompatibilité au niveau des applications présentes sur l&#8217;Android Market. Le billet qui m&#8217;inspire celui-ci appel ça &#8220;la fragmentation&#8221; est pour lui c&#8217;est inévitable. Malheureusement en [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] d&#8217;incompatibilité au niveau des applications présentes sur l&#8217;Android Market. Le billet qui m&#8217;inspire celui-ci appel ça &#8220;la fragmentation&#8221; est pour lui c&#8217;est inévitable. Malheureusement en [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tane Piper</title>
		<link>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6152</link>
		<dc:creator>Tane Piper</dc:creator>
		<pubDate>Mon, 02 Feb 2009 20:40:49 +0000</pubDate>
		<guid>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6152</guid>
		<description>I think there may be some truth to this, although I don't think it will be in the web browser.  Google have recently published their findings and a new API based on OAuth - allowing web and "desktop" applications to access your contact data, amongst other things.  Over time I expect them to add more and more services to this, so that google becomes our main data provider.  Appengine too I think is part of this plan, allowing developers to create data on google services and tie it into your google account.</description>
		<content:encoded><![CDATA[<p>I think there may be some truth to this, although I don&#8217;t think it will be in the web browser.  Google have recently published their findings and a new API based on OAuth - allowing web and &#8220;desktop&#8221; applications to access your contact data, amongst other things.  Over time I expect them to add more and more services to this, so that google becomes our main data provider.  Appengine too I think is part of this plan, allowing developers to create data on google services and tie it into your google account.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Ebling</title>
		<link>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6148</link>
		<dc:creator>Andrew Ebling</dc:creator>
		<pubDate>Mon, 02 Feb 2009 06:06:23 +0000</pubDate>
		<guid>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6148</guid>
		<description>That's certainly an interesting line of thought and there is certainly a chance things may pan out as you have predicted.  However I don't believe it was Google's intent from the start, for the following reasons:

- The Android Developer Challenge shows at least some level of commitment to stimulating native application development on the platform.

- If Apple eventually broke down and opened the iPhone/iPod Touch up for native application (having pretended initially that web/thin client was the only development environment needed), why would Google deliberately plan to do something which would drive their own platform back in this direction?

- Google's own support of the iPhone through native application development shows that they still think there is (currently) a need which is fulfilled by native applications over web or thin client applications.

Personally, I think if Android becomes successful enough to survive long-term, we'll see Google introduce JSR-style standards to try and address fragmentation problems.

I think the success of the platform hangs on whether Google can prevent fragmentation from affecting the overall user-experience, rather than whether they can solve the problem for developers.   Given how high the iPhone has raised the bar in terms of user-experience, this will be the biggest challenge Google face going forward.</description>
		<content:encoded><![CDATA[<p>That&#8217;s certainly an interesting line of thought and there is certainly a chance things may pan out as you have predicted.  However I don&#8217;t believe it was Google&#8217;s intent from the start, for the following reasons:</p>
<p>- The Android Developer Challenge shows at least some level of commitment to stimulating native application development on the platform.</p>
<p>- If Apple eventually broke down and opened the iPhone/iPod Touch up for native application (having pretended initially that web/thin client was the only development environment needed), why would Google deliberately plan to do something which would drive their own platform back in this direction?</p>
<p>- Google&#8217;s own support of the iPhone through native application development shows that they still think there is (currently) a need which is fulfilled by native applications over web or thin client applications.</p>
<p>Personally, I think if Android becomes successful enough to survive long-term, we&#8217;ll see Google introduce JSR-style standards to try and address fragmentation problems.</p>
<p>I think the success of the platform hangs on whether Google can prevent fragmentation from affecting the overall user-experience, rather than whether they can solve the problem for developers.   Given how high the iPhone has raised the bar in terms of user-experience, this will be the biggest challenge Google face going forward.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Android: does it scale? &#124; The Mobile Web Tablet</title>
		<link>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6139</link>
		<dc:creator>Android: does it scale? &#124; The Mobile Web Tablet</dc:creator>
		<pubDate>Sun, 01 Feb 2009 13:00:11 +0000</pubDate>
		<guid>http://mobilestance.com/2009/01/31/whats-this-android-on-shaky-ground/#comment-6139</guid>
		<description>[...] Stance has a longer post on the subject, even suggesting that Google would benefit from fragmenting the OS as it would move [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Stance has a longer post on the subject, even suggesting that Google would benefit from fragmenting the OS as it would move [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
