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.

Read also :

• Weekly Android Applications 12/2/2008
• Weekly Android Applications 5/2/2008
• Android SDK Security Release m5-rc15
• McObject Sharpens its Edge in Database Indexes With New KD-Tree

Highlighted features in this release :

• New user interface - totally remodeled interface, new design and icons, looks much better.
• Layout animations - Developers can now create layout animations for their applications using the capabilities introduced in the android.view.animation package
• Geo-coding - android.location.Geocoder enables developers to forward and reverse geo-code (i.e. translate an address into a coordinate and vice-versa), and also search for businesses.
• New media codecs - The MediaPlayer class has added support for the OGG Vorbis, MIDI, XMF, iMelody, RTTL/RTX, and OTA audio file formats.
• Search Manager - A new search API is now available android.app.SearchManager, providing the ability to to search for user, system or network based data, making search a seamless, system-wide feature.
• Updated Eclipse plug-in - A new version of ADT is available and provides improvements to the Android developer experience. In particular, check out the new Android Manifest editor.

Something very interesting in the new interface is the new menus. Now it is more iphone-like - if I can say - Menus have been iconized which make it easier for touchscreen phones, and we can see the blurred menus by the end, so you can scroll down/up to see more menu options. To dig into the new Android interface here is some screenshots from the new SDK :

Home of the Android Platform

Android dialer

Android Dev Tools

Browser Menu replaced by icons

By clicking on more you get the entire menu

Android New Contact

Android Call Manager

Ready to go ? download the new Android SDK, read M5 announcement on the Developers blog.

Read also :

• Android SDK Security Release m5-rc15
• Android Developer Challenge Deadline Extended
• Second Android SDK Update m3-rc37a
• Look inside Android, Day one

OHM: What do you think about Android Mobile Platform?

Eric Eller, SVP Products and Marketing at Millennial Media

With good reason, there is lots of excitement surrounding any open initiative. It provides increased opportunity for developers to be creative and innovative while taking an active role in the future of consumer applications and services. More mobile applications mean more choices and more compelling content for users, which will lead to higher mobile usage - obviously a positive thing for the industry.

Jason Spero, VP Marketing at Admob :

The launch of the iPhone and the announcement of the Android project are about users. The potential of the mobile ecosystem has been well documented (and well marketed). Many blame the Operators for the perceived lack of progress toward this potential, but a variety of forces have constrained the user experience on the mobile device. These include: device form factor, text entry and capabilities, network speeds and capabilities, billing mechanisms, discovery mechanisms, non-commerce monetization mechanisms, fragmentation of application platforms, fragmentation of browser platforms and more. Each of these needs to be addressed for mobile to achieve its promise. Apple and Google recognize the opportunity and have grown frustrated with the pace at which the obstacles are being address.

Android is a market development effort. Google understands the opportunity for its business model once the mobile internet takes off. Google is now working actively to accelerate that takeoff. Android addresses some (but not all) of the ecosystem needs. In theory, the availability of a robust underlying software platform will reduce fragmentation for application developers, decrease cost and time to market for device manufacturers and spark a new wave of competition in device form factors that will deliver better user experience for mobile data. This will drive use of the mobile internet. In theory. What remains to be seen is how manufacturers will leverage and extend Android to their needs and whether this will undermine the core goal of decreasing fragmentation. But we remain hopeful that Android will deliver on its promise.

AdMob has had a front row seat for the acceleration of the mobile internet in 2006 and 2007. We see dramatic progress against the constraints to mobile web usage.

• Devices are dramatically improved even before the impact of iPhone and Android
• Increases in network speeds have improved the mobile browsing experience
• Simpler data pricing models have made mobile internet more accessible for all
• Content providers have a viable means to monetize their offerings via advertising
• Discovery is being addressed via search, directories and advertising

The launch of the iPhone gave the market a picture of what a mobile data experience could be. This is an example that has catalyzed investment against all of the requirements for mobile data. The iPhone and Android have accelerated something that was already happening.

AdMob is pro mobile internet for all the same reasons that Google is pro mobile internet. AdMob is device agnostic and can benefit from any and all improvements in the mobile web experience. The launch of Android devices in 2008 and beyond will drive increased usage of the mobile internet. Google has said that it will keep separate its market development efforts via Android from its search and AdSense businesses. AdMob believes this ensures fair competition. So AdMob, awaits the arrival of Android devices in the same way we anticipate innovation from Nokia, Motorola, Samsung and others. Improvements in user experience will drive usage, which is all we can ask.

OHM: How could Google Android change the mobile advertising market?

