With the aim of helping children learn maths and computing, a few years back some very bright people at MIT set about building a visual programming language called Scratch. Instead of writing lines of code, you arrange lego blocks that represent events, actions and logic. For those working in the GIS space think FME or Model Builder. Google have now taken this work, and built upon it, with ‘App Inventor’. Drag and drop building blocks, from within your web browser, to build an application for your Android mobile phone – the web development environment even includes an emulator. Sounds good, but does it really work?

In short – Yes. It’s a beta service and you can only deploy to phones connected to your PC (no Android market place distribution yet). It’s a Google beta, which means comprehensive, robust, and well supported. Everything I need for my mobile apps, is already there, location awareness, read-write-web, rich user forms, local storage and graphics.

It’s remarkable that mobile phone applications can now be developed within hours. I hope Google continue to grow this initiative, and can only recommend you try it.

I often work on the assumption that location adds value to an application, so it was intriguing to discover that a greater percentage of location aware applications are given away for free (40%), in comparison to the larger pool of iPhone applications, of which only a quarter are given away, and the remainder are sold.

The theory goes…take a GPS enabled mobile phone; some beta software from Nokia; a handful of HTML, Javascript and PHP goodness; and you have all the components for a dynamic tracking web service and mapping website?

Well, the theory works! I’ve put a demonstration together at the following link:

Mobile Phone Tracking with a Nokia N95 Demonstration

Given all the current hype regarding some telecomunications technology; I’m puzzled by the apparent lack of interest in the mobile web server. Sure, there are a few pieces to still fall into place, but if the mobile web server’s graduation from Nokia research labs, results in widespread deployment, it must have a profound impact on the web?

It turns out, a couple of years back Nokia embarked on a project to port the Apache web server to the symbian operating system that underpins their Series60 device platform. The project was subsequently handed over to the open source community and you can get involved here, project raccoon. Interestingly, Nokia have recently wrapped the web server as user friendly software with a supporting website: www.mymobilesite.net.

I installed the application on my N95 and as you might expect it provides complete access to the contents of my mobile phone via the web. I can fire up the web browser on my desktop PC and browse to a web page, and then click a button on the web page to take a photo with the camera on my phone, wherever my phone might be. I can then use my desktop web browser to browse the photos I have taken, or any other information I have on my phone e.g. contact details or calendar events.

This struck me as a unique piece of software, I tried to think of other software that functioned in a similar manner. After roaming the web for some ideas I found an article from Tim O’Reilly that suggested similar behaviour could be observed with Apple iTunes, he’s coined a term to describe such software as…‘software above the level of a single device’.

Installing the mobile web server software on your phone, allows you to use the software on any number of devices…your phone; a desktop client with web browser; a games console; or any other internet enabled device, even someone else’s mobile phone? Software above the level of a single device – just as Tim O’Reilly describes when he observers that you can control your iPod from an iMac.

From a geospatial perspective, couple the GPS enabled N95 mobile phone, with the mobile web server, and we have a tracking service that can be consumed by any internet enabled device, powerful stuff. Perhaps worthy of more consideration, I look across the GI industry, GIS software vendors, the open source community, and other corners, but I don’t see ‘GIS software above the level of a single device’ as an overriding design architecture?

There is a bigger question here…what happens when 3 billion mobile phones run as personal web servers?

March 2007 saw the release on the GPS enabled Nokia N95, assisted GPS followed shortly after. August saw a national campaign from Vodafone advertising location based services from UK property website Rightmove, and traffic updates from the AA. If in any doubt of the impact LBS would have on the mobile industry in 2007, October saw Nokia stump up $8 billion for mapping data provider Navteq; and only last week, news broke of a location enabled Apple iPhone.

The 2008 report strikes a more bearish note for LBS, at least with regards to GPS enabled mobile phones. Deloitte acknowledge that the convergence of successful technologies in their own right, doesn’t always add value to the converged device…just because we can GPS enable mobile phones, does it add value?

I have sympathy with this view point, and recall with anxiety, last weeks news from the Consumer Electronics Show (CES) of the MP3 enabled Stun Gun:

The 2008 Deloitte report can be found here: Deloitte Telecommunications Predictions 2008.

Having vague recollections of working with Java whilst undertaking my undergrad dissertation at Lancaster way back when, I plumbed for Java and promptly downloaded the Eclipse IDE. Next up, I installed Carbide.j, a suite of mobile development tools from Nokia. It was at this point I encountered my first frustration; it turns out the Carbide tools from Nokia don’t support the latest version of Eclipse, a school boy error of failing to read the doc. A quick uninstall, download, and install later, I’m back on track with an older version of Eclipse (3.1.2).

Nokia have provided a whole host of up-to-date documentation for building LBS applications for the series60 platform, so I downloaded their TouristRoute Java Midlet example and their location API developers guide. The location API is pretty concise, with a handful of important classes:


