LeWeb08-Google's Mayer tips Local Search as key opportunity for 2009

PARIS-Marissa Mayer, VP of Search Product & User Experience at Google, gave an insightful view on various challenges facing both Google and its competitors in terms of Search.

Marissa pointed out that there is still some way to go to improve search (harking back to a previous interview she had given where she had stated that 90% of the work on search has been completed but that the last 10% was the tricky part).

One area where Google is looking to improve its game is in personalised search, with the recent launch of the Google Search Wiki seeking to test the waters in this area.

Another area, is search through devices other than the PC, notably through a mobile phone and, linked to this,voice-activated search.

Loic le Meur asked Marissa whether she thought any improvements in video search were in the pipeline. She answered that improvements are imminent in detecting voice within video and searching on this. However, graphic recognition (e.g.of a face in a video) is still a few years away partly due to YouTube's success and the proliferation of video content on the web.

Finally, and critically for companies in the LBS space, Marissa stated that "local search is one of the big opportunities in 2009".

LeWeb 08 Paris-Prologue and Photos

PARIS-LeWeb08 managed to pull off a great event in a time of economic uncertainty, and despite the heavy atmosphere associated with the global financial system, it offered rays of hope as well as advice on how to weather the storm.

Many industry heavy hitters, from Marissa Mayer at Google to Marc Simoncini of Meetic, Maurice Levy of Publicis and Martin Varsavsky, serial entrepreneur, gave their take on future plans and opportunities in the market.

Marc Simoncini gave a very entertaining talk on different dating habits he had to consider when launching his service in different countries in Europe.
For example, in Italy, women were not overt in their dating habits as they normally 'had to ask permission from their brother to date' while in Sweden, the Meetic offer of free membership for women was met with a 'why should it be free for us' reaction.

New Resources for Developers

We're back in action after a Thanksgiving break filled with turkey, stuffing, and pumpkin pie. Now it's the holiday season (at least, here in the U.S.) and we're filled with good will toward developers. Today I wanted to talk about a couple things we just finished polishing up.

First, the Android 1.0 SDK, release 2 is now available. Like the previous 1.0_r1 release, this new 1.0_r2 build creates applications that are compatible with Android 1.0 devices, such as the T-Mobile G1. This new release fixes a few bugs. In 1.0_r1, it was possible for developers to write technically-illegal code by using the Java Reflection APIs to access private or protected fields and methods. 1.0_r2 fixes that problem by enforcing private/protected visibility of items accessed via Reflection. Meanwhile, the class android.R.styleable was included in 1.0_r1 primarily for documentation purposes as a way for developers to look up the style attributes available to them to use. However, actually referring to that class via source code would result in applications that might break when run on future versions of the Android platform, so 1.0_r2 corrects the oversight and removes access to the class from the android.jar file. (The class remains in the documentation for reference purposes, though.)

Both of these problems are obscure "future-proofing" issues, and I'd be quite surprised if they actually caused problems for anyone, but now they're fixed. 1.0_r2 also includes a few other smaller changes; check out the release notes for all the details.

Second, many of you have asked if developer devices will be available. We've worked with our partners to create a program for developers to purchase devices that enable them to test and debug applications more easily.

I think these new tools will be quite helpful to developers, and I'm looking forward to seeing what people do with Android, next.

New Nokia N97..but not for Christmas

Nokia used the opportunity of the Nokia World Event in Barcelona on Tuesday 2nd December to announce the release of the much anticipated N97 -the second touchscreen phone by the manufacturer, but this time, unlike the XpressMusic, it comes with an inbuilt QWERTY keyboard. It also has sufficient new features to pack a punch and looks set to carve out its own cult following.

The N97 features integrated A-GPS sensors and an electronic compass, which the vendor says will make it easy to update social networks automatically with real-time information, giving approved friends the ability to update their status and share their 'social location' as well as related pictures or videos. The device supports up to 48GB of storage, including 32GB of on-board memory, expandable with a 16GB microSD card.

Sadly for Nokia-philes, the N97 is only expected to begin shipping in the first half of 2009 (at an estimated retail price of €550 before taxes) at which point demand is anticipated to have built up dramatically.

Touch Mode

Designing and developing user interfaces for Android is very different from doing so in a regular desktop environment. Because Android runs applications on mobile devices, application designers and developers must deal with numerous constraints that are not always obvious. To help you design and develop better applications, we are publishing a new series of posts focusing on Android user interfaces. In this series, we will give you design guides and tools, development tips, and explain the fundamental principles of the Android UI toolkit. The goal here is simple: we want to help you design and develop a great user experience. To start off this series, I'd like to introduce touch mode, one of the most important principles of the UI toolkit.

The touch mode is a state of the view hierarchy that depends solely on the user interaction with the phone. By itself, the touch mode is something very easy to understand as it simply indicates whether the last user interaction was performed with the touch screen. For example, if you are using a G1 phone, selecting a widget with the trackball will take you out of touch mode; however, if you touch a button on the screen with your finger, you will enter touch mode. When the user is not in touch mode, we talk about the trackball mode, navigation mode or keyboard navigation, so do not be surprised if you encounter these terms. Finally, there is only one API directly related to touch mode, View.isInTouchMode().

Sounds easy enough right? Oddly enough, touch mode is deceivingly simple and the consequences of entering touch mode are far greater than you might think. Let's look at some of the reasons why.

Touch Mode, Selection, and Focus

