Blog of Leonid Mamchenkov

A couple of weeks ago my beloved Sony Ericsson P910 died.  It got dropped one too many times.  A rather large semi-lequid patch appeared in its left bottom corner and touch screen stopped working.  Since the keyboard died a long time ago, I was left with no way to input or navigate the phone.  Being an exceptionally smart individual I decided that a reboot might cure this, and, obviously, that left me at the “Enter your PIN” prompt with no hope what so ever.

Next morning I rushed to the mobile shop.  The first two on my way were closed, since that was too early in the morning, but gladly I remembered that there is a Germanos branch in Debenhams, which opens pretty early.  Like 8 or 9 o’clock in the morning.  And indeed it was open.

[Read more →]

Today is the last day of The Mobile World Congress which takes place in Barcelona.  Makers of everything mobile (as in phones, not as in real estates opposite) are showing off their stuff at this event.  Also, there are many announcements, news, and releases tied to the dates of the congress.

It seems like a good time to revisit the Android story.  Is it moving it all?  What’s happening there?  Will we see any of it any time soon?

It appears that the Android is moving along as planned.  There were a few pre-production prototypes at The Mobile World Congress, and people were pretty much impressed with them.

The biggest surprise of the demos was how well Android runs on slow devices.

In other news, Google released a new version of Android SDK.  This new version brought a few major changes and improvements, fixed many things that developers complained about.

The upgrade also takes to heart developer complaints about the software and includes several major but less visible upgrades: in addition to easier development of layouts, any app can now translate addresses to map coordinates and back. Audio formats such as MIDI and OGG are now also built-in, according to Google.

The same source suggests that we will indeed see some phones in the second half of 2008, as it was planned and announced last year.

Android’s upgrade brings the Linux-based platform much closer to production quality for its expected release, which should start with handsets in the second half of the year from companies such as HTC, Motorola, LG, and Samsung. Most of these devices are understood to focus heavily on Internet access and are expected to include some models with GPS and touchscreens.

I was reading this post about Mobile World Congress over at Web Worker Daily.  This paragraph got me thinking:

At January’s Macworld show, Apple CEO Steve Jobs cited data from NPD showing that the iPhone already has 20 percent of the smartphone market after one year, and that Apple is selling 20,000 iPhones per day.

How often do you change your mobile?  And how often do you change your mobile phone vendor?  Are you a fan of one particular brand or do you like trying each and every one of them?

Mobile market is measured in billions of users.  And these users can be pretty dynamic about their devices and the choice of vendors.  Mobile phone is something very easily replaceable.  It’s not like a house, or a car, or even a laptop computer. The thought of how dynamic the market is boggles the mind.  One day you the king of the mountain, and the a couple of months later they don’t know your name. But then again you can get it back before the end of the year…

Tom Evslin has this interesting observation about the quality of voice in the traditional phone:

The bandwidth of the telephone connection between our homes and the telephone network hasn’t changed in my long lifetime. Although some noise has been eliminated in long distance calls (sometime and if we’re not on a cellphone), voices on the phone still sound like they did sixty-five years ago. We’ve trained ourselves to accept the clipped quality of a telephone voice with its lack of emotional overtones.
You wouldn’t dream of listening to music over the phone. You expect and get much better sound quality from almost any radio and on TV. Movies have Dolby sound. But the telephone is still the telephone.

He suggests that VoIP (think: Skype) is changing that.

Blogosphere keeps providing more and more insights into the Google Android story.  As I mentioned in my previous post, Android platform has a lot to do with Java.  In fact, many people consider the level to which Java is integrated into the platform to be the “big news”, unique and all.  Here is a quote from Simon Brocklehurst’s post titled “Putting The Android SDK In Perspective” (read the whole piece, it’s very good):

Android has integrated the Java platform deeply into the phone. In other words, it’s a native application platform for Android phones. No-one has done this before, and it will allow new types of application to be developed (Google has set aside $10M to give away to developers to stimulate development of such software - I hope young entrepreneurs use this opportunity, some great little companies could be started by following this path). It should be noted that Sun’s forthcoming mobile OS platform, JavaFX Mobile, is based around almost exactly the same concept.

After I read the last sentence, I realized that the story is even deeper than I thought.  Google is jumping into competition with Sun, using Sun’s own Java technology.  How is that possible?  Sun was never known for its generosity.  Did it suddenly change?  And what about Microsoft, who invest heavily into both Java and mobile industry?  How did they let this happen?  And what about all those licenses, alliances, and competition?

Google Blogoscoped has an insightful post titled “How Google Android Routes Around Java Restrictions” which explains a few things.  Here are a few quotes to get you started:

Sun released their “free java” source code under the GPLv2 to both win the free software crowd and capture peripheral innovation and bug fixing from the community. For the java standard edition (aka “the cat is out of the bag”) there is an exception to the GPLv2 that makes it “reciprocal” only for the Java platform code itself but not for the user code running on it (or most people wouldn’t even dare touching it with a pole).
But such exception to the GPLv2 is not there for the mobile edition (aka “where the money is”).
This brilliant move allows Sun to play “free software paladin” on one hand and still enjoy complete control of the licensing and income creation for the Java ME platform on mobile and embedded devices on the other

Dalvik is a virtual machine, just like Java’s or .NET’s.. but it’s Google’s own and they’re making it open source without having to ask permission to anyone

Android uses the syntax of the Java platform (the Java “language”, if you wish, which is enough to make java programmers feel at home and IDEs to support the editing smoothly) and the java SE class library but not the Java bytecode or the Java virtual machine to execute it on the phone (and, note, Android’s implementation of the Java SE class library is, indeed, Apache Harmony’s!)

So, here we are: Apple makes the iPhone, incredibly sweet, slick and game-changing and yet incredibly locked. Google makes Android and not only unlocks development abilities on the mobile phone but also unlocks millions of potential Java mobile programmers from Sun’s grip on it.

This is fascinating stuff.  Even if a bit technical for non-IT audience, still fun to read through…