chrisblunt.com

Another analysis of mobile2.0 posted at landspurg.net, again identifying some of the fundamental problems facing the area - primarily HCI challenges and cost -, and analysing the current use-context which mobiles currently occupy.
mobile2.0 seems an increasingly active topic at the moment, especially as it seeks to define itself as more than merely Web2.0-on-the-mobile. Tom identifies synchronisation (perhaps to the Web or a local device) as one of the current use-context of current mobile(2.0) platforms. This is certainly the case with toupix, which as well as its J2ME MIDlet, uses a browser-based Web interface as a main point of interaction.

However, in the very near future (once the technical and standardisation issues are less of a barrier), I think it is likely that we will increasingly see mobile2.0 shifting to the (borrowing Tom’s terminology) browse-use context of the mobile that Web 2.0 is to the desktop.

My last meeting with Frances about Transience has finalised the context of Transience. With the technology working, all that remains is to write up the concept and some background information for the web site. It’s been suggested that I look into works by Nigel Thrift and Ivrea on isolation within the city, and examine some other worksin human geography. Once this is written and online, Transience will be available to download for mobile devices from www.chrisblunt.com/transience/

Socialight is a cool looking mobile2.0 app that lets you create ’sticky notes’ at a real-world location that are accesible on a mobile phone.

You leave your message (picture, message, sound..)in space via your mobile or the Web. When people running socialight are at that location, they can see (or hear) your sticky-note.

Looks really interesting, but at the moment it appears to be US only.

On the back of today’s meeting, I’ve finally bitten the bullet and released the first tentative steps of Toupix for testing. The offer is currently open to MLA/DAT students:

My final project is a social J2ME application for mobile devices. Unfortunately, I’ve only been able to test it on one phone so far (SE K600/K608i) on which it is, at last, working. However, before I go much further with it, I’d like to ask if anyone would be willing to give up some spare minutes testing it on their phone/PDA.

The MIDlet is written for devices supporting MIDP2.0, Bluetooth and with a camera. If your device fits these criteria, then it might work. If you’re unsure, it might work anyway, so give it a go!

To be involved, please let me know your name, email and device make/model.

Being a social thing, the more people using it, the better!

For more information, visit www.chrisblunt.com or www.toupix.com.

At the moment, the test is just to see on which phones Toupix works. Hopefully, it’ll work on any MIDP2.0 device supporting JSR-82 and JSR-135, but experience tells me things could never be so simple…

Today’s project meet with Geoff confirmed my fears that it’s about time toupix got released. Earlier, the day was spent sorting out random technical issues that decided to occur - something to remember for the final presentation. What’s left to do then:

ame
• Sort out a flickering display bug with the MIDlet.

ame

• Get toupix tested on more than a Sony Ericsson K608i. If you can help (a shout for Nokia owners :) please let me know!

ame

• Sort out the user licence.

ame

• Write up proper developer docmentation.Â

ame

• Find/Arrange an event where toupix can be used and tested in a real environment.

ame

• (Fix any issues that are certain to occur during the test)Â

ame

• Document that event!

ame

• Publish documentation to the website

ame

• Finish

The majority of work now rests on documentation, something that usually is a last-minute thing in my determination to get the project working! Hopefully, then, this blog might get updated a little more often…