Monday, November 26, 2007

More on Android and OSGi

As I wrote in one of my previous posts, Android is not a Java platform. However, it is "Java-like" enough to manage to get OSGi on it. I am happy to see this kind of experimentation, because I seriously think that OSGi has a potential to bring the concept of component orientation into the mobile area.

Monday, November 12, 2007

Google Android - is it the way to go?

Yesterday Google has released an early access version of the Android SDK. For the first look, it is nice. It is Java-compatible (at least on source level) and it has a component model. Its API looks well-thought.
However, there is a big problem with it: compatibility. Android's Dalvik VM is not a Java VM. Its byte code is not Java byte code. It uses different packaging conventions, and so on. Therefore, if Android will be successful, mobile application developers have to deal with at least two totally different platforms.
I agree that CDC/CLDC and MIDP have several weaknesses and MIDP does not have a component model. But these problems can be addressed in a standard way (see JSR232 or JSR271 for example). Even the weak UI can be improved using existing solutions like eSWT.
So the question is open: do developers really need Android?

Thursday, November 8, 2007

MIDP3 - is it worth waiting for it?

In 2005 I was very interested about the MIDP3 proposal, but now, two years later it seems a little bit outworn. The expert group is not an active one, they published the early draft review only in September, this year. If this progress will not speed up, I hardly believe that the first MIDP3-capable phones will hit the market before 2009. And there are other promising technologies like OSGi and Google's Android. OSGi has already reached the mobile market, thanks to Nokia, and the Android SDK will be available in a few days. I don't think Android is based on OSGi, but it is developed by smart people, so I hope its architecture will be straightforward.