<?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 Meaning of Droid</title>
	<atom:link href="http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/</link>
	<description>Media, Tech &#38; Business Models</description>
	<lastBuildDate>Fri, 10 Feb 2012 03:09:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: bird houses for sale</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-15466</link>
		<dc:creator>bird houses for sale</dc:creator>
		<pubDate>Mon, 23 May 2011 22:34:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-15466</guid>
		<description>thank you for all this new and useful information, it will most certainly come in handy</description>
		<content:encoded><![CDATA[<p>thank you for all this new and useful information, it will most certainly come in handy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Meaning of Droid &#124; Monday Note &#187; andrewsavikas.com</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-6129</link>
		<dc:creator>The Meaning of Droid &#124; Monday Note &#187; andrewsavikas.com</dc:creator>
		<pubDate>Fri, 03 Sep 2010 00:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-6129</guid>
		<description>[...] http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/" rel="nofollow">http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fajar</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-4868</link>
		<dc:creator>fajar</dc:creator>
		<pubDate>Mon, 12 Jul 2010 02:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-4868</guid>
		<description>mantapsss</description>
		<content:encoded><![CDATA[<p>mantapsss</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Osborne</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-2470</link>
		<dc:creator>J Osborne</dc:creator>
		<pubDate>Tue, 23 Mar 2010 20:14:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-2470</guid>
		<description>&quot;google chose to use a Java VM model to allow for HW/CPU abstraction, which results in slow(er) apps&quot;

Well, sort of.   The JVM model forces you to use a specific intermediate language at some point (JVM bytecodes), and forces the final device to take JVM bytecodes and &quot;do something&quot; with them.   &quot;Something&quot; could be directly execute them, interpret them, just in time compile them, or compile them at install time into native executables.

The model Apple has chosen doesn&#039;t force a specific intermediate language, but for all practical purposes there are really only two, the internal intermediate languages that gcc or llvm use.  They then go on to generate ARM code that the CPU executes directly.

The two models aren&#039;t as distinct as people tend to make them out.   If the JVM bytecode is compiled at install time to a native format then there are similar results.

The real issue is how &quot;device independent&quot; Apple&#039;s Cocoa and UIKit are vs. how &quot;device independent&quot; Android&#039;s equivalent layers are.   Too much and it is hard to write specifically for a device.   Too little and it is hard for the devices to change...  and that isn&#039;t really dependent on ABI or language choice.

(nor is how uniform the hardware actually is...can an app rely on touch being present?   multiple fingers?   how big is the display?  what is the resolution?   what is the aspect ratio?   For Android all those things are questions.   For iPhone/iPod Touch those are all constant.   For iPhone/iPod Touch + iPad a few of those things become questions, but at least they are only questions with a limited set of answers; this makes a huge difference in how hard it is to make apps, and how well fitted those apps can be to the hardware)</description>
		<content:encoded><![CDATA[<p>&#8220;google chose to use a Java VM model to allow for HW/CPU abstraction, which results in slow(er) apps&#8221;</p>
<p>Well, sort of.   The JVM model forces you to use a specific intermediate language at some point (JVM bytecodes), and forces the final device to take JVM bytecodes and &#8220;do something&#8221; with them.   &#8220;Something&#8221; could be directly execute them, interpret them, just in time compile them, or compile them at install time into native executables.</p>
<p>The model Apple has chosen doesn&#8217;t force a specific intermediate language, but for all practical purposes there are really only two, the internal intermediate languages that gcc or llvm use.  They then go on to generate ARM code that the CPU executes directly.</p>
<p>The two models aren&#8217;t as distinct as people tend to make them out.   If the JVM bytecode is compiled at install time to a native format then there are similar results.</p>
<p>The real issue is how &#8220;device independent&#8221; Apple&#8217;s Cocoa and UIKit are vs. how &#8220;device independent&#8221; Android&#8217;s equivalent layers are.   Too much and it is hard to write specifically for a device.   Too little and it is hard for the devices to change&#8230;  and that isn&#8217;t really dependent on ABI or language choice.</p>
<p>(nor is how uniform the hardware actually is&#8230;can an app rely on touch being present?   multiple fingers?   how big is the display?  what is the resolution?   what is the aspect ratio?   For Android all those things are questions.   For iPhone/iPod Touch those are all constant.   For iPhone/iPod Touch + iPad a few of those things become questions, but at least they are only questions with a limited set of answers; this makes a huge difference in how hard it is to make apps, and how well fitted those apps can be to the hardware)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Who will buy Palm? &#124; Monday Note</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-2330</link>
		<dc:creator>Who will buy Palm? &#124; Monday Note</dc:creator>
		<pubDate>Sun, 21 Mar 2010 18:36:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-2330</guid>
		<description>[...] only to take a less advantageous deal later and too late. By then, everyone knew about the Pre’s tepid reception at Sprint, taking any leverage away from Palm in discussions with other [...]</description>
		<content:encoded><![CDATA[<p>[...] only to take a less advantageous deal later and too late. By then, everyone knew about the Pre’s tepid reception at Sprint, taking any leverage away from Palm in discussions with other [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Apple Licensing Myth &#124; Monday Note</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1947</link>
		<dc:creator>The Apple Licensing Myth &#124; Monday Note</dc:creator>
		<pubDate>Sun, 17 Jan 2010 17:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1947</guid>
		<description>[...] Apple could indeed end up “losing” the smartphone market to Android, just as it “loses” the PC market today, making more money than Dell and HP combined, they with a 33% market share and Apple with less than 10%. (More details in the November 1st, 2009 Monday Note.) [...]</description>
		<content:encoded><![CDATA[<p>[...] Apple could indeed end up “losing” the smartphone market to Android, just as it “loses” the PC market today, making more money than Dell and HP combined, they with a 33% market share and Apple with less than 10%. (More details in the November 1st, 2009 Monday Note.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Droid and Android &#124; Monday Note</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1705</link>
		<dc:creator>Droid and Android &#124; Monday Note</dc:creator>
		<pubDate>Sun, 15 Nov 2009 17:01:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1705</guid>
		<description>[...] there is ample evidence Apple puts profits before market share. As we saw two weeks ago, with less than 10% market share it makes twice as much money as HP and Dell who, combined, command [...]</description>
		<content:encoded><![CDATA[<p>[...] there is ample evidence Apple puts profits before market share. As we saw two weeks ago, with less than 10% market share it makes twice as much money as HP and Dell who, combined, command [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: heeatseverything</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1695</link>
		<dc:creator>heeatseverything</dc:creator>
		<pubDate>Sat, 14 Nov 2009 03:32:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1695</guid>
		<description>Come on it&#039;s the 13th already.  When are you going to &quot;get one ASAP and report&quot;?</description>
		<content:encoded><![CDATA[<p>Come on it&#8217;s the 13th already.  When are you going to &#8220;get one ASAP and report&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elishia Windfohr</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1663</link>
		<dc:creator>Elishia Windfohr</dc:creator>
		<pubDate>Sun, 08 Nov 2009 10:46:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1663</guid>
		<description>We really do ned some good smartphones that actually work! tired of thm getting hot etc, I have hope for the blackberry though. great post though

Elishia Windfohr</description>
		<content:encoded><![CDATA[<p>We really do ned some good smartphones that actually work! tired of thm getting hot etc, I have hope for the blackberry though. great post though</p>
<p>Elishia Windfohr</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jahangir Naina</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1638</link>
		<dc:creator>Jahangir Naina</dc:creator>
		<pubDate>Wed, 04 Nov 2009 04:59:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1638</guid>
		<description>I think a lot of folks discount the level of integration and polish needed to make a truly useable consumer targetted smartphones. Apple has UI finesse in their DNA and knows how to make the whole kit, giving their users &quot;it just works&quot; level of product purity. The Android model is similar to the WinMo model where the final integration is done by the OEM/ODM, carrier or some MVNO outfit. The end result being each iteration of an Android or WinMo phone has enough of a difference to fragment the all-important &quot;platform&quot;.

Give it time, the Android user base WILL get fragmented. Fragmentation along the lines of SW version (remember some earlier Android phones cannot be field updateable for firmware), custom UI shells/themes, customizations, etc. Second, the Android suffers from a bad design decision in that it only has 512MB for both the OS and apps to play. This WILL limit applications beyond only the simple. Third, google chose to use a Java VM model to allow for HW/CPU abstraction, which results in slow(er) apps. The iPhone will not suffer as much in terms of abstraction, and will be truly able to grow not just the userbase, but also the platform.</description>
		<content:encoded><![CDATA[<p>I think a lot of folks discount the level of integration and polish needed to make a truly useable consumer targetted smartphones. Apple has UI finesse in their DNA and knows how to make the whole kit, giving their users &#8220;it just works&#8221; level of product purity. The Android model is similar to the WinMo model where the final integration is done by the OEM/ODM, carrier or some MVNO outfit. The end result being each iteration of an Android or WinMo phone has enough of a difference to fragment the all-important &#8220;platform&#8221;.</p>
<p>Give it time, the Android user base WILL get fragmented. Fragmentation along the lines of SW version (remember some earlier Android phones cannot be field updateable for firmware), custom UI shells/themes, customizations, etc. Second, the Android suffers from a bad design decision in that it only has 512MB for both the OS and apps to play. This WILL limit applications beyond only the simple. Third, google chose to use a Java VM model to allow for HW/CPU abstraction, which results in slow(er) apps. The iPhone will not suffer as much in terms of abstraction, and will be truly able to grow not just the userbase, but also the platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Per Bothner</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1634</link>
		<dc:creator>Per Bothner</dc:creator>
		<pubDate>Tue, 03 Nov 2009 17:42:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1634</guid>
		<description>This sentence seems rather questionable: &quot;It is significantly harder to write applications for the Blackberry, it uses Java and, as a result, the applications have less “expressive powers” than with other operating systems&quot;. &#039; First, I&#039;m not sure why you think using Java gives applications &quot;less expressive powers&quot;.  Secondly, you realize Android also uses Java?</description>
		<content:encoded><![CDATA[<p>This sentence seems rather questionable: &#8220;It is significantly harder to write applications for the Blackberry, it uses Java and, as a result, the applications have less “expressive powers” than with other operating systems&#8221;. &#8216; First, I&#8217;m not sure why you think using Java gives applications &#8220;less expressive powers&#8221;.  Secondly, you realize Android also uses Java?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: srinio</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1630</link>
		<dc:creator>srinio</dc:creator>
		<pubDate>Tue, 03 Nov 2009 13:04:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1630</guid>
		<description>Hey thanks for this post, it has been very helpful to me. Thank you very much.</description>
		<content:encoded><![CDATA[<p>Hey thanks for this post, it has been very helpful to me. Thank you very much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google’s Disruption Leads to Commoditization &#124; CloudAve</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1626</link>
		<dc:creator>Google’s Disruption Leads to Commoditization &#124; CloudAve</dc:creator>
		<pubDate>Tue, 03 Nov 2009 01:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1626</guid>
		<description>[...] The Meaning of Droid (mondaynote.com) [...]</description>
		<content:encoded><![CDATA[<p>[...] The Meaning of Droid (mondaynote.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom b</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1624</link>
		<dc:creator>tom b</dc:creator>
		<pubDate>Mon, 02 Nov 2009 21:21:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1624</guid>
		<description>Right now, the iPhone is priced to sell. I expect this will prevent Droid from stealing share. Also, in the US, Droid is tied to Verizon, a CDMA network, and a carrier more despised than ATT. Verizon always cripples their phones; they will do it with Droid, as well. I don&#039;t see a winning strategy for Droid, long term, because of the first point, economies of scale.</description>
		<content:encoded><![CDATA[<p>Right now, the iPhone is priced to sell. I expect this will prevent Droid from stealing share. Also, in the US, Droid is tied to Verizon, a CDMA network, and a carrier more despised than ATT. Verizon always cripples their phones; they will do it with Droid, as well. I don&#8217;t see a winning strategy for Droid, long term, because of the first point, economies of scale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Verizon Droid</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1620</link>
		<dc:creator>Verizon Droid</dc:creator>
		<pubDate>Mon, 02 Nov 2009 14:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1620</guid>
		<description>We think that the Droid will be a great device.
&lt;a href=&quot;http://verizon-droid.com&quot; rel=&quot;nofollow&quot;&gt;Verizon Droid&lt;/a&gt; fansite</description>
		<content:encoded><![CDATA[<p>We think that the Droid will be a great device.<br />
<a href="http://verizon-droid.com" rel="nofollow">Verizon Droid</a> fansite</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Howell</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1616</link>
		<dc:creator>Richard Howell</dc:creator>
		<pubDate>Mon, 02 Nov 2009 10:00:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1616</guid>
		<description>I think the &quot;correct&quot; last link should be: http://www.businessinsider.com/facebooks-self-service-ads-are-ridiculously-easy-to-make-2009-10#go-to-facebookcomadvertising-1</description>
		<content:encoded><![CDATA[<p>I think the &#8220;correct&#8221; last link should be: <a href="http://www.businessinsider.com/facebooks-self-service-ads-are-ridiculously-easy-to-make-2009-10#go-to-facebookcomadvertising-1" rel="nofollow">http://www.businessinsider.com/facebooks-self-service-ads-are-ridiculously-easy-to-make-2009-10#go-to-facebookcomadvertising-1</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Youssef Rahoui</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1610</link>
		<dc:creator>Youssef Rahoui</dc:creator>
		<pubDate>Mon, 02 Nov 2009 02:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1610</guid>
		<description>A brilliant overview, thanks.

PS: the last link does not work.</description>
		<content:encoded><![CDATA[<p>A brilliant overview, thanks.</p>
<p>PS: the last link does not work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Coldwell</title>
		<link>http://www.mondaynote.com/2009/11/01/the-meaning-of-droid/#comment-1606</link>
		<dc:creator>Tim Coldwell</dc:creator>
		<pubDate>Mon, 02 Nov 2009 00:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mondaynote.com/?p=2196#comment-1606</guid>
		<description>Yet more disruption is the meaning of Droid. Google will give you ad splits on search if you [carrier] use it.  That’s right; Google will pay you to use their mobile OS.

http://abovethecrowd.com/2009/10/29/google-redefines-disruption-the-%E2%80%9Cless-than-free%E2%80%9D-business-model/</description>
		<content:encoded><![CDATA[<p>Yet more disruption is the meaning of Droid. Google will give you ad splits on search if you [carrier] use it.  That’s right; Google will pay you to use their mobile OS.</p>
<p><a href="http://abovethecrowd.com/2009/10/29/google-redefines-disruption-the-%E2%80%9Cless-than-free%E2%80%9D-business-model/" rel="nofollow">http://abovethecrowd.com/2009/10/29/google-redefines-disruption-the-%E2%80%9Cless-than-free%E2%80%9D-business-model/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

