I’ve processed and put up all the videos I recorded now – sorry I didn’t manage to record more!

Some were on Blip.tv and some on YouTube, so the full list of the lot is here (my post on the weekend from a girl geek perspective!).

Or you can see just the blip.tv videos.

And I’ve also taken the liberty of making up my own laws of mobileCamp!

Many thanks to everyone involved.

Imp.

On Saturday, Jure Sustersic gave a talk on Nokia’s LBS services and how developers can access them:

Peter Bond of Otodio spoke about using synthetic and real voice applications to provide more effective information to mobile users.

Michael Shiloh of OpenMoko sits down with Improbulus of A Consuming Experience to go over his presentation at Mobile Camp London.

Here are the slides that accompanied this presentation:

Petro Soininen from Forum Nokia was our first speaker on Saturday. He gave an overview presentation on developing widgets for Series 60 phones:

Connecting people with technology. Technology that connects people must be sustainable, wearable and functional.

Current wearable technologies, eye glasses, hearing aids, IUD, pace makers, prosthetics etc.

Blue-Jacking, podcasting, moblogging and smartmobs are all items that have been all about connecting people on the move. As a result there are needs for having technology more integrated whilst on the move.

Portable and wearable are not the same thing. Portable is boxes attached to things and are carryable not integrated. Uncomfortable, awkward and not quite wearable. (more like attachable/ optional – or handbag bling ;) )

Wearable technology has a stereotype related to the military, medical and geek cultures. This however is a past stereotype. Hopefully over time this stereotype will break down and be come something normal rather than freaky.

Hug shirt: Wear the hug shirt and squeeze… then send it to a hug message through the sensors in the shirt and squishes the person when they are wearing it. These shirts are going to be shown in a sci-fi movie. These items are going to manufacturing soon, market date is to be announced at a later date.

This company is really switched on to the context and the ability to access information any time, place etc. They are also quite tuned into both the male and the female market for wearable technology.

SkateHoodie: listening to music without having to have an mp3 player attached to you. This is a device plays and stores the music for you, just attach a usb device and it just uploads it. There are again no wires in this device, the speakers are in the jacket and play.

Tom is yet again in front of the audience… One of his favourite places in the world… a room full of developer types and talking about the latest mash up software from Yahoo. You can find information on FireEagle The api’s are currently in pre Alpha and are all about enabling a middleware layer of functionality such as mapping and flickr integration based on mobile cell id for users. (for example)

Yahoo are currently looking to pre-alpha partners that are interested in partnering up with people interested in gps partners, i.e. those people interested in location based services. Each application needs a key which signs the application to be able to use this service in very much the same way that facebook does. However within FireEagle you can limit the information being passed through to other applications through the service management interface. This is an interesting way of doing things and limits the amount of data being private and belonging to the users.

Adam Cohen-Rose at Kizoom is working with Transport for London’s (TFL) Real-time Integration Programme (RTIP) and Imperial College London on the Vortix project which is looking to see how how RFID can be used in a transportation contexts.

At Blackfriars station there are multiple lines, including bus and river ferry connections. Its a confusing place, with lots of options. Signs are helpful, but is there something else we can do as well?

National Rail Enquiries is providing Kizoom with real time information on train, bus and ferry times. Users can swipe their phones across posters, and get real-time updates on their devices. The idea is this:

With an RFID Reader on your phone and a little application your phone, you can get updates on route based on when and where you are.

The project is in its early stages, TFL is passing out Nokia 6131′s to test subjects to see how users might react to updates, tied to place can affect their experience.

It’s an interesting concept, I wonder if they’re talking to Timo Arnal Arnall at all?

Post event note: Adam has just pinged me to include this link for further details:
http://www.tfl.gov.uk/corporate/media/newscentre/5832.aspx

This session was done by Otodio and it was all about audio information and how it should be effective, simple and monetisable. It should also be easy, tagged and so much more. More than just music audio track stuff… It’s planned for mobile device integration and should be able to deliver documents as sound.

This session was more about a product than technical content. However if you want to find out more then please see Otodio’s website.

The podcast for this session will be arriving shortly:

Sam gave a talk about the good, the bad and the ugly of the services that you do and don’t have access to as a developer and all those things that are potential but just aren’t available unless you are on their white list. The same issue of whitelists is applicable in the UK independantly of each operator.

Items that were discussed were, identity of user/ device, payments or charges for services via mobile device billing mechanism. Location aware data again needing identity information. Security of data and authentication across sessions.

For the side of the operator it’s all about risk vs reward. If you’re the little guy or girl then you’ll find that it’s hard to get integrated with the operators and you’re cut is pretty small for any profits collected via the operator offering a service to the customer.

All in all it’s not a nice system at the moment. So I guess the other thing that the operators should consider that all these links through and issues that they are creating by being quite closed are things that long term the developers will find a way round. Wifi helps the developer. The phone numbers for ID can be a log in for the user on the phone turning on. Location could be triangulated (or if there’s GPS in the device you could use that) and for payments you can use paypal.

Network Operators see their closed wall garden as a value added data service. The way I see it there are two spaces and the most usable will win out… what do you think?