The BONDI specification attempts to define a generic JavaScript API that can be used to access mobile phone features such as the camera, geolocation, contacts, etc.

This is obviously an excellent idea.

The problem is that currently the specification is being written by people who've obviously never written JavaScript. Although this page does lead to other pages which eventually lead to actual JavaScript code examples, the whole thing is set up in an impossible-to-read Java format that has nothing to do with JavaScript and is very hard to interpret.

Still, it's the best we have right now.

I hope a future version of the specification will be written by someone with actual web development and JavaScript knowledge.

Android has been designed exceptionally well for 3rd party developers; the programming paradigm of Intents and Java-SE environment make programming apps a breeze.

However, when designing Android, the Google team had PC developers in mind. And in the mobile industry, it’s not 3rd party developers who create phones. It’s OEMs and their partners (so-called 2nd party developers). And the needs & wants of 2nd party developers are very different to those of 3rd parties.

OEMs care not just about speed of app development, but the speed of variant management; i.e. how quickly can you take one Android phone and create a second one that looks very different in a fraction of the time. Android is poorly designed in going from n to n+1 variant. You need to be re-customising the Java code for each app separately, playing with XML templates and inheritance operators alone will not help.

The trick is that, say, document.onclick exists as a property even if no event handler is set (except in Mozilla). Read out whether the property exists, and you know if a browser supports an event. (It's slightly more complicated than that, but not much.)

Palm now allows you to apply for a beta version of the webOS SDK, which includs the Mojo library. Maybe interesting; currently I'm wondering if I should sign up. (I wouldn't have the time to create a full app anyway, and I'm wondering what the SDK is worth without access to an actual Palm Pre.)

Anyway, I continue to be mildly impressed by Palm's wholesale gamble on the world of web development.