The Android Value Prop – live from Google I/O

This is a short excerpt of the value proposition of Android, as presented by Jason Chen at the "Introduction to Android" break-out session at Google I/O.

For the User:

The user “controls” the experience. Users will chose what applications to use, versus what is shoved down their throats by OEM’s and operators

For Developers:

1) Developers will be able to ship applications at will

2) All API’s are exposed

3) Integration/extension and even replacement into and of existing components:
- Integration across various applications
- Extending = customization of default applications
- Replacement = end-users could wind up replacing default applications for new cool apps developed by the community

My personal dilemmas with Android:

1) According to the presenter, discovery and distribution is left up to the community. This is nothing new to the mobile space. The problem is that operators not only want to, but NEED to control the distribution of applications. After all, it is they who issue the phone bill at the end of the month; it is they who have to answer customer calls and issue refunds to disgruntled end-users.

2) There doesn't seem to be much of a strategy around discovery of applications that are downloaded to device. After downloading an application it will reside in a subfolder that is accessible through the home UI. This is not different from today's semi-open platforms. Perhaps the Android marketing team has something in the works.

3) Hardware won’t be available to developers until 1st devices are shipped (1st handsets will ship during the 2nd half of 2008) – It seems that unless an application wins the Developer Challenge, there's little likelihood it would ship at the same time the device does. After all, applications should really be tested and re-tested on the physical device before being shipped.

4) Security questions were not thoroughly addressed during the session. I have confidence that Android is really paying attention to this, however.

Another question that did not come up but that keeps bugging me:

5) Who will address customer care once the applications ship? Operators? If so, does Google really expect operators to allow exposure of all APIs and for applications to simply ship without going through thorough certification operator-controlled processes?

Conclusion

Android will be a very sexy platform with great toolkits for developers. Graphics will be superior, guaranteeing applications to be equally sexy. Enticing API’s will be exposed (keep in mind that other mobile platforms already expose many of these API's). However, Android needs a solution to what I see as the key problem with existing platforms: discovery before and after download of applications. Also, at least in the short term, Android does aggravate the problem of fragmentation that developers face in mobile today.

I am hopeful that as these discussions with the community continue to take place Android will uncover more execution issues and work to resolve them.

Short follow up on Ribbit

I just thought I would do a quick post on what "Randy" from Ribbit shared in his comment to my post: to get more info on Ribbit, check out their blog or their RSS feed.

Good nite!

Android ditched for LiMo by Verizon… for Now

The Google versus evil carrier saga continues. Verizon Wireless announced today that it has joined the LiMo Foundation.

LiMo is an alliance that aims to create an open handset operating system based on Linux for Mobile. To date they not only have attracted 40 big industry names, but they have also launched a number of handsets:

• MOTO U9, MOTO Z6w, MOTOROKR Z6, RAZR2 V8, RAZR2 V8 Luxury Edition and MOTOROKR E8 from Motorola;

• NTT DoCoMo FOMA N905i, FOMA N905iμ, FOMA N705i and FOMA N705iμ from NEC;

• NTT DoCoMo FOMA P905i, FOMA P905iTV, FOMA P705i and FOMA P705iμ from Panasonic Mobile Communications, and

• SGH-i800 from Samsung.

(Source: http://www.limofoundation.org/)

While Verizon may not necessarily limit its support to LiMo, today’s move represents a blow for Android. It will be much more difficult to secure a significant footprint on mobile devices.

One thing that Google still has going for itself is the traction it has gained among developers (almost 1,800 Android Developer Challenge submissions). The only problem with this is that in the short term developers will gravitate to the fad of the moment. In the long term, however, it is those platforms that make the most economic sense that will result the winners.

All in all the jury is still out. The truth is there is plenty of room for all players. But as an important reminder… with fragmentation (and this seems to be getting worse instead of better), it is the developers who suffer in the process… and the ultimately loser is the consumer…

More Strides towards Openness: Funambol

Funambol offers open source email, contacts and calendars. It provides connectors between Microsoft Exchange and IBM Domino email servers, and a range of mobile devices. It also provides an open community for other open source and standard solutions that service providers and mobile device manufacturers can benefit from.

So one might ask what the value prop of Funambol is when Android promises to be the answer to mobile open source. The answer is that Android is a software stack, while Funambol is a platform. Therefore, they are very complementary to eachother.

Take the following example:

As a potential consumer of Funambol I have already found a problem using its consumer service. As usual, the problem is porting. My phone, being one of the most popular phones, the LG chocolate, is not supported by Funambol. Also, in my case, Funambol assumes Verizon’s phones are open. When I tried to set up my account Funambol gave me clear instructions on how to tweak my phone settings to synchronize with Funambol’s server. The problem is Verizon does not allow for that because they either want me to pay for the sync application on a smartphone, or to download and pay for a Brew email client on my feature device.

The bottom line is that this problem makes for a stronger case for Android and the power it has to forge relationships with operators and OEM’s, and lowering the porting barriers.

If unlike me, you do have access to an open device and furthermore, to an outlook server here are some quick easy resources to help you through the steps: setting up Outlook and Blackberry.

One Small Step for Verizon, One Big Step for Mankind

Mark your calendars! March 19-20 is Verizon’s Open Development conference.

But what does this mean exactly? If you are an application developer, don’t book your flight to NYC just yet. For starters, the conference is not for all developers.

The first step towards enabling an open platform environment is getting device manufacturers on board and in sync with each other. This explains why the first conference targets device developers. During the conference Verizon will review its technical device standards. The question is are these “standards” standard with respect to the rest of the devices in the world?

On a side note: another, perhaps even bigger announcement is the “company’s desire to encourage innovation, give customers wireless choices, and quickly address opportunities to expand the wireless market”. I just love the sound of that!

Related posts: GigaOm, mobilebuzz