The application itself comes with the phone on most recent Nokia S60 devices (with recent Firmware – check Nokia Software Updater for new firmware). To check if your particular phone is capable you can check the Nokia Share Online Support site.

Nokia Share Online appears on the home screen of your device (screenshots are from a N95 8GB):

Home Screen

First time only configuration

On first use you will have to check the available services by choosing ‘Options’:

Update Service

Activate Service

On a new device you will be prompted for your Flickr Username / Password. Since I have used the Flickr Plugin on this particular phone previously the Username was already saved (which is a bit of a worry – since deleting the account should have also removed the credentials I would have hoped).

Select Access Point

Activate Website 1

Activate Website 2

Accept Conditions

Set the update frequency:

Update interval

NOTE: Be careful with this setting as there could be mobile data fees involved depending on the method you use to connect to the internet on your device. Consult with your network operator on the fees if you are using the wireless data network of your phone provider.

After this step you are ready to connect to Flickr and sync your recent fotos:

Sync recent

Create Flickr Post

Once the service has been set up you can create post using the following steps:

New Post

Adding the Post Title and Description.

Post Title

Insert Image(s)

Choose Image

Tags

You can coose from a list of previously used tags (or create new ones).

Choose Existing Tags

Finally you can post to the web:

Choose Existing Tags

Your post is now being uploaded and should be available via your Flickr Photostream (mine is on http://www.flickr.com/photos/leogaggl/) soon. The upload time will depend on the size of the image and the speed of your data connection.

Enjoy !

Of course there is similar technology available for the applications that require this link between the physical world (presence) and the mobile internet. One example is RFID together with Near Field Communications (NFC). However apart from the additional expense for RFID labels, no other technology has anywhere close the number of handsets that are capable of using this technology without some add-on to the mobile phone. Currently there are only very few handsets that will support this technology. Possible use in m-Payment projects might speed up the process of handset manufacturers including this in their handsets, but that will be some way off. 2D codes are here and now.

Looks like I will dig out some of the pilot projects out of my (virtual) drawers and see if we can get some interest in them. The project that will most likely be the first is a m-Learning implementation using 2D codes together with the Moodle Learning Managment System which is our preferred LMS.

Let’s see if Australia is also ready to move on this technology ….

Some of the current limitation of this approach:

-cost of the bandwidth
-speed

The ability to proxy the users content on the Mobile Web server Gateway as well as the ability to integrate content outside of the mobile phone seem to be the main points that will have to be improved for this to become a more mainstream technology. Another area of concern (or another potential use of this technology – depending on your viewpoint) is the backup of data from the mobile phone. The ability to proxy the content on the Gateway could also be used as a backup of the content that is hosted within the MWS on the mobile phone.

Some of this work is already on the way. David Johnson (see above) is currently working on some Webservice API for MWS that should allow the use of MWS served content in mashups with other content sources.

General

Profile name: nodephone

Service profile: IETF

Default access point: {Your WLAN Access Point}

Public user name: sip:{NodePhone Phone No}@sip.internode.on.net

User compression: No

Registration: When needed

Use security: No

Proxy Server (not required)

Proxy Server Address: none

Realm: none

Username: none

Password: none

Allow loose routing: none

Transport Type: none

Port : none

Registrar Server:

Registrar Server Address: sip:203.2.134.1

Realm: BroadWorks (Note:CASE-SENSITIVE)

User name: {NodePhone Phone No}

Password: *****

Transport type: UDP

Port : 5060

General

Profile name: sipgate
Service profile: IETF
Default access point: {Your WLAN Access Point}
Public user name: sip:{SIPGate UserID}@sipgate.at
User compression: No
Registration: When needed
Use security: No

Proxy Server

Proxy Server Address: sip:sipgate.at
Realm: sipgate.at
Username: {SIPGate UserID}
Password: *****
Allow loose routing: Yes
Transport Type: UDP
Port : 5060

Registrar Server:

Registrar Server Address: sip:sipgate.at
Realm: sipgate.at
User name: {SIPGate UserID}
Password: *****
Transport type: UDP
Port : 5060

The screenshots are from a Nokia E65, but should be applicable for similar Nokia phones.

Screenshot 1

General

Profile name: engin
Service profile: IETF
Default access point: {Your WLAN Access Point}
Public user name: sip:{phone number}@voice.mibroadband.com.au
User compression: No
Registration: When needed
Use security: No

Screenshot 2

Screenshot 3

Proxy Server

Proxy Server Address: byo.engin.com.au
Realm: mobileinnovations.com.au
Username: {your engin phone number}
Password: *****
Allow loose routing: Yes
Transport Type: UDP
Port : 5060

Screenshot 4

Screenshot 5

Registrar Server:

Registrar Server Address: byo.engin.com.au
Realm: mobileinnovations.com.au
User name: {your engin phone number}
Password: *****
Transport type: UDP
Port : 5060

Screenshot 6