Eric E.: “Google is obviously a major player in online advertising and anything they do in the mobile space will have an impact. What remains to be seen is the nature of that impact. On the one hand, by enabling developers to quickly create new innovative mobile applications, Android could help increase the availability of mobile content that is available for free using the ad-supported model. On the other hand, if developers are compelled to preferentially utilize Google advertising services versus other opportunities in the market, the perception of openness will disappear.”

Jason S.: “The mobile ad market is already growing rapidly.

If Android delivers an improved user experience this will drive usage of the mobile internet. This will further accelerate the growing interest in reaching users on their mobile devices and will motivate more and more content providers to invest in mobile. User experience improvements will drive both supply of and demand for mobile advertising.”

Read also :

• Android SDK Security Release m5-rc15
• McObject Sharpens its Edge in Database Indexes With New KD-Tree
• Interview with Adriano Chiaretta from iambic
• Weekly Android Applications 12/2/2008

NTT DoCoMo is one of leading mobile communications companies worldwide, Headquartered in Tokyo, and is owner of i-mode, the world’s most popular mobile e-mail/Internet service, used by nearly 48 million people.

The company provides already a set of Handsets in collaboration with handset manufacturers such Fujitsu, including : Raku-Raku PHONE Basic, Secure 3G FOMA F903iBSC, 3G FOMA 703i Series, D800iDS and SO903iTV.

According to a new study by Mobile Consumer Behavior, outlining key challenges and success factors for the Open Handset Alliance :

Google’s Android is the first legitimate attempt to re-create the success of Japan’s “Wireless Ecosystem” model within the context and realities of international mobile markets. If successful, Google could spark unprecedented innovations within mobile content, service and application development, yet a number a critical factors stand in the way of such success.

Google is facing a big challenge in the Japanese Mobile Marketing Market first, then to reproduce this wireless ecosystem worldwide. Dr. Philip Sugai, Director of the Mobile Consumer Lab at the International University of Japan and lead author of MCB report, stated :

“Although Symbian and Microsoft have offered the most stinging criticisms of Google’s Android, Google’s next (and most) critical challenge at this early stage of development actually lies in how it will address MontaVista, and galvanize the mobile Linux development movement. Without successfully accomplishing this goal, Android will become obsolete within 2008, never ever leveling a substantial competitive threat against either Symbian or Microsoft.”

Read also :

• ARM To Showcase Android Internet Devices at Mobile World Congress 2008
• Google and UIQ Partnership on Services, not on Android
• Buglabs released BUG, Open Device for Linux mobile
• Today, the first taste of Android

By supporting Android, Tira Wireless partners will be able to convert their applications from JavaME to Android easily. Another porting solution from JavaME to Android is now available after Esmertec and ME4Android. Tira Wireless solution will fit very well for organizations with limited internal development resources or those that require the scalability that Tira Wireless provides.

“Tira Wireless’ move to support Android is in line with our vision to support the major platforms and manage all elements of the mobile content lifecycle, regardless of the device or mobile operator,” said Juan Dewar, CEO of Tira Wireless. “Supporting the Android platform is also a natural extension of the work we have been doing with Java ME applications. Because of our years of experience in this market, we are very well positioned to understand the challenges of developing mobile content in a similar environment, and as a result, can maximize Android’s unique capabilities.”

Tira Wireless customers include Content publishers such Airbone Entertainment, Disney Mobile, Dwango Wireless, I-Play, Warner Bros, Pixiem, THQ Wireless, Dwango Wireless, Hudson Soft, ifone, Jumbuck, Mforma, Mobile Scope, Mobliss, Namco, Sega, SkyZone Entertainment, Sonic Branding Solutions, Sony Pictures Mobile, and Summus; Engineering Services Providers such Babel Media, Mahindra British Telecom, and Absolute Quality; and finally Mobile Operators : Telus, T-Mobile, and Helio.

The GoMobile Edition of the Jump Developer Desktop can be used to commercially deploy a single application on up to 12 handsets. For non-commercial purposes, it is free.

Read also :

• ME4Android, the JavaME Solution for Android
• Android is even better with Esmertec
• Android SDK Security Release m5-rc15
• McObject Sharpens its Edge in Database Indexes With New KD-Tree

While all rumors and breaking news were about HTC to provide the first Android phones, a la mobile confirmed this orientation and got better : the first HTC phone using a complete mobile Linux stack based on Android.