LocationProvider: represents the source of the location information (in this case the integrated GPS)

LocationListener: receives events associated with a particular LocationProvider.

Coordinates: represents coordinates as latitude-longitude altitude values.

Location: represents the standard set of location information (time-stamped coordinates, speed, accuracy, course, etc.)

Landmark: represents a known location with a name.

LandmarkStore: has some methods for persistent landmark store management (store, delete, and retrieve landmarks).


The sample built fine, generating a Java Archive (JAR) file and Java Application Descriptor (JAD) file. The JAR file is a package of the classes and resources, the JAD file a description of the Midlet. Right clicking on the JAR file (the midlet executable), the Eclipse context menu gives you two deployment options:


1) Deploy by Bluetooth
2) Deploy to Web Server


Unfortunately my laptop doesn’t have Bluetooth, so I went with option two and uploaded the files to my server (they can be downloaded here). I uploaded both files, the JAR and the JAD, I’m not sure if both are required or not? I added corresponding mime types to the .htaccess file on the server (this instructs the server how to handle requests for jar and jad files) and browsed to the jar file with my mobile phone browser. A couple of keypad clicks later, the application had been downloaded and installed on my phone.

I have had the phone for a couple of months now and am very impressed. Nice design, great camera, and a half decent GPS, but it’s the open development platform that sets this phone apart from the crowd, allowing everybody and anybody to develop a whole host of useful (and not so useful) applications. So far I’ve already acquired SportsTracker, which allows me to save my mountain bike routes as KML, some handy software that uploads my photos to my Flickr account, and the ubiquitous Google Maps which syncs nicely with the GPS.

Do we need a European Global Navigation Satellite System?

Galileo seems to have hit the rocks after the funding model for the project showed its true colours. In some sort of magic third way PPP\PFI buy-now, pay later scheme – so in vogue at the moment – it was initially envisaged that the private sector would contribute to somewhere near a third of the costs for such a system. For me, there are two chief reasons why I believe expecting a contribution from the private sector to fund this thing is pie in the sky…

First up, the Americans have developed GPS and provide free access for all, so rather crudely speaking, the argument goes “why sell Pepsi, when you can have coke for free?” – GPS is here, it works well, and it’s free.

Ok, so some say Galileo will be better, and I’m sure this is possible; but still, do we really expect business to pay for this upfront? To my mind this is the stuff of fantasy, business works for today and so often heavily discounts the future; for example, consider the following two statements:

“Today Google has joined forces with Salesforce.com to sell content based advertising”

“Google has invested $1billion in Galileo, the European Sat Nav system. On the back of this investment, it’s estimated that sales in location based advertising will quadruple, at some point after 2014 when Galileo will go live.”

Which statement will move the share price? The first! And it’s for this reason that it’s naive to expect the private sector to stump up money to fund Galileo, since any returns won’t materialise for a long, long time.

The debate is well worth a read; and now I’m going to try something new…a poll. For sure, it’s a little naff, but anyhow…if you’re one of my regular three readers…go on, vote

So if we accept that the private sector won’t invest cash up front…


Note: There is a poll within this post, please visit the site to participate in this post’s poll.

Over the weekend I read an article from the Technology, Media and Telecommunications group at Deloitte that was published last month and discusses some of their predictions for 2007.

Supporters of net neutrality, suggest the proposed plans for prioritising some web traffic, over other web traffic, has little to do with covering the cost of maintaining the network, it’s just a guise for the telephone companies (Telco’s) to grab a bigger slice of the pie – currently being eaten predominately by Google (and one or two other online companies). Telco’s, both wired and wireless, are under pressure to deliver increased returns to shareholders; with this in mind Deloitte consider some killer applications that could help them do this, and for mobile operators in 2007 that could mean delivering on the hype of ‘Presence Based Services’.

The report is well worth a read, some random points I found interesting are bulleted below:

• The volume of traffic flowing over the World’s largest Internet hub in Amsterdam, which caries 20% of all of Europe’s Internet traffic, grew at a compound monthly average of 7.4% in 2006.




• Daily traffic at the exchange exceeded one petabyte in Feb 2007, it’s expected the exceed two petabytes per day by Oct 2007.




• In 2002 adult internet penetration in the USA hit 60%, it was another 4 years before it clocked 70%.




• The PC is acting as a bottle neck to the internet, as there is usually only one per house, members of the household are prevented from accessing the internet at the same time. This should spawn the development of other lower cost devices that provide access to the Internet at the same time as the PC (e.g. radio’s & video phones).




• Mobile TV won’t work – mobile operators should concentrate on getting content (e.g. pictures & movie clips) off the mobile to more suitable devices (e.g. widescreen TV’s) if they want to boost revenue.