Designing a UI toolkit for mobile devices is difficult because of the various interaction mechanisms they provide. Some devices offer only 12 keys, some have a touch screen, some require a stylus, some have both a touch screen and a keyboard. In that regard, it is a great benefit for the Android development community that the first commercially available device, the G1, offers multiple forms of input using a touch screen, a trackball, and a keyboard. Because the user can interact with applications using three different mechanisms, we had to think very hard about all the possible issues that could arise. One issue led us to create the touch mode.

Imagine a simple application, ApiDemos for example, that shows a list of text items. The user can freely navigate through the list using the trackball and they can also scroll and fling the list using their finger. The issue in this scenario is the selection. If I select an item at the top of the list and then fling the list towards the bottom, what should happen to the selection? Should it remain on the item and scroll off the screen? In this case, what would happen if I then decide to move the selection with the trackball? Or worse, if I press the trackball to act upon the currently selected item, which is not shown on screen anymore. After careful considerations, we decided to remove the selection altogether.

In touch mode, there is no focus and no selection. Any selected item in a list of in a grid becomes unselected as soon as the user enters touch mode. Similarly, any focused widgets become unfocused when the user enters touch mode. The image below illustrates what happens when the user touches a list after selecting an item with the trackball.

To make things more natural for the user, the framework knows how to resurrect the selection/focus whenever the user leaves touch mode. For instance, in the example above, if the user were to use the trackball again, the selection would reappear on the previously-selected item. This is why some developers are confused when they create a custom view and start receiving key events only after moving the trackball once: their application is in touch mode, and they need to use the trackball to exit touch mode and resurrect the focus.

The relationship between touch mode, selection, and focus means you must not rely on selection and/or focus to exist in your application. A very common problem with new Android developers is to rely on ListView.getSelectedItemPosition(). In touch mode, this method will return INVALID_POSITION. You should instead use click listeners or the choice mode.

Focusable in Touch Mode

Now that you know focus doesn't exist in touch mode, I must explain that it's not entirely true. Focus can exist in touch mode but in a very special way we call focusable in touch mode. This special mode was created for widgets that receive text input, like EditText or, when filtering is enabled, ListView. This is why the user can type text inside a text field without first selecting it with the trackball or their finger. When a user touches the screen, the application will enter touch mode if it wasn't in touch mode already.  What happens during the transition to touch mode depends on what the user touched, and what currently has focus.  If the user touches a widget that is focusable in touch mode, that widget will receive focus.  Otherwise, any currently focused widget will not retain focus unless it is focusable in touch mode. For instance, in the picture below, when the user touches the screen, the input text field receives the focus.

Focusable in touch mode is a property that you can set yourself either from code or XML. However, it should be used sparingly and only in very specific situations as it breaks consistency with Android normal behavior. A game is a good example of an application that can make good use of the focusable in touch mode property. MapView, if used in fullscreen as in Google Maps, is another good example of where you can use focusable in touch mode correctly.

Below is another example of a focusable in touch mode widget. When the user taps an AutoCompleteTextView's suggestion with his finger, the focus remains on the input text field:

New Android developers often think that focusable in touch mode is the solution they need to "fix" the problem of disappearing selection/focus. We really encourage you to think very hard before using it. If used incorrectly, it can make your application behave differently from the rest of the system and simply throw off the user's habits. The Android framework contains all the tools you need to handle user interactions without using "focusable in touch mode". For example, instead of trying to make ListView always keep its selection, simply use the appropriate choice mode. And if you feel that the framework does not suit all your need, feel free to let us know or contribute a patch.

Touch Mode Cheat Sheet

Do:

