<?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"
	>
<channel>
	<title>Comments on: Putting The Android SDK In Perspective</title>
	<atom:link href="http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/</link>
	<description>Simon Brocklehurst's Technology Blog</description>
	<pubDate>Sun, 23 Nov 2008 09:53:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: simon</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-209705</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Tue, 08 Jan 2008 19:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-209705</guid>
		<description>Wow, Asam -  that is hilarious! I may have to blog about it.   The authors of the article have their Ada agenda to push.  I assume they're frustrated that students aren't being taught to program in Ada; and that there's close to zero demand for Ada programming/software.

There is nothing about Java that should lead to the kind of problems these people say they've observed.  The kind of problems they've observed are due to low quality students and/or low quality teaching.</description>
		<content:encoded><![CDATA[<p>Wow, Asam -  that is hilarious! I may have to blog about it.   The authors of the article have their Ada agenda to push.  I assume they&#8217;re frustrated that students aren&#8217;t being taught to program in Ada; and that there&#8217;s close to zero demand for Ada programming/software.</p>
<p>There is nothing about Java that should lead to the kind of problems these people say they&#8217;ve observed.  The kind of problems they&#8217;ve observed are due to low quality students and/or low quality teaching.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asam Bashir</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-209560</link>
		<dc:creator>Asam Bashir</dc:creator>
		<pubDate>Tue, 08 Jan 2008 16:27:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-209560</guid>
		<description>http://developers.slashdot.org/article.pl?sid=08/01/08/0348239

"Professors Slam Java As "Damaging" To Students"</description>
		<content:encoded><![CDATA[<p><a href="http://developers.slashdot.org/article.pl?sid=08/01/08/0348239" rel="nofollow">http://developers.slashdot.org/article.pl?sid=08/01/08/0348239</a></p>
<p>&#8220;Professors Slam Java As &#8220;Damaging&#8221; To Students&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mr X</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-158783</link>
		<dc:creator>Mr X</dc:creator>
		<pubDate>Wed, 28 Nov 2007 11:14:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-158783</guid>
		<description>What is an operating system beyond the hardware abstraction layers for screen, input, memory, storage etc? It's an attempt at an integrated user experience. 

However if you critically look at OS's today then they really haven't moved that far from the innovation of cut&#38;paste and drag&#38;drop implemented for quite simple data types, and a fairly unsophisticated linking of data with applications using extensions!

The web on the one hand has made it much easier to *code* adhoc  application integration, on the other hand has made it harder for end user driven resuse - look at the difficulty with cut and paste of web content. Though another great invention which is under valued is the use of mime-types and handlers.

It's a fundamentally hard problem - hence the failure of things like publish and subscribe, open doc etc. 

An interesting approach is taken by things like Enzo and Apple's Automator - essentially recognise that creating easy workflows actually does require some coding - the aim should be to make that coding as easy a possible so the end user can do it - essentially a unix type approach. ( Doomed to invent and all that )

I agree that zero install is important, but I also think it's easily fixable - what's hard, but what frustrates people and frankly what sold the iPod to a large degree is all this messing about people have to do copying this to that, reformatting, ripping, importing, exporting .

ie if I want to put this address in this email in my contacts, why do I have to retype the damn thing? Apple have actually addressed this much better in Leopard. 

If the android platform makes it easy for developers to make it easy for end-users to install programs which make it easy to synch their desktop picture with some online account - that google has no interest in - then they will have succeeded.</description>
		<content:encoded><![CDATA[<p>What is an operating system beyond the hardware abstraction layers for screen, input, memory, storage etc? It&#8217;s an attempt at an integrated user experience. </p>
<p>However if you critically look at OS&#8217;s today then they really haven&#8217;t moved that far from the innovation of cut&amp;paste and drag&amp;drop implemented for quite simple data types, and a fairly unsophisticated linking of data with applications using extensions!</p>
<p>The web on the one hand has made it much easier to *code* adhoc  application integration, on the other hand has made it harder for end user driven resuse - look at the difficulty with cut and paste of web content. Though another great invention which is under valued is the use of mime-types and handlers.</p>
<p>It&#8217;s a fundamentally hard problem - hence the failure of things like publish and subscribe, open doc etc. </p>
<p>An interesting approach is taken by things like Enzo and Apple&#8217;s Automator - essentially recognise that creating easy workflows actually does require some coding - the aim should be to make that coding as easy a possible so the end user can do it - essentially a unix type approach. ( Doomed to invent and all that )</p>
<p>I agree that zero install is important, but I also think it&#8217;s easily fixable - what&#8217;s hard, but what frustrates people and frankly what sold the iPod to a large degree is all this messing about people have to do copying this to that, reformatting, ripping, importing, exporting .</p>
<p>ie if I want to put this address in this email in my contacts, why do I have to retype the damn thing? Apple have actually addressed this much better in Leopard. </p>
<p>If the android platform makes it easy for developers to make it easy for end-users to install programs which make it easy to synch their desktop picture with some online account - that google has no interest in - then they will have succeeded.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-158210</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Tue, 27 Nov 2007 21:30:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-158210</guid>
		<description>That &lt;i&gt;is&lt;/i&gt; an interesting way of doing things.  It needs some thinking about though  -at least, I feel that &lt;i&gt;I&lt;/i&gt; need to think about it some more. My instinct is that, while it's nice, it's not actually going to be a critical success factor.

I don't under-estimate the points you make about web apps - they are important. Rather, I think there's something that's more important: that is, the "zero install" nature of web apps.

So, I suspect the phone software platforms that will succeed &lt;i&gt;big-time&lt;/i&gt; are those that can deploy rich applications with &lt;i&gt;no manual installation steps&lt;/i&gt; and &lt;i&gt;zero admin for updating to new versions&lt;/i&gt;.  Not sure how Android deals with that (if indeed it does deal with it at all).  Compare that to Flash (and Flash Lite), and Java SE applets.  The former work pretty well today, that latter is starting to look like it might work pretty well (perhaps even on JavaFX Mobile phones) in 2008.   There's a big opportunity for the consumer JavaFX Mobile/Java SE guys to do something amazing, if the phone hardware is up to it - but it will need top-end CPUs, like the iPhone has.


Also, even having said that, the software platform isn't even close to being the whole story. The device hardware is also critically important. Post-iPhone, the mobile phone world has changed - consumer device designers really have to up their games now.   I can see Android and JavaFX Mobile phones easily ending up being like Amazon's new Kindle (e-book reader).  That is - good ideas, but just incredibly poorly executed...
</description>
		<content:encoded><![CDATA[<p>That <i>is</i> an interesting way of doing things.  It needs some thinking about though  -at least, I feel that <i>I</i> need to think about it some more. My instinct is that, while it&#8217;s nice, it&#8217;s not actually going to be a critical success factor.</p>
<p>I don&#8217;t under-estimate the points you make about web apps - they are important. Rather, I think there&#8217;s something that&#8217;s more important: that is, the &#8220;zero install&#8221; nature of web apps.</p>
<p>So, I suspect the phone software platforms that will succeed <i>big-time</i> are those that can deploy rich applications with <i>no manual installation steps</i> and <i>zero admin for updating to new versions</i>.  Not sure how Android deals with that (if indeed it does deal with it at all).  Compare that to Flash (and Flash Lite), and Java SE applets.  The former work pretty well today, that latter is starting to look like it might work pretty well (perhaps even on JavaFX Mobile phones) in 2008.   There&#8217;s a big opportunity for the consumer JavaFX Mobile/Java SE guys to do something amazing, if the phone hardware is up to it - but it will need top-end CPUs, like the iPhone has.</p>
<p>Also, even having said that, the software platform isn&#8217;t even close to being the whole story. The device hardware is also critically important. Post-iPhone, the mobile phone world has changed - consumer device designers really have to up their games now.   I can see Android and JavaFX Mobile phones easily ending up being like Amazon&#8217;s new Kindle (e-book reader).  That is - good ideas, but just incredibly poorly executed&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mr X</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-157853</link>
		<dc:creator>Mr X</dc:creator>
		<pubDate>Tue, 27 Nov 2007 10:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-157853</guid>
		<description>One interesting aspect of the Android platform is the design - Activities and Intents. Activities are addressable parts of an application - Intents a decoupled way of addressing them.

Essentially they have learned that one of the benefits of the nature of the web platform is it leads to easy decomposition of applications with addressable parts - generally easy to link directly to a specific part of an app - say compose email  or read a specific message - web applications tended to be built on a screen by screen basis.

Also as most web apps are fairly stateless ( on the client ) how to construct a web page in a certain state is fairly simple as the parameters go into the network call.</description>
		<content:encoded><![CDATA[<p>One interesting aspect of the Android platform is the design - Activities and Intents. Activities are addressable parts of an application - Intents a decoupled way of addressing them.</p>
<p>Essentially they have learned that one of the benefits of the nature of the web platform is it leads to easy decomposition of applications with addressable parts - generally easy to link directly to a specific part of an app - say compose email  or read a specific message - web applications tended to be built on a screen by screen basis.</p>
<p>Also as most web apps are fairly stateless ( on the client ) how to construct a web page in a certain state is fairly simple as the parameters go into the network call.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VisionMobile Forum :: The significance of Google&#8217;s Android</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-156762</link>
		<dc:creator>VisionMobile Forum :: The significance of Google&#8217;s Android</dc:creator>
		<pubDate>Sun, 25 Nov 2007 16:04:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-156762</guid>
		<description>[...] with the underlying Linux support package. In other words, the Java SE-like platform is a native application platform for Android phones. Symbian may arrogantly dismiss Android as yet another Linux initiative, but the breadth and depth [...]</description>
		<content:encoded><![CDATA[<p>[...] with the underlying Linux support package. In other words, the Java SE-like platform is a native application platform for Android phones. Symbian may arrogantly dismiss Android as yet another Linux initiative, but the breadth and depth [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-150466</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Fri, 16 Nov 2007 11:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-150466</guid>
		<description>&lt;p&gt;Asam said, &lt;i&gt;How are Nokia and SE going to suddenly start making interfaces with the profound insight Apple has?"&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;I actually think this is where something like JavaFX Mobile can help the big handset manufacturers.  The big advantage of the iPhone form factor is that 90% of the interface is software, and can be upgraded remotely in the field via iTunes updates.   Phones built around JavaFX mobile could have similar advantages.&lt;/p&gt;
&lt;p&gt;Why could that that help?  Because it means the manufacturers don't have to get everything right first time, and a core strength of JavaFX Mobile, if Sun executes well, will be that it will be the easiest of all mobile platforms to build super-compelling user interfaces via JavaFX Script.    However - it's not out yet, so we'll have to wait and see how well it turns out - the guys at Sun have really got their work cut out for them bringing all the consumer Java stuff together. &lt;/p&gt;
&lt;p&gt;Asam said,&lt;i&gt; "PS where is Google going to for deep human user interface insight? Like, who has it been working with on its Google apps?"&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;Not sure they're going to anyone.  Apple writes the "Google" apps for iPhone, not Google.&lt;/p&gt;
&lt;p&gt;Asam said, &lt;i&gt; "Java developers, guys you need to wise up and learn how a really good human interface works, the only way you’ll be able to do this is to go buy a Mac and an iPhone…"&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;Not sure why you single out Java developers.   Developers in general often have a poor understanding of user interface design.  This is partly what's led to the new trends in tooling that allow graphics interaction designers to put interfaces together, while developers write code that hooks into the interfaces.  &lt;/p&gt;
&lt;p&gt;It's a reasonable way of working... except: "graphics interaction designers" usually know as much about user interface design as developers do (i.e. not much); and also that probably 90% of all software development projects don't have the budget to allow development of really compelling interfaces.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Asam said, <i>How are Nokia and SE going to suddenly start making interfaces with the profound insight Apple has?&#8221;</i></p>
<p>I actually think this is where something like JavaFX Mobile can help the big handset manufacturers.  The big advantage of the iPhone form factor is that 90% of the interface is software, and can be upgraded remotely in the field via iTunes updates.   Phones built around JavaFX mobile could have similar advantages.</p>
<p>Why could that that help?  Because it means the manufacturers don&#8217;t have to get everything right first time, and a core strength of JavaFX Mobile, if Sun executes well, will be that it will be the easiest of all mobile platforms to build super-compelling user interfaces via JavaFX Script.    However - it&#8217;s not out yet, so we&#8217;ll have to wait and see how well it turns out - the guys at Sun have really got their work cut out for them bringing all the consumer Java stuff together. </p>
<p>Asam said,<i> &#8220;PS where is Google going to for deep human user interface insight? Like, who has it been working with on its Google apps?&#8221;</i></p>
<p>Not sure they&#8217;re going to anyone.  Apple writes the &#8220;Google&#8221; apps for iPhone, not Google.</p>
<p>Asam said, <i> &#8220;Java developers, guys you need to wise up and learn how a really good human interface works, the only way you’ll be able to do this is to go buy a Mac and an iPhone…&#8221;</i></p>
<p>Not sure why you single out Java developers.   Developers in general often have a poor understanding of user interface design.  This is partly what&#8217;s led to the new trends in tooling that allow graphics interaction designers to put interfaces together, while developers write code that hooks into the interfaces.  </p>
<p>It&#8217;s a reasonable way of working&#8230; except: &#8220;graphics interaction designers&#8221; usually know as much about user interface design as developers do (i.e. not much); and also that probably 90% of all software development projects don&#8217;t have the budget to allow development of really compelling interfaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asam Bashir</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-150099</link>
		<dc:creator>Asam Bashir</dc:creator>
		<pubDate>Thu, 15 Nov 2007 23:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-150099</guid>
		<description>&lt;p&gt;In response to Simon, "Apple should be in strong position here, I agree. However, it’s worth noting that Sun is not trying to build phone hardware. Rather, they’re hoping to license the JavaFX Mobile OS platform to the big players like Samsung, Nokia, Sony Ericsson etc."&lt;/p&gt;
&lt;p&gt;So you don't see the most fundamental problem here? Sun with zero consumer level human interface experience, marketing a product to developers who will now try to adapt there brands of user interface to JavaFX - fools leading more fools? Problem with current phone is not the core OS, S60 3rd edition for example is an excellent implementation of Simbian, it's Nokia and SE's awful user interfaces that make the phones such a pain to use. How are Nokia and SE going to suddenly start making interfaces with the profound insight Apple has? By throwing money on it? Nope, MS has done that a million times and that does not work....&lt;/p&gt;

PS, where is Google going to for deep human user interface insight? Like, who has it been working with on it’s Google apps?

I have a simple message for all Java developers, guys you need to wise up and learn how a really good human interface works, the only way you’ll be able to do this is to go buy a Mac and an iPhone…


</description>
		<content:encoded><![CDATA[<p>In response to Simon, &#8220;Apple should be in strong position here, I agree. However, it’s worth noting that Sun is not trying to build phone hardware. Rather, they’re hoping to license the JavaFX Mobile OS platform to the big players like Samsung, Nokia, Sony Ericsson etc.&#8221;</p>
<p>So you don&#8217;t see the most fundamental problem here? Sun with zero consumer level human interface experience, marketing a product to developers who will now try to adapt there brands of user interface to JavaFX - fools leading more fools? Problem with current phone is not the core OS, S60 3rd edition for example is an excellent implementation of Simbian, it&#8217;s Nokia and SE&#8217;s awful user interfaces that make the phones such a pain to use. How are Nokia and SE going to suddenly start making interfaces with the profound insight Apple has? By throwing money on it? Nope, MS has done that a million times and that does not work&#8230;.</p>
<p>PS, where is Google going to for deep human user interface insight? Like, who has it been working with on it’s Google apps?</p>
<p>I have a simple message for all Java developers, guys you need to wise up and learn how a really good human interface works, the only way you’ll be able to do this is to go buy a Mac and an iPhone…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: simon</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-150050</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Thu, 15 Nov 2007 21:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-150050</guid>
		<description>&lt;p&gt;Asam said, &lt;i&gt;"if people decided to not buy Java phones next time they upgrade that figure could vanish in less the six months"&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;True. Let's see if Apple sells a billion iPhones during the next six months then ;-)  I predict it won't...&lt;/p&gt;
&lt;p&gt;Asam said, &lt;i&gt;"Sun will never catch up, why, simple, because it has zero real-world consumer human interface understanding, it would need 20 years of producing consumer orientated products to even come close to Apple’s expertise…"&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;Apple should be in strong position here, I agree.   However, it's worth noting that Sun is not trying to build phone hardware.  Rather, they're hoping to license the JavaFX Mobile OS platform to the big players like Samsung, Nokia, Sony Ericsson etc.&lt;/p&gt;
&lt;p&gt;Asam said, &lt;i&gt;"If you want to look at how marketshare can change in a matter of a few months, take a look at the new figures coming out for desktop OS share in Japan, Apple is wiping the board and currently at 60 % marketshare,"&lt;/i&gt;&lt;/p&gt;
&lt;p&gt;Well, not really.  In fact, not even close. Those figures are percentage market share for sales of shrinked-wrapped boxes with an OS DVD inside, during the time when Leopard was released.   This represents a zero percent real change in desktop OS market share.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Asam said, <i>&#8220;if people decided to not buy Java phones next time they upgrade that figure could vanish in less the six months&#8221;</i></p>
<p>True. Let&#8217;s see if Apple sells a billion iPhones during the next six months then <img src='http://www.psynixis.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  I predict it won&#8217;t&#8230;</p>
<p>Asam said, <i>&#8220;Sun will never catch up, why, simple, because it has zero real-world consumer human interface understanding, it would need 20 years of producing consumer orientated products to even come close to Apple’s expertise…&#8221;</i></p>
<p>Apple should be in strong position here, I agree.   However, it&#8217;s worth noting that Sun is not trying to build phone hardware.  Rather, they&#8217;re hoping to license the JavaFX Mobile OS platform to the big players like Samsung, Nokia, Sony Ericsson etc.</p>
<p>Asam said, <i>&#8220;If you want to look at how marketshare can change in a matter of a few months, take a look at the new figures coming out for desktop OS share in Japan, Apple is wiping the board and currently at 60 % marketshare,&#8221;</i></p>
<p>Well, not really.  In fact, not even close. Those figures are percentage market share for sales of shrinked-wrapped boxes with an OS DVD inside, during the time when Leopard was released.   This represents a zero percent real change in desktop OS market share.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asam Bashir</title>
		<link>http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-150034</link>
		<dc:creator>Asam Bashir</dc:creator>
		<pubDate>Thu, 15 Nov 2007 21:28:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/2007/11/14/putting-the-android-sdk-in-perspective/#comment-150034</guid>
		<description>If you want to look at how marketshare can change in a matter of a few months, take a look at the new figures coming out for desktop OS share in Japan, Apple is wiping the board and currently at 60 % marketshare, an incredible and profound change in global mind-set. The killer product for Japan hasn't even been released yet, that will mark the death-bed for Windows in Japan at least, ultra-compact form factor SSD based machine on schedule for release at MacWorld Expo, San Fran Jan 2008...</description>
		<content:encoded><![CDATA[<p>If you want to look at how marketshare can change in a matter of a few months, take a look at the new figures coming out for desktop OS share in Japan, Apple is wiping the board and currently at 60 % marketshare, an incredible and profound change in global mind-set. The killer product for Japan hasn&#8217;t even been released yet, that will mark the death-bed for Windows in Japan at least, ultra-compact form factor SSD based machine on schedule for release at MacWorld Expo, San Fran Jan 2008&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