“While mobile Linux has made steady progress in the industry since 2006, Google’s advocacy with the unveiling of the Android framework further substantiates the position of Linux as a major mobile operating system alongside Windows Mobile and Symbian,” said Pauline Lo Alker, President and CEO of a la Mobile, Inc. “However, despite the market enthusiasm about Google Android, many questions remain concerning the technical details, and skepticism exists concerning its readiness. As the leader in mobile Linux, we believe it is our responsibility to take the initiative to allay the ‘mystery’ and dispel any skepticism surrounding Android by first demonstrating a complete mobile Linux system stack, including drivers, middleware, and a suite of Android-based applications running on an existing advanced smartphone manufactured by one of the premier handset vendors in the market.”

It’s true that there are many missing information about Android platform itself until today, but according to a la mobile they are providing a complete mobile stack solution : device drivers, Linux kernel, system utilities, mobile middleware (such as security, device management, provisioning, etc.), an application framework (Android) that supports JAVA services, browser, and miscellaneous applications for the end device.

“Despite the open-source nature of the Android framework, developing a complete mobile system solution with customized, differentiated features continues to present major technical challenges requiring considerable time, effort, and resources — a barrier and reach beyond the scope of many handset vendors,” continues Alker. “Our mission is to remove the complexity for handset vendors and mobile operators to enable them to accelerate their device time-to-market, ensure high quality while reducing total development and device costs. The experience we have gained in putting together this demo will enable us to trim a device’s time-to-market by at least half!”

About A la mobile

Founded in 2005, a la Mobile has already established itself as the leader in developing and delivering one-stop, commercial-grade complete Linux system stacks for mobile devices: integrated, customized, certified, supported and maintained. The Company’s first Linux system offering - Convergent Linux Platform (CLP) version 1.0 - based on the Qt application framework by Trolltech, was first introduced in 2006 and adopted by several handset vendors.

Read also :

• Nokia to Acquire Trolltech for $153M
• The Linux Phone Standards and the Open Handset Alliance

McObject is offering the Android-ready Perst, as well as TestIndex, a demo application showing Perst and Android’s bundled SQLite database performing the same tasks side by side. Both are available as free downloads, with complete source code, from http://www.mcobject.com/android.

With Perst, users of Android-based phones will benefit from responsive, richly-featured embedded software made possible by a database system that delivers high performance and a small footprint, and by the efficiency that results from true Java developer-oriented features.

Perst stores data directly in Java objects. This eliminates the need for data-packing or unpacking code to map between the application’s data model and the database’s data model, as is required by relational and object-relational databases. The Perst API is flexible, easy-to-use and very fast compared to alternative commercial Java OODBMSs.

Perst is a very compact embedded database, with a core consisting of only five thousand lines of code. This small footprint imposes little demand on system resources. Moreover, Perst does not require administration. Perst supports transactions with the ACID (Atomic, Consistent, Isolated and Durable) properties, and expands developers’ coding efficiency by making Java objects as easy to use as possible.

For example, for access to objects, Perst implements 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).

In addition to its core functionality, Perst provides optional features such as garbage collection, detection of hanging references, automatic schema evolution, XML import/export utilities, master-slave replication support (with the option to run read-only queries on slave nodes), an SQL subset to filter elements of any collection, and integration with the AspectJ and JAssist AOP tools.

To read McObject’s complete announcement of Perst and TestIndex for Android, see http://www.mcobject.com/pressroom.php?step=3&article=91.

Read also :

• McObject Sharpens its Edge in Database Indexes With New KD-Tree
• ODMG3 now hosted by ODBMS.ORG
• db4objects Announces db4o Database for Android
• Android SDK Security Release m5-rc15

OHM : Can we know a little about yourself ?

Brendan : I’m a professor of computer science at Union College in Schenectady, NY. I just graduated a year and a half ago from the University of Massachusetts with a PhD in Robotics. Before grad. school, I worked in the software industry for a couple of years; mostly web-apps. I’ve done a bunch of different development over the years.

OHM : So you have a PhD in robotics, and you are interested into mobile development also ?

Brendan : I like to code. My term ended in the middle of November, and I wanted a project to keep me busy.

I had just taught graphics as my fall course and so I thought I’d play around and port some of the code from the class over to Android. Since I’d never done OpenGL on an embedded device, then I was thinking about building an app for the Challenge and I realized it was really annoying to build a GUI in XML. So I wrote the GUI builder.

OHM : Are you entering the challenge alone or in a team ?

Brendan : I’m not sure, probably by myself. I’m not 100% committed to entering. I have to come up with a really good idea, and so far my ideas are only ok.

OHM : So what about Android-GL, are you planning to build something with it ?

Brendan : I was thinking about it, but the renderer still has some bugs in it. While I was working on that I found a reported and number of them and I’ve seen reports from other people as well.

