05 Nov

Google Android – YAP

Windows Mobile, BREW, Symbian, Web, UIQ, Java FX, S60, Palm OS, MIDP, Pocket PC, BlackBerry, SMS, Widgets, iPhone, and now Android…


Android, Yet Another Platform?

Let’s try to predict… Android, a Linux-based platform for mobile handsets that supports local applications via some kind of Java VM that is not Java ME/MIDP-based, with support to some kind of C-based SDK, and of course with support of mobile web applications via a local browser web-runtime, and access to services on the web such as OpenSocial API and other Google APIs. Anyone will be able to write applications for it, but at the end of the day, the carriers will still have control…

Google and the Open Handset Alliance, will it really change the game? It is possible; the landscape is changing… But Google ain’t Apple. Time will tell.

Related to this topic see:


6 thoughts on “Google Android – YAP

  1. Yes, seeing Aplix and Esmertec as members, I realize they would supply some kind of Java VM… hopefully minimizing new APIs or more fragmentation. Thanks.


  2. Android guys simply cannot mention supports “Java” as Android seems to be truly open and free to use in commercial device products. Java isn’t free for commercial usage as most TCKs (e.g. all from Sun) are missing open source licenses. See for good discussion about this:

    Esmertec and Aplix sell commercial Java implementation products as they have got licenses from Sun (and others) to the required Java ME TCKs. What it means that they are happy to see them also to Android using device manufacturers.

    What Java tech-ecosystem would need is fully free and open “Java”. I hope open handset alliance will eventually release also compatibility kits for free-Java but then everybody would start to use some other name for this technology. Hey OJ!

  3. Yes both Esmertec and Aplix who are part of the OHA have their own Java VMs and MIDP implementations. It is going to be interesting to see how all this evolves, and what VM vendor wins on what handsets. This of course doesn’t address the Java fragmentation problem. 🙂


Comments are closed.