• Remain consistent with the core applications
• Use the appropriate feature if you need persistent selection (radio button, check box, ListView's choice mode, etc.)
• Use focusable in touch mode if you write a game

Don't:

• Do not try to keep the focus or selection in touch mode

Behind the apps: Amazed

This week's developer video features Jason Tomlinson of Hands-On Mobile. He wrote Amazed, an application open sourced in the apps-for-android project. Things Jason mentions in the videos include:

• Amazed was built primarily to get familiar with the accelerometer. This helped him in his work on Guitar Hero® World Tour Mobile for Android.
• Using traceview to track down which methods take the most CPU cycles.

This and other Android developer videos can be found here.

ESA -Technology Transfer Programme and LBSs

BARCELONA -Framed by the spendid view from the 20th floor of the Mapfre Tower, Bruno Naulais, European Space Incubators Network Manager at ESA, explained some of the current initiatives of the ESA with potential for tech start-ups.

The new Galileo satellite will offer better resolution than GPS, precise timing via an atomic clock and a guaranteed signal (a boon indeed for LBS companies given occasional unreliability of GPS signals on mobile devices).

Bruno also covered other alternatives to GPS.Consisting of three geostationary satellites and a network of ground stations, EGNOS achieves its aim by transmitting a signal containing information on the reliability and accuracy of the positioning signals sent out by the US Global Positioning System (GPS) and the Russian Global Orbiting Navigation Satellite System (GLONASS). It allows users in Europe and beyond to determine their position to within 2 metres, compared with about 20 metres for GPS and GLONASS alone.

In addition, new boosters are being developed as part of the ESA Technology Transfer Programme that will allow indoor usage of GPS, thus providing realtime navigation guidance at large scale indoor events (trade fairs).

A new centre for Innovation in Geospatial and Location Based Services is also being set up by ESA together with Oracle and TeleAtlas.

The ESA VC Fund Initiative is providing finance of up to €1.3m for innovative start-ups and they are seeing the key dealflow in the area of Location based products and services.

More info can be found at www.esa.int/ttp

KoreaComm 2008-PhotoBlog

ESA Living Labs-Mobile Lessons from Space

When it comes to exploring the frontiers, both geographical and cognitive, space agencies are difficult to beat. Many inventions originally conceived for space missions (one example amongst many, lithium ion batteries) have found their way into the consumer mainstream.

It therefore makes perfect sense to attempt to harness the know-how capability of space science for the benefit of the world of communications and related technologies.

Living Labs Global, together with the European Space Incubators Network of the European Space Agency, ESA, run by Bruno Naulais, and Barcelona's 22@ Initiative have organised a half-day event on the 19th November in Barcelona to explore how best to leverage space innovation within the start-up environment.

The event is limited to 50 participants so getting a seat may be a challenge. If you are keen to attend though, you can give it a try by following the title link. Otherwise, I will be reporting back on the event on this blog and provide highlights on the key points.

Location Mobile Trends for 2009 LBSs

The Location Based Service (LBS) sector of Value Added Services (VAS) on mobile is evolving.

I see 3 key trends and a similiar number of challenges for the year ahead for companies within the expanding LBS ecosystem:

TRENDS:

1. COMPETITION

There is little doubt that this sector is heating up, with both the iPhone and the Android platforms spawning a plethora of applications. And the global start-up map for LBS indicates that new ventures are emerging outside of traditional hotbeds like the US and Western Europe. This means that differentiation is becoming key. Start-ups with the big budgets can choose to differentiate via advertising (though this is becoming unviable-see point 3 of Challenges below) while smaller companies need to think smart and go for whatever niche they think offers the best returns.

2. PREMIUM CHARGING

It is apparent that consumers are ready to pay a premium for some LBS services, though this is on a more pay-per-use model than a subscription model. Quick and easy services that everyone can understand and that add immediate value (place me on a map now and show me Points of Interest around me) can be charged successfully and it is looking increasingly likely that pedestrian navigation-type services will also meet with success.

3. CONVERGENCE

Convergence spans a wide spectrum of meaning. In terms of LBSs, it means that traditional LBS services are moving into the Portable Navigation Device (PND) space, and that the reverse is also happening. It also means that connected devices like the Playstation Portable (PSP) are also moving into the LBS space with the likelihood of new devices entering the market (including the rumoured launch of the National Geographic Explorer Device).The LBS landscape is liable to some tectonic shifts in the coming year.


The LBS sector has consistently offered some of the greatest opportunities but also some of the greatest challenges in mobile, some that I would highlight today are as follows:

CHALLENGES

1. OPERATOR RESTRICTIONS

Fortunately for the mobile ecosystem, walled gardens are crumbling and we are seeing what I have previously defined as 'Open Playgrounds' being created. This doesn't stop Mobile Network Operators (MNOs) from imposing limitations on accessing their location platforms. No MNO currently offers anything other than 'pull' mechanisms for location detection (the user has to request to be located) while it is the 'push' mechanisms (tell me automatically where I am and push relevant info to me) that would yield the greatest benefits to the user.

2. SEAMLESS LOCATION DETECTION

Locator technologies are in themselves converging as the need to deliver a seamless location detection service to the mobile user becomes more of an imperative. 2009 will see an acceleration of this trend and successful apps will be able to switch automatically from a GPS to a Wi-Fi to a CellID environment according to the criteria that deliver the best experience to the user (this could be related to location, so delivering Wi-Fi location indoors or battery life, switching to CellID to reduce battery exhaustion).

3. MONETISATION

The monetisation model for LBSs has not been proven.But it will. And even if it takes time, let's not forget how long it has taken YouTube to adopt a clear monetisation mechanism (it announced today that it will offer sponsored video search, 3 years after launch). However, there is a tiresome task pending for LBSs to continue educating brands and advertisers of the potential effectiveness of LBS advertising (particularly that which links place with context). However, we live in a period of retrenchment-MNOS are retreating in their shells and curtailing infrastructure spend. Some, but not all, advertisers are cutting back on mobile and retreating to less effective media like TV.

Now is the time for LBS start-ups to redraw the lines of their monetisation models-to squeeze out revenues where they can be squeezed and cut costs in other areas. Highly funded start-ups with high burn rates will need to adapt more to the new low cost environment. The opportunities for small start-ups with smart monetisation ideas will peak next year-but their emphasis will have to be on easily addressing the true needs of the mobile user, requiring an understanding of the likely behaviour of this user in the new economic environment.

AT&T Acquires Wayport to add to Wi-Fi capabilities

AT&T Inc. announced yesterday that it had agreed, through one of its subsidiaries, to acquire privately-held Wayport, Inc., a leading provider of managed Wi-Fi services in the United States, for approximately $275 million in cash. The deal adds Wayport's focused capabilities and enterprise customer portfolio with AT&T's leading Internet Protocol (IP) and 3G networks, and broad consumer and business customer bases, to deliver enhanced broadband connectivity at home, in the office, on the road, and virtually anywhere in between.

The acquisition expands the AT&T Wi-Fi^SM footprint to nearly 20,000 domestic hotspots, takes the company's global Wi-Fi presence to more than 80,000 locations^*, and creates thousands of new ways for customers worldwide to stay in touch. Millions of AT&T customers — plus millions of other consumers needing to connect on the go — will benefit from access to new hotspot locations served by Wayport.

AT&T's global brand, marketing leadership and extensive enterprise sales force will complement Wayport's expertise in enabling and managing applications over an integrated network. Wayport will also extend AT&T's reach in the hospitality, health care, education and retail sectors.

"We're seeing exponential growth of Wi-Fi-enabled devices — such as smartphones — combined with a continued dependency on 24/7, anytime, anywhere Internet access across business and consumer market segments," said John Stankey, president and CEO, AT&T Operations. "Now is the right time for AT&T to affirm our commitment to Wi-Fi leadership. By acquiring Wayport, we're giving consumers more ways to stay in touch and building a more robust network management solution for businesses. We're bringing ready access to the nation's leading Wi-Fi, wireless and IP networks — on a global scale."

Behind the apps: Amazon and imeem

Last week we introduced a couple Android developers who shared how they built their Android apps and gave their insight into Android app development. This week, we have videos of two developers who've built music-related apps.

The first is of Allan Hsu—he wrote imeem's Android app. A couple of things he mentions in his videos:

• Using SQLite databases and regular expressions
• Completing the app, including rewriting many of their Activities and web service API calls, in just 6 weeks.

The second video features Casey Langen—he wrote the Amazon MP3 for Android app. Things he mentions in the videos include:

• Using Apache HTTPClient to download data from their servers. Also used ListView in all activities and the MediaPlayer for song previews.
• Developers new to Android should get familiar with ViewGroups and how they're implemented.

Check out other Android developer videos here: Android App Developers.

Le Web 08 Conference, Paris-Exclusive Reader Discount

PARIS-Once again, Le Web 3.0 (now re-branded Le Web '08) is upon us, and over 1800 participants are expected to converge on Paris for the 2 day event on the 9th and 10th of December.

Paulo Coelho, now popular amongst digital media events, will bless the conference with his insights along with MySpace CEO Chris DeWolfe, Mark Simoncino of Meetic , Michael Arrington of TechCrunch and many more..This year's theme for the event is 'Love' and, going along with this theme, as I love my blog readers, each and everyone of you can claim a 20% discount.

Just link through from the title of this post to the Event Website and you can get your ticket for €1196 instead of €1495 if you book by November 20th.

Don't miss out!

Mobile Services in Korea-an eyewitness report

SEOUL-As you would expect, things are a little different in Korea compared to, say, Europe...Research reports are all fine and well, but they fail to give that 'finger-on-the-pulse' feel for what is happening on the street.

So, having spent a week in Korea (and considering that this is one of the most advanced countries in terms of mobile communications) I thought I would share some brief impressions of mobile usage in the region.

Firstly, I'd like to dispel the myth that everyone uses the sort of high end LG or Samsung models widely publicised in Europe...while Koreans have a very high penetration of 3G handsets, many of the ones I saw were Anycall handsets, a Samsung local brand or Cyon (the LG local brand) .

Another thing you notice travelling on the Seoul subway, is how everyone has a mobile device of some sort, be it an MP3 player, PSP or mobile phone. And the most widely used feature on a mobile phone that I witnessed was..yes, you guessed it, TV...and not Mobile TV, but good old Terrestrial/Digital TV, whose signal is captured via a not-so-modern retractable antenna.

All of this should not make us forget that Mobile Social Networking is also huge in Korea, with the Cyworld service launched by SK Telecom boasts over 20m users and has built a profitable business model based on sale of creative digital content.

Finally, it was also noticeable how every car (and I really mean all of them, taxi or otherwise) had a GPS PND device-Seoul is a big city, so GPS offers an invaluable service to local drivers.

One bit of trivia...Samsung is actually a word in Korean and it means 3 stars.

Mobile Web 2.0-KoreaComm 2008 Presentation

Evolution Of Mobile Web Ric Ferraro

View more presentations or upload your own. (tags: playground open)

KoreaComm 2008-IPTV, Converged Services & More

SEOUL- Steve Murphy from AOL kicked off the event yesterday with a keynote speech where he highlighted the following based on his experience at AOL and of AOL customers:

-Mobile is about immediacy more than anything else...as people can get to their mails quicker on mobile than on a PC this explains the migration from PC to Mobile Web (personal note:hearing subsequent talks on future converged devices about to be launched that go for a widget based Web approach, immediacy could come to the traditional PC world soon)

-Mapquest is one the most downloaded AOL apps in the US

-About open models, the question is not so much whether this is important or not (everyone has it a priority)..the issue is whose version of 'open' will prevail

-Steve also made a point about niche plays on mobile which is convenient for me as I make a point on this in my presentation later today


Young Lyoul Lee from KT gave a remarkable presentation on IPTV in Korea (it is simply huge here, with KT planning to invest $1bn in this area over 5 years)...over 450,000 subscribers have signed up since launch in early 2008...the KTH network (a subsidiary of KT) now has over 35,000 videoclips available, the biggest collection of any operator in the world.

KT is now about to launch an IPTV-Shopping combo service this month, where you can watch actors in a videoclip and interact to find out what they are wearing and make a purchase online...

Young Min Kim from CELRUN gave a presentation on converged services, explaining how Telephone, Internet, Broadcast and Content are set to converge business models soon..interestingly I was reading the local paper today and they mentioned how the Korean government had just approved portability of household numbers so that users switching to IP telephony could retain their old number...

Young Min made a good point about the need for Service providers to merge to be able to increase the scope of their offerings..a trend we are starting to see already.

KoreaComm 2008 Kicks off

SEOUL -Things are about to kick off here at the Seoul Sheraton and the expected 2000 strong crowd is making its way in...huge auditorium here with a largely Korean crowd, though the first couple of seat rows are reserved for foreign dignitaries including various diplomats from Latin America, Central Asia and other areas.

Was provided with a thoughtful gift of a 4-CD boxset of traditional Korean music, which I will duly check out on the all-singing and dancing Bose stereo at the W Hotel.

More at lunchtime (Korean time)...

The stories behind the apps

As we mentioned yesterday, the Android Market is now open for developers to upload their applications. I'm pretty excited because Market, along with the availability of the first Android-powered phone and the Android 1.0 SDK, puts the basic pieces of the Android platform into place for developers to create and distribute their apps.

To help developers better understand what's available to them, we've collected stories from some Android application developers. In the videos, you'll hear them talk about how they built their apps, their takes on the Android platform, and also some tips they want to share with other developers. I think they have a lot of insight to share about Android application development, so I hope you'll find these videos useful.

Here are the first two developers in this series:

Jeff Sharkey is an ADC finalist—he built CompareEverywhere.

Jacob Abrams is from Glu Mobile and helped to build their first Android app, Bonsai Blast.

Keep an eye on this blog, our YouTube channel, or the playlist for this series for more of these videos in the coming weeks.

The Evolution Of Mobile Web

I'm going to Seoul for the KoreaComm 2008 hosted by the Korean Communication Commission with over 2000 professionals expected to attend over the two day event on 30-31st October.

I'll be giving a talk on the evolution of mobile web broaching such subjects as 'are we at Mobile 2.0 yet' and picking out a few key trends I've noticed over the last year.

I'll be dedicating some time to discussing the evolution of Location Based Services and the convergence between Mobile Social Networks and LBS's. Not only are services based around location quintessential to what makes up Mobile 2.0, but the whole area of LBS is going mainstream as it navigates its way through the famous hype curve..witness Loopt's sponsoring of The Middle Show in the US.

I'll post more from the event over the next few days as well as share my presentation online.

Android Market: Now available for users

Last month I outlined some details around Android Market. Today, Android Market launched for users to download applications along with the first Android-powered phone—the T-Mobile G1.

With Android Market, users can easily download apps to their Android-powered phone. Users can also rate the apps they've downloaded and leave comments. These users' ratings along with anonymous usage statistics help determine how apps are ranked and presented within Android Market.

If you're a developer, you will be able to register and upload your applications starting next Monday, 2008-10-27, when we've wrapped up a few final details. In order to make sure that each developer is authenticated and responsible for their apps, you will need to register and pay a one time $25 application fee. Once registered, your apps can be made available to users without further validation or approval.

Starting in early Q1, developers will also be able to distribute paid apps in addition to free apps. Developers will get 70% of the revenue from each purchase; the remaining amount goes to carriers and billing settlement fees—Google does not take a percentage. We believe this revenue model creates a fair and positive experience for users, developers, and carriers.

There are already over 50 apps available in Android Market today. You can view a showcase of some of these apps—which include multimedia, location-based tools, barcode scanners, travel guides and games—at http://www.android.com/market/. Now that Android Market is live and ready for contributions, we hope to see developers adding their own compelling apps starting next week.

In the coming months, we'll continue to roll out additional tools and enhancements to Android Market. We also expect to see additional Android-powered devices rolling out by different carriers around the world. Starting today, you can get a device, test your apps on it, and get them ready for upload. On Monday, to share your app with the world, simply register, upload your application and publish it. It's really that easy. I look forward to seeing what you bring to the Market.

Update: As of Monday morning (2008-10-27), http://market.android.com/publish is now available for developers to publish their apps on Android Market.

New Android Maps API Terms of Service and Key Enforcement

When we released the 0.9_r1 beta SDK, we mentioned that the Maps API included with Android would soon require an API key to function correctly and load map tiles. Part of the reason for this was that the Terms of Service (ToS) for the Maps API had not been finalized.

Today, I'm pleased to be able to tell you that the new Android Maps API ToS are now finalized and they're actually pretty exciting. Most of the restrictions present in the old ToS are now gone—for instance, it's now permissible to use the Android Maps API to build "friend finder" style applications. There are still a few limitations, but not nearly as many as before.

Now that the ToS are finalized, it's time to take the next step. Until now, developers have been able to use any value for their Maps API key—that is, the Maps API keys weren't enforced. However, starting early tomorrow morning (Oct 22nd, PDT), we are turning on Maps key enforcement, so the grace period is ending very soon. This means it's also time for developers to acquire and begin using real API keys. Here's what you'll need to do:

1. Visit http://code.google.com/android/maps-api-signup.html, fill out the required information, agree to the Terms of Service, and submit.
2. Take the key you are given in response, and place it either:
• In the XML layout where you declare your MapView, or
• In your source code, where you instantiate your MapView object

The way the keys work is that when you use a MapView, it queries the system to find the public fingerprint ID of the certificate used to
sign the currently-running application. The MapView then works with the server to verify that the certificate which signed the current application is the same certificate to which the current Maps API key belongs. If they match, then tiles are displayed; if they do not match, then no map tiles are displayed.

You will need one Maps API key for each certificate you use to sign your applications. That is, you'll need separate Maps API keys for both your debug-time signing certificate used in the emulator, and for your release-time certificate you'll use when publishing your apps. Fortunately this is free, and there is no limit to the number of keys you can acquire. Finally, note that this only applies if you're using a MapView in your
Android application. If you don't use Maps at all, or if you use an Intentto launch Google Maps, you don't need to follow these steps.

Be sure to get your Maps API key now to avoid a disruption.

Android is now Open Source

Over the past year, we announced Android, released several SDKs (eventually resulting in the 1.0 SDK), gave out the first half of the $10,000,000 prize money for the Android Developer Challenge, and prepared the first Android-powered device for users. Tomorrow, the T-Mobile G1 goes on sale.

But today, we're making what might just be the most exciting announcement of all: we and our Open Handset Alliance partners have now released the source code for Android. There's a huge amount of code and content there, so head over to http://source.android.com/ for all the details.

I'd like to offer a huge thank you and congratulations to my colleagues and the Alliance partners for what I hope will be a red-letter day for the open source community, and openness in the mobile industry.

"Mobile Crunch" -New rules for Mobile Start-ups in today's economy

Extremely well-timed Mobile Monday Barcelona session last night focussed on Mobile Start-ups in Times of Crisis and how to manage through a financial and/or economic downturn.

Panelists Oscar Farres from Debaeque Capital, Sergio Perez from Caixa Capital Risc and Marcel Rafart, from Nauta Capital, gave their take on the current situation and offered guidance to young mobile start-ups.

Their main points:

• The rules of engagement have changed -risk profiles have shot up and banks are retreating to safe investments, those that generate revenue or profit already (but preferably both). Fundamentally, for young start-ups the message was 'forget the banks'.
• Start-ups should outsource or plan to outsource whatever activity can be externalised, as these leverages the company's cost base and reduces risk from an investor point of view.
• Focus on burn rates-cut out any expenditure that is not strictly essential
• These are tough times, but also times of opportunity for those companies able to stick it out throughout the crisis.

As Rudy de Waele put it eloquently, 5 years ago there was no Facebook or Twitter or myspace...times of crisis allow for a natural selection of only the very best concepts and businesses. Start-ups should really ask themselves what unique benefit do they offer that no-one else offers?

I asked the VC guys what % ROI they expected to still consider making an investment and the rule of thumb was 25-30% y-o-y.

Interestingly, Oscar Farres highlighted what he considered to be the big growth opportunities in the market (independently of recessionary pressures) and Location based services was up there amongst the chose few sectors.

Opera Mobile for your Windows Mobile Device

It has now been 3 months since the Norwegian browser Opera released the beta of their Opera Mobile 9.5 for the Windows Mobile platform. Despite some initial bugs, including an OOM (Out of Memory) problem on some devices as a result of caching activity and a Notifications bug (that turned off notification sounds), overall feedback has been positive from the Opera fan base.

Browser wars are hotting up, though, with Mozilla announcing a mobile version of their browser later in the year, Skyfire consolidating its mainstream appeal and the i-Phone Safari browser receiving accolades for its user experience.

Meanwhile, Opera's Java-based browser, Opera Mini, has built up a substantial following of its own and provides an excellent solution for mid-range phones to access the web and avoid connectivity glitches that arise by accessing the web through the operator portal.

Currently, Opera Mobile 9.5 only works on touchscreen devices with non-touchscreen compatibility expected to be added in the future. However, things have gone dead quiet on the community forum over at Opera and no announcements have been made of future releases..maybe they are busy gearing up for the Mozilla launch, which is now rumoured to take place in 'a few weeks'.

Why now is a good time to invest in mobile start-ups

Global financial meltdown...credit crunch...government bailout...fiscal tightening...all these words will be very familiar to everyone following the unfolding of financial events on both sides of the atlantic. The picture for stock holders and bond holders, from private investors to pension plan owners, is not pretty.

That small proportion of wealthy individuals around the world are faced with some stark choices for making the most of their capital...look to preserve it by adopting a risk-averse approach (and buy gold bullion) or sit on their cash and ride out the storm, wary of potential bank collapses.

Neither of these two options offer the true capitalist a decent return. But, as always, there is money to be made in times of crises and parts of the economy that will fare better than others. The mobile sector is by no means immune to the downturn, and while operator revenues are likely to stay flat (guarded by inelastic demand), other parts will grow.

Mobile web is at an inflection point in terms of its global growth, moving from niche to mainstream, from Mobile 1.0 to Mobile 2.0, and there will be a number of competent start-ups that, though small today, will be huge tomorrow.

The great news is that the relative risk of investing in these start-ups has decreased compared to a year ago, given the drastically reduced equity returns from quoted companies. In addition, many of these quoted companies have either cut or withdrawn their dividend, and so look and feel more like growth stocks.

Fancy a flutter on an equity investment? My advice is, look at the opportunities out there to fund a mobile web start-up: it will be not much riskier than a blue-chip investment, will certainly be more fun to follow and, you never know, could be your next mobile equivalent of Facebook.

Enablers for Mobile Social Networks (MSN's)

LONDON-As one of the key themes that was discussed at the Mobile Web Europe Conference last week in London was Mobile Social Networks (MSN's), User Generated Content (UGC) vs branded content and Location enablers, I feel prompted to delve into this subject area to share some current thoughts.

Firstly, when we think about MSNs we often witness the attempt by some operator or another to launch their own network (whether based around music or some other catalyst)...these attempts have met with mixed success, though it is probably to early to draw a line below them. Nontheless, in research presented by Priya Prakash of Flirtomatic, over 70% of social network users would refuse to join a(nother) social network created by an operator. On the other hand, off-portal attempts by start-ups (notably itsmy.com) have met with success.

In general, the feel I get is that operators are losing traction at a faster pace than anticipated and off-portal startups have proved that it is possible to build a sustainable and profitable business without the operator.

Social objects (or the reason two people are talking to each other) can be either UGC or branded/syndicated from mainstream sources...with the saturation in the MSN playing field, it seems that at the very least a mix of the two is required to ensure that community members remain stimulated (and check in daily or hourly on the MSN).

An interesting play on this is by Buongiorno's blinko MSN (currently in closed beta) which has VIP channels that allow users to follow their favourite celebrity (be it Paris Hilton or Beyonce' Knowles).What is interesting is also the breadth of VIP channels available, which relates to a point made by Adrian Velthuis of Milennial Media. He stated that advertisers and community hosts alike should develop niche audiences to allow a differentiation in their offering compared to the plethora of competing MSNs or other mobile content.

As far as location is concerned, my belief is that this will be one of the key enablers of MSNs in the future -and that while technological limitations mean that it is still not mainstream, developments are expected in leaps and bounds. Sam Critchley from Gypsii talked about 'ambient awareness' as being the background awareness of what one's social network is doing...definitely something that reinforces location as a key enabler (where am I?) to achieve that contextual holy grail (what am I and my friends doing?).

Mobile Web Europe Conference- Key Takeaways

LONDON -It will take me a while to assimiliate 3-days worth of information on where we are headed with Mobile Web today but some of the key questions that were addressed were:

-Should we head towards a 'one-web' concept (same for PC and mobile as per the Convergence theorists) or more towards two distinct webs (as advocated in part by .mobi), one optimised for PC and the other optimised for Mobile (and the maligned 'small screen')?

-With much talk of Mobile Social Networks, shouldn't companies in this space realise that they need to focus on hosting the network instead of managing it? This was a great point mentioned by Priya Prakash of Flirtomatic, who also went on to state that a great host should facilitate conversations and act more as a matchmaker so that new contacts can be made

-Alfie Dennen from moblog:tech was of the opinion that the iphone has taken the industry a step back (due to its closed environment), something overlooked amongst the mass hysteria surrounding it

-Kashif Hassan, from ooober, made an excellent point about content, suggesting that given the sameness of many Mobile Social Networks, it is the presence of branded content that will make the difference...witness HBO's Entourage feature on the whrrl site

...to be continued///

Announcing the Android 1.0 SDK, release 1

About this time last year, my colleagues and I were preparing for the first of the "early look" SDK releases. I remember being a little freaked out—November 12 was starting to sound awfully close! But I think I can safely speak for the entire Android team when I say that we were all very excited about that upcoming release. In the year since, we've run and concluded the first Android Developer Challenge, given away $5,000,000, released more SDK builds, and worked with our partners to prepare the first device for users. It's been quite the whirlwind of a year.

In one of those strange cosmic symmetries, here we are a year later, and we're once again very excited about an upcoming release. I'm referring, of course, to the first Android-powered device that our colleagues at T-Mobile have just announced—the T-Mobile G1. We can't wait to see our hard work on store shelves and in the hands of users, but today we're almost as excited because we're announcing the brand-new Android 1.0 SDK, release 1.

Yes, that means we're officially at 1.0. Of course the SDK won't remain static—we'll keep improving the tools by adding features and fixing bugs. But now developers can rely on the APIs in the SDK, and can update their applications to run on Android 1.0-compatible devices. The Android Market beta will also launch with the T-Mobile G1, providing developers an easy and open way to distribute their applications on that and later devices. I've already seen a lot of applications that have me stoked, and I can't wait to see things really come together as developers cross that final mile to prepare their applications for Android 1.0.

So what's next for us? Well, we'll keep working on the SDK, as I said. But we're also working hard with our partners in the Open Handset Alliance on the open-source release, with the aim of making the code available in the fourth quarter. The second Android Developer Challenge is also on the horizon—watch this space for more details. We're also already working on the future of the Android platform, and on more devices. We've updated the Developer Roadmap, and we'll keep updating it as more information becomes available.

It has indeed been quite an exciting road to get to where we are today. The road stretches on ahead though, and we're not slowing down for a moment. I look forward to meeting and working with many of you developers out there—and trying out your apps on my phone!

Happy Coding!

Panoramio

The Panoramio web site has a great collection of photos from all over the world, and they also have a very convenient web API. I thought it would be a lot of fun to use Android to access this content while you are out walking around – and especially to have Android find interesting photos based on your current location. The resulting open source application is now available in the apps-for-android project.

The application starts by showing your current location in a custom MapView. You can pan and zoom this map to choose the area you want to search.

Once you have selected a search area, the application downloads thumbnails of the most popular photos taken within that area:

You can tap on an item to see more details.

From here you can use the menu to find more pictures by the same photographer or to see the original photo on the Panoramio site. My two favorite features, though, help you find the location of the photo in the real world. You can show the location on the map along with your current location:

Or, you can bring up a radar view that uses the compass and GPS to show you the location of the photo in relation to your own location:

I thought that other applications might want to use the radar view for their own purposes ("find me the nearest taqueria"), so I split that into its own package. You can find the source for that in the Radar project. Of course, you don't need the source in order to use this feature. Because of Android's component architecture, all you need to do us use an Intent:

Intent i = new Intent("com.google.android.radar.SHOW_RADAR");

i.putExtra("latitude", 37.422f);

i.putExtra("longitude", -122.084f);

startActivity(i);


The code for these applications is not very long, but they are a good example of how to use a number of Android's location APIs:

• Using an embedded MapView along with a MyLocationOverlay to plot your current location. The is also a custom class which extends Overlay to draw the Panoramio pushpin.
• Using the SensorManager to get our compass heading.
• Using the LocationManager to determine our current location

Using WebViews

I've written a small application called WebViewDemo that shows how you can add web content to your application. You can find it in the apps-for-android project. This application demonstrates how you can embed a WebView into an activity and also how you can have two way communication between your application and the web content.

A WebView uses the same rendering and JavaScript engine as the browser, but it runs under the control of your application. The WebView can be full screen or you can mix it with other Views. The content for your WebView can come from anywhere. The WebView can download content from the web, or it can come from local files stored in your assets directory. The content can even be dynamically generated by your application code. For this example, the HTML comes from a local file called demo.html.

This application does not do very much: when you click on the android, he raises his arm.

This could, of course, easily be accomplished with a little bit of JavaScript. Instead, though, WebViewDemo takes a slightly more complicated path to illustrate two very powerful features of WebView.

First, JavaScript running inside the WebView can call out to code in your Activity. You can use this to have your JavaScript trigger actions like starting a new activity, or it can be used to fetch data from a database or ContentProvider. The API for this is very simple: just call the addJavascriptInterface method on your WebView. You pass an object whose methods you want to expose to JavaScript and the name to use when making calls. You can see the exact syntax in WebViewDemo.java. Here we are making our DemoJavascriptInterface object available to JavaScript where it will be called "window.demo".

Second, your Activity can invoke JavaScript methods. All you have to do is call the loadUrl method with the appropriate JavaScript call:

mWebView.loadUrl("javascript:wave()");

Our WebViewDemo uses both techniques: when you click on the android, it calls out to the activity, which then turns around and calls back into the JavaScript. WebViews are very powerful, and they may be a valuable tool to help you build your application – especially if you already have a lot of HTML content. As it happens, we've used exactly this approach in some of the applications we've written.

Divide and Conquer

Years ago I was addicted to a simple game that I played on my then state-of-the-art Pentium-75. In this game, balls would bounce around, and I would try to partition them into small enough spaces so that I could go to the next level where more and more balls would be added. As of a couple of months ago, for the life of me, I couldn't remember the name of this game. So when I sat down to write an application for Android in my 20% time, I thought, why not try to recreate something similar? After completing most of the game and showing it to some of my friends at work, one of them said, "Oh, this reminds me of JezzBall!" Eureka! If working on this game does nothing more than reveal the name of one of the favorite games of my youth, I'll call it a success, but in the meantime, I'm happy to announce that the source of this application, named Divide and Conquer, is now available on apps-for-android.

The game starts with instructions:

and begins simply enough with one ball bouncing around. You drag your finger in a horizontal or vertical gesture on the screen to initiate a line that extends until it reaches the edges:

In each level, once you've shaved off 80% of the original area, you move to the next level. Here's a screen shot of level 6:

If a ball hits a line in progress, you lose a life:

Once you are out of lives, it is game over:

While this game isn't going to win any awards for cutting edge graphics, it demonstrates use of several Android features and APIs:

• custom drawing and animation
• touch input based gesture detection


• overriding the default behavior of the back key in some situations (to pause the game)


• creating custom Dialogs


• configuring an application to be full screen with no title or status bar
• use of the preferences framework


• use of the vibrator API

DivideAndConquerView is a custom View that implements its own onDraw method using the Canvas methods, and gesture detection using onTouchEvent and a helper class DirectionPoint. It keeps track of the state of the game using BallEngine, and reports relevant events back to the main activity of the application, which, in turn, keeps track of and controls the state of the game. The application is configured to be full screen in its AndroidManifest.xml file.

GeoMe quoted in El Pais Newspaper as Leading LBS Innovator

MADRID -El Pais, Spain's leading newspaper, published an article yesterday on Location Based Services and Mobile Social Networks, describing the overall environment and prospects.

'In Spain, there are a handful of innovative start-ups vying to lead the market.From the location-based service of GeoMe...the mobile phone is 'dressing up' with a web outfit in order to hit the town..' says Manuel Angel-Mendez, from El Pais.

I was interviewed for this article and duly get a quote later on where I state my view that most users don't want to be tracked wherever they are and prefer to leave messages on a map so that only their friends can see them if and when they are in the same area as the message.

Rummble, one of the companies presenting at the Mobile 2.0 Europe event in July in Barcelona (see previous quote) gets a well-deserved mention-they have a recommendation-based search function that allows community members to receive notifications according to your preferences.

'The barrier for mobile social networks is achieving a community of 100,000 users' continues Angel-Mendez, 'Once a service hits this magic number, anything is possible'.

For Spanish-speakers, the El Pais article can be referenced through the title link of this post.

Three new Samples: Triangle, SpriteText and Downloader

I've posted three new open source samples to the apps-for-android project: Triangle, SpriteText and Downloader.

The first two samples, Triangle and SpriteText, show techniques that would be useful to anyone using the OpenGL ES 3D graphics APIs to write Android applications. The samples contain several reusable classes that may eventually be incorporated (in some form) into the SDK. Chief among these is the GLView class, which abstracts the OpenGL ES book-keeping code from the rest of the application. GLView helps handle the extra work OpenGL ES applications have to do when the activity is paused and resumed, and when the display goes to sleep and wakes up. In the Pause/Resume case the OpenGL surface has to be recreated. In the display sleep / wake-up case the entire OpenGL context has to be recreated.

Triangle

The first sample, Triangle, shows how to use the GLView class and the OpenGL ES 3D library to display a spinning textured triangle. Think of it as the "hello, world" of OpenGL ES apps. Because it's relatively simple, it's a good place to start when experimenting with the OpenGL ES API.

SpriteText

The second sample, SpriteText, shows how to efficiently display screen-aligned text using the GL11Ext.glDrawTexiOES method. SpriteText contains a reusable LabelMaker class for drawing static text and screen-aligned images, as well as a Projector class for finding the 2D screen coordinates corresponding to a 3D point, and a MatrixTrackingGL class for keeping track of the current transformation matrix. Finally, it shows how to use these classes to display a milliseconds per frame counter. A ms/f counter can be helpful for tuning graphics performance.

Downloader

The third sample, Downloader, shows how to add a downloader activity to your application. The downloader activity runs at the beginning of your application and makes sure that a set of files have been downloaded from a web server to the phone's SD card. Downloader is useful for applications that need more local data than can fit into an .apk file. For example a game could use Downloader to download the game's artwork, sound effects, and level data. The Downloader activity is designed to be a drop-in addition to your application. You customize it by supplying the URL of an XML configuration file which lists the data files that need to be downloaded.