Also, I’m not 100% convinced that 3D plus mobile is the best solution, since most devices still don’t have accelerated graphics

OHM : how did you find coding on Android platform ?

Brendan : Its pretty easy I think. Its very similar to J2SE, more similar than J2ME which I did a little coding for.

There are some major differences between the OpenGL ES API and the regular OpenGL API - no glBegin(…)/glVertex(…)/glEnd() - that took some getting used to, but that’s the direction that the regular OpenGL API is headed also as far as I’ve heard. I think OpenGL 3.0 does away with that style of 3D coding. So it wasn’t a bad thing to learn more about.

OHM : so Java before Android was not much different than after Android ?

Brendan : Yeah, I think so, because I’m not in the mobile industry, and I don’t have a strong sense for the use of Java in that market. So I don’t really know if Android will mark a major shift toward Java or not.

One thing that is interesting about Android is that after two quick SDK releases, its slowed down !

You can tell that there are internal releases being developed, because the release stamp on the bottom of the docs pages keeps changing (Today its: Build m3-rc31 - 04 Dec 2007 17:47). So I’m curious about Google’s SDK release plans/schedule.

OHM : Which feature are you waiting for in the next release ?

Brendan : I’m waiting for Bluetooth support to be activated, So I can drive my Lego NXT Robot from Android !

Thanks Brendan for your time.

Read also :

• Android SDK Security Release m5-rc15
• McObject Sharpens its Edge in Database Indexes With New KD-Tree
• Interview with Adriano Chiaretta from iambic
• Weekly Android Applications 12/2/2008

With Android release, LiPS published an FAQ on the differences between their standardization effort and OHA :

LiPS and Android both seek to reduce fragmentation among Linux-based mobile platforms. LiPS seeks unity through open standards, while Android/OHA does so through shared code.

Effort for Mobile linux stardization isn’t new at all, and beside the LiPS we count also the ELC Mobile Linux Initiative (MLI), Linux Mobile Foundation (LiMo), the embedded linux consortium, and the Gnome embedded initiative. There are also many others individual efforts by companies acting in the linux mobile business. According to ABI research, by 2012 there will be approximately 127 million Linux smartphones shipped each year.

It’s true that OHA and Android are boosted by Google, so should the LiPS profit from Android or should Android learn from the LiPS ?

Read also :

• Synaptics and the Touch Interface Driver for Android
• Android SDK Security Release m5-rc15
• McObject Sharpens its Edge in Database Indexes With New KD-Tree
• Interview with Adriano Chiaretta from iambic

Java programmers are delighted with Android’s full object oriented platform they are frustrated by its bundling with a relational database, requiring cumbersome plumbing between objects and tables. db4o fills the gap by providing a fast and secure, native Java object database that makes storing objects and sharing of data between applications simple and easy.

It’s true that Android came with “Content providers” but as Carl Rosenberger, db4object’s Chief Software Architect, said in a blog post “this is not Java, it’s not object-oriented, it’s not even SQL.” Which is the missing element in Android platform : The object database solution.

This Tuesday we had the chance to talk to Nik Wekwerth, the VP of Marketing db4objects, and he told us about db4o solution for Android and how it could help developers to make fully advanced object oriented applications. “It’s all about simplicity” he told us, “In Java you prefer always to stay in Object Oriented. Object is more flexible than SQL, it doesn’t lock your memory”.

There are currently two applications ported to db4o, the Password Manager application and MapMe. It shows the capabilities of db4o and the simplicity of using objects to store and retrieve data. There is no real benchmark at this time Nik told us, but it’s clear from these two samples that using db4o is much easier and very simple to maintain.

Where can you use db4o ? “If you look at our customers, database usage is very large from planes, high speed trains, photocopiers, research …” Added Nik. DB4o proved its performance in many critical usage and their world class leaders customers like BMW, Boeing, Bosch, IBM, Intel, Ricoh, and Seagate, are certainly enough for Android developers to make sure that they have in hands a high level database solution.

Developers can write software applications that enable the backup of user data to a back-end server or their home PC. A consumer use case could be to start a game on the phone, freeze it, and continue playing at home in the evening. Business use cases include field force automation, data acquisition such as with RFID, and complex navigation systems that use locally cached geodata.

Db4o is open source under GPL, you can get started by downloading db4o for Android and start porting your current relational application, or start your new project in a fully object oriented environnement.

Read also :

• ODMG3 now hosted by ODBMS.ORG
• McObject Sharpens its Edge in Database Indexes With New KD-Tree
• McObject, Object-Oriented Embedded Database for Android
• Tips: Howto Connect Android Emulator behind proxy