Google Android and Local: Built-In!

As most of you must know by now, Google announced their Android open mobile development platform last week. At the time, the big question I had was “given the major possibilities around local and mobile, will the platform be built with that opportunity in mind?”

After digging a bit in the documentation and reading some of the comments in the blogosphere, I’m happy to see that the platform is definitely engineered with location-based services (LBS) in mind.

Ed Parsons, Google’s Geospatial Technologist, has a short analysis on his blog:

For me and my interest in geographic information the key detail about the Android SDK is the LBS component, and where is appears in the whole android stack. I have often argued that LBS would only really make sense as an underlining infrastructure that is available to all applications, therefore allowing much higher levels of integration. (…) With Android the Location Manager component is part of the core application framework, meaning that all user applications have access to the devices location.

android_LBS

Update: my friend Martin takes a deeper technical look.

What it means: any application will be able to “ping” the mobile device to retrieve the user’s location. This creates an opportunity to build very compelling local search applications. Given the association with the Open Handset Alliance, I think we can safely assume some handset manufacturers and wireless providers will adopt that new platform (most notably HTC, Motorola, Samsung, T-Mobile, and Sprint/Nextel) but I wouldn’t hold my breath for short term opportunities. We’re still talking about a product that will be deployed in the market in 6-18 months. Put this one on your radar screen but do not engage resources too quickly.

2 thoughts on “Google Android and Local: Built-In!

  1. Hey Seb:

    We will have to see how this compares to the currently available JSR 179: Location API for J2ME: “An Optional Package that enables developers to write mobile location-based applications for resource-limited devices.” which has been around for some time.

    And I think you said it correctly that this is still a little bit out there. But the best way to leverage this would be to have this API leverage something similar to what SkyHook is providing with his association with SiRF Holdings (WIFI and GPS location determination).

    L8er – Martin

  2. Hey Seb:

    We will have to see how this compares to the currently available JSR 179: Location API for J2ME: “An Optional Package that enables developers to write mobile location-based applications for resource-limited devices.” which has been around for some time.

    And I think you said it correctly that this is still a little bit out there. But the best way to leverage this would be to have this API leverage something similar to what SkyHook is providing with his association with SiRF Holdings (WIFI and GPS location determination).

    L8er – Martin

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s