McObject has added support for the KD-Tree, a database index with uses in spatial and pattern-matching applications, to its Perst open source, object-oriented embedded database system available for the Android mobile development platform.

The new k-dimensional tree or KD-Tree index adds a structure in Perst that stores and manipulates point objects in a k-dimensional space by partitioning that space. Practical uses include computer graphics, geographical information systems and biometric applications such as fingerprint matching. In addition to their efficiency in handling multi-dimensional data, KD-trees are useful in “normal” applications in which query predicates contain various combinations of object fields. For example, KD-Trees are used to construct Query-By-Example (QBE) features in which the user selects fields and values, and the application builds database queries based on these selections.

While many Java databases offer limited index support, Perst implements rich options for data access, including specialized collection classes optimized for different data layouts and access patterns, including:

• Classic B-Tree implementation;
• R-tree indexes for spatially-oriented applications such as GIS and navigation;
• Main-memory database containers, based on T-Tree indexes, optimized for real-time memory-only access;
• Patricia Trie index, which speeds searches in networking and telephony applications;
• TimeSeries class to efficiently deal with small fixed-size objects;
• Specialized versions of collections for thick indices (indices with many duplicates), and bit indices (keys with a restricted number of possible values);
• KD-Tree indexes

For McObject’s announcement of KD-Tree support see http://www.mcobject.com/pressroom.php?step=3&article=93.

For general information about Perst for Android, including links to the open source, complete Perst database source code, and to McObject’s Android-ready TestIndex database benchmark, go to http://www.mcobject.com/android/.

Popularity: 84%

Iambic is one of the already established mobile software companies that started developping for the Android platform. You have probably met with one of their Android applications GoogHelper or Tipper that we announced in previous posts . Adriano Chiaretta - Chief Operating and Information Officer at Iambic - accepted to answer our questions and share their development experience with Google Android.

Q1 : We have introduced iambic in the last weeks to OHM readers with GoogHelper and Tipper, What can we know more about the company ?

iambic was founded at the end of 1993. At the time, the company had two people developing solutions for one of the very first PDAs, the Apple Newton. Making it easy to do time and expense tracking while on the go was the primary focus. Later in 1994 the company expanded its area of focus to include personal information management (PIM). As a result, Action Names was born. Through the years, that application evolved to what is now Agendus, currently available for Palm OS, Windows Mobile, Symbian, as well as Windows desktop PCs.

During the last few years, we expanded our portfolio of Windows Mobile applications — with the development of titles that had a broader reach in areas that include: personal productivity, including vehicle managers, health and diet applications, and call management and action taking. In a nutshell, our mission is to empower users to make the most out of their time wherever they are –on the go or at the desk–, through the creation of easy-to-use, yet powerfully customizable solutions.

Q2 : Why the interest to create applications for the Android platform ?

Since the announcement of the new Android mobile OS and related SDK, we have been intrigued by what it promises to deliver at a variety of levels. From a development standpoint, being able to access any tiny detail of the platform without having to jump through hoops is a great time saver, and also saves from countless “back and forths” with device manufacturers for updated handset specific SDKs.

Having the ability to closely interact with the built-in applications and related data storages (love Sqlite and I’m glad it’s the storage engine of choice of Android) is another definite plus. This without forgetting the new operating system is backed by a rather consistent number of prominent companies, leaders in their industry and market specific area. All this, of course, so far on “paper” or “bits” if you want in the form of a quickly evolving SDK, and slick emulator. Will the promises I mentioned above become reality when the first handsets hit the market? I truly hope so.

Q3 : How many developers are currently working on Android projects ? Did you hire or is it from the current dev team?

We have a developer fully dedicated to Android projects, from the current development team, while another one is playing with the SDK “just for fun” — creating small tools so to speak. I’m getting my hands dirty too. I’ve been checking out examples, documentation, and thinking about what else we can creatively use out of what made available through the SDK.

Q4 : Are you just porting current iambic mobile projects to Android or planning new ones also ?

So far, in order to start getting our “feet wet,” we ported a few titles while exploring the possibility of the platform, along with the expected rough edges of the SDK.

Q5 : Any commercial application for Android in your plans ?

We do plan to release commercial solutions for Android. GoogHelper and Tipper themselves might get revised and “enriched” to become commercially distributable.

