I’ve said it a before: good mobile 2.0 services requires good web services in the back. Well, Google is building one heck of a backbone of services to complement their upcoming phones (or phone OS). Interesting to see what they come up with in the end.

Anyway, congratulations to Jyri and the rest of the Jaiku team!

Updated: Techcrunch UK has more.

Tim O’Reilly has a good overview of Jaiku here. This sentence sums up why this is related to the GPhone:

This is the way a phone address book ought to work. I continue to think that the address book is one of the great untapped Web 2.0 opportunities, and that the phone, even more than email and IM, and certainly more than an outside-in, invitation-driven “social networking application” represents my real social network.

My own company, GlocalReach, will solve a slightly different problem in another circle of intimacy but the address book in the phone is definitely one of the untapped goldmines of social networking. The established manufacturers are fumbling with more or less closed and slow moving solutions like Wireless Village that no one uses.

Jaiku was founded in February 2006 and Twitter the month after. Wireless Village has been in standardization groups for years. Google, on the other hand, is an acquisition machine not wasting time eating salmon sandwiches in standardization meetings (believe me, I’ve been to them) but in stead letting innovation happen outside the company and pick the right time to devour integrate it.

I bet there are at least five times as many people working with acquisitions than with standardization at Google. I also bet there are fifty times as many people working with standardization than acquisitions at companies like Nokia, Sony Ericsson or Motorola.

Should they change? I don’t know. The telecom way of standardizing everything is not a winning strategy if you want to be innovative. It might be good for a lot of other stuff, like building huge wireless networks or come up with platforms that other can innovate on, but not for innovation.

It boils down to the question: what kind of company do you want to be? The innovative kind or the standardizing kind? The application or the platform? If you’re a successful application, you’re going to end up becoming the platform anyway so I’d say the choice is easy. Just ask Microsoft.