<?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: Why Google should have developed its own Gphone</title>
	<atom:link href="http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/</link>
	<description>Tracking the digital lifestyle</description>
	<lastBuildDate>Fri, 12 Mar 2010 20:04:25 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Len Feldman</title>
		<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/#comment-63575</link>
		<dc:creator>Len Feldman</dc:creator>
		<pubDate>Sun, 17 Aug 2008 23:37:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.last100.com/?p=2545#comment-63575</guid>
		<description>I agree with your conclusion that Google should have designed its own Gphone. In my opinion, they didn&#039;t for one of the reasons that you stated in your article--most of Google&#039;s products are in a perpetual beta state. It&#039;s far easier to iterate software than hardware. They would have had to get the Gphone right the first time, or the credibility of the entire project would have gone down the tubes. Think about it--if the original iPhone had been a dud, no one would have been waiting in line for the 3G version.

I don&#039;t think that Google expects the first versions of Android-based phones to be killer products, but they expect them to become killers over time. Google&#039;s executives probably expect that this will be a three- to five-year process. However, if Android doesn&#039;t come out strong and gains a user and developer following quickly, it may not be around in three to five years.</description>
		<content:encoded><![CDATA[<p>I agree with your conclusion that Google should have designed its own Gphone. In my opinion, they didn&#8217;t for one of the reasons that you stated in your article&#8211;most of Google&#8217;s products are in a perpetual beta state. It&#8217;s far easier to iterate software than hardware. They would have had to get the Gphone right the first time, or the credibility of the entire project would have gone down the tubes. Think about it&#8211;if the original iPhone had been a dud, no one would have been waiting in line for the 3G version.</p>
<p>I don&#8217;t think that Google expects the first versions of Android-based phones to be killer products, but they expect them to become killers over time. Google&#8217;s executives probably expect that this will be a three- to five-year process. However, if Android doesn&#8217;t come out strong and gains a user and developer following quickly, it may not be around in three to five years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cireasa</title>
		<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/#comment-63472</link>
		<dc:creator>cireasa</dc:creator>
		<pubDate>Fri, 15 Aug 2008 12:20:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.last100.com/?p=2545#comment-63472</guid>
		<description>Speaking of open-source, let&#039;s remember that OS X (apple) also has it&#039;s roots in FreeBSD. So, let&#039;s see what&#039;s going to happen along the way :)</description>
		<content:encoded><![CDATA[<p>Speaking of open-source, let&#8217;s remember that OS X (apple) also has it&#8217;s roots in FreeBSD. So, let&#8217;s see what&#8217;s going to happen along the way :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brandy</title>
		<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/#comment-63448</link>
		<dc:creator>brandy</dc:creator>
		<pubDate>Thu, 14 Aug 2008 23:42:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.last100.com/?p=2545#comment-63448</guid>
		<description>I would absolutely love to have a Gphone i would so buy it you should ask google to do it. who who</description>
		<content:encoded><![CDATA[<p>I would absolutely love to have a Gphone i would so buy it you should ask google to do it. who who</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve O'Hear, editor</title>
		<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/#comment-63434</link>
		<dc:creator>Steve O'Hear, editor</dc:creator>
		<pubDate>Thu, 14 Aug 2008 19:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.last100.com/?p=2545#comment-63434</guid>
		<description>@ Will

Any member of the Open Handset Alliance, or anybody, can alter the source code in their own use. The Open Source license is very forgiving. See my earlier post:
http://www.last100.com/2008/06/01/android-its-the-browser-stupi/</description>
		<content:encoded><![CDATA[<p>@ Will</p>
<p>Any member of the Open Handset Alliance, or anybody, can alter the source code in their own use. The Open Source license is very forgiving. See my earlier post:<br />
<a href="http://www.last100.com/2008/06/01/android-its-the-browser-stupi/" rel="nofollow">http://www.last100.com/2008/06.....ser-stupi/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/#comment-63433</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Thu, 14 Aug 2008 18:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.last100.com/?p=2545#comment-63433</guid>
		<description>Firstly nice post.

@Steve
There is the risk of fragmentation?  I realize that Android&#039;s going for open source, but there is still some level of copyright involved, so couldn&#039;t (and shouldn&#039;t) they make hardware providers place the whole OS on the devices?</description>
		<content:encoded><![CDATA[<p>Firstly nice post.</p>
<p>@Steve<br />
There is the risk of fragmentation?  I realize that Android&#8217;s going for open source, but there is still some level of copyright involved, so couldn&#8217;t (and shouldn&#8217;t) they make hardware providers place the whole OS on the devices?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve O'Hear, editor</title>
		<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/#comment-63426</link>
		<dc:creator>Steve O'Hear, editor</dc:creator>
		<pubDate>Thu, 14 Aug 2008 12:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.last100.com/?p=2545#comment-63426</guid>
		<description>@ Ontario Emperor

Windows Mobile may be a great example of where the Android strategy could fail. See &lt;a href=&quot;http://www.last100.com/2008/08/04/review-htc-touch-diamond/&quot; rel=&quot;nofollow&quot;&gt;my recent HTC Touch Diamond review.&lt;/a&gt;

There is also the risk that Android &lt;a href=&quot;http://www.last100.com/2008/07/24/qa-anddevorg-android/&quot; rel=&quot;nofollow&quot;&gt;could become fragmented&lt;/a&gt; if carriers decide to omit certain APIs or limit possible features.</description>
		<content:encoded><![CDATA[<p>@ Ontario Emperor</p>
<p>Windows Mobile may be a great example of where the Android strategy could fail. See <a href="http://www.last100.com/2008/08/04/review-htc-touch-diamond/" rel="nofollow">my recent HTC Touch Diamond review.</a></p>
<p>There is also the risk that Android <a href="http://www.last100.com/2008/07/24/qa-anddevorg-android/" rel="nofollow">could become fragmented</a> if carriers decide to omit certain APIs or limit possible features.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ontario Emperor</title>
		<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/#comment-63414</link>
		<dc:creator>Ontario Emperor</dc:creator>
		<pubDate>Wed, 13 Aug 2008 23:31:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.last100.com/?p=2545#comment-63414</guid>
		<description>(Disclosure - I work for a provider of Android applications.) 

Re your statement that “&#039;1,000&#039; similar but different Gphones&quot; could potentially confuse the customer - don&#039;t we already have 1,000 similar but different Windows Mobile phones already?

I will grant, however, that you have a point with Apple. Despite our love for open this and open that, our darling is one of the most proprietary companies out there.</description>
		<content:encoded><![CDATA[<p>(Disclosure &#8211; I work for a provider of Android applications.) </p>
<p>Re your statement that “&#8217;1,000&#8242; similar but different Gphones&#8221; could potentially confuse the customer &#8211; don&#8217;t we already have 1,000 similar but different Windows Mobile phones already?</p>
<p>I will grant, however, that you have a point with Apple. Despite our love for open this and open that, our darling is one of the most proprietary companies out there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alec</title>
		<link>http://www.last100.com/2008/08/13/why-google-should-have-developed-its-own-gphone/#comment-63411</link>
		<dc:creator>Alec</dc:creator>
		<pubDate>Wed, 13 Aug 2008 22:28:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.last100.com/?p=2545#comment-63411</guid>
		<description>Woot</description>
		<content:encoded><![CDATA[<p>Woot</p>
]]></content:encoded>
	</item>
</channel>
</rss>