Q6 : Will any of your iambic projects will take part of the Challenge ?

Yes, we are currently working on a project we plan to submit to the Developer Challenge.

Q7 : How do you compare development under Android to other mobile platforms ?

So far we are finding the development for Android a much more streamlined experience compared to other platforms. I believe this is because the operating system is young (there are no phones based on it yet), and therefore getting up and running with the development environment is extremely quick and straightforward. Unzipping the latest Eclipse, the Android SDK, getting the Android plug-in setup in Eclipse and being off stepping through a few breakpoints while debugging the app on the emulator took less than 15 minutes. On mature mobile platforms such as Palm OS, Windows Mobile, Symbian, or BlackBerry the process of installing a development environment, main SDK, various licensees’ customizations, etc. can easily take half day.

That said, the SDK itself is clearly a work in progress. Its documentation is sort of “hit and miss” at the moment and definitely not super clear. And a few of the API calls are not working as expected. Then again, this is the type of stuff I’ve seen in SDKs that are much more mature, so no real news there. It often comes down to looking around forums and message boards for solutions, and spicing up the approach with some trial & error.

The latest SDK released just a few days ago is quite a step forward, although it introduces a variety of changes both from an API/development standpoint as well as from a user interaction / usage model standpoint. The latter according to what the UI showcased by the emulator is telling us. We are investing quite some time now getting the projects we are currently developing up to speed with the latest SDK. Hopefully we won’t see a similar rather deep change in the coming updates.

Popularity: 90%

After the first Android Campfire at the Googleplex, tow other international Android Code Days have been lined up. The first one on January 31st in London and Tel Aviv; and the second one in Boston, Massachusetts on February 23th. A similar event will be held in Munich, Germany during the Mobile Monday Germany on January 29th.

What’s a Code Day, you ask? Well, it’s just our name for a day-long introduction and immersion session for Android. We’ll give a technical introduction to the platform as well as a more in-depth look into topics of interest to the attendees. Then we’ll have a free-for-all coding session that we like to call the “Laptop Lounge”.

Two from the Google Android team will assist the Android Code Days “Jason Chen and I will be doing those Code Day events.” Dan Morill confirmed to OHM in email.

We are not sure if other intenational Android Code Days will be held by Google in other places, so probably the community can organize separately more Android Code Days. Meeting other Android developers will be great not only to exchange ideas and knowledge, but also to find partners for the challenge. Remember that last submission date is getting closer, March 3rd, 2008 !

Popularity: 26%

While Android aims to be an Open Platform for mobile handsets, it remain closed at different levels, even for bug reporting ! After SDK launch many developers started reporting bugs in the discussion group, which is not really useful. Android team were tracking issues internally, but it’s also very interesting for developers to know different issues. Today the issues list finally goes live and everyone is able to report bugs, and we started believing that it was an open source project. The next Android SDK release is going to be BIG according to Dan :

We’ve been improving that “early look” and are preparing for the next big SDK release, so it’s time to take the whole thing up a notch. As we move toward the first handsets, it’s time to formalize the process, and the first step in that is to enable an issue tracker for developers to submit feedback.

Issue Tracker is available at this address : http://code.google.com/p/android/issues/list, everyone is welcomed to submit any issues encountered with Android SDK, but always be sure to check if the issue have not been submitted before by someone else.

Popularity: 22%

As it was previously announced by Dan Morrill at the Android Developers Blog, next Thursday January 23rd, 2008 will be held the first Android Campfire at the Googleplex. A unique event, especially for Android developers to be updated on the latest Android News, and find answers for all their unanswered questions.

The evening will feature an update on Android’s latest news and an open forum for you to ask questions, discuss your application ideas, and to connect with other Android enthusiasts.

A very unique occasion to meet Android team, about one month before closing submission for the Android Challenge. There is a registration page for this Campfire if you are attending the event. Otherwise Google is preparing an international event and an Android World tour, so just hope that next camping will be close to your place.

Our developers will be a huge part of Android’s success, so we want to meet you, our colleagues. We’re working on some events around the world that we hope to announce soon, but to kick things off, on the 23rd of January we’ll be holding a Campfire about Android.

Popularity: 24%