.Dust

This is the pre­sen­ta­tion I gave a few weeks ago at the UXcon­fer­ence 2009.

There were a lot of great pre­sen­ta­tion and it was a fan­tas­tic event that I hope to attend again in 2010.

As I usu­ally do the pre­sen­ta­tion need some details in order to be bet­ter under­stood. Below you will find some com­ments on the slides.

Slide 3 — 4

Mobile Social Net­works were born at the very same time Mar­tin Cooper from Motorola placed the first mobile call back in 1973. When we decided that mobile phones had to have a con­tacts appli­ca­tions we can say that mobile social net­works were born.

Slide 5 — 7

30 years later 3 launched the first UMTS com­mer­cial net­work in Europe with the NEC E606 and Motorola A835 mobile phone.

Slide 8 — 9

The orig­i­nal sin. We, as oper­a­tors, have been blind to the fact that the con­tact appli­ca­tion could be the foun­da­tion of the mobile social network.

Slide 10 — 11

Actu­ally we can observe a tran­si­tion from SMS (Short Mes­sage Ser­vice) to SSM (Short Sta­tus Mes­sage). This is def­i­nitely a quan­tum leap. (By the way, we should be a lit­tle be scared of this as oper­a­tors )

Slide 12 — 17

Usu­ally on Social Net­works we can share plenty of con­tent and, while in mobil­ity, most of that can be asso­ci­ated with posi­tion­ing infor­ma­tion from GPS and net­work assisted services.

Slide 18

We will need to rethink the whole User Expe­ri­ence of Social Net­works in mobility

Slide 19

This a process that need to take in con­sid­er­a­tion the End to End archi­tec­ture that we, as oper­a­tors, pro­vide to our users. This the only way where we can pro­vide value and avoid the “bit pipe” nightmare.

Slide 20

How can we do this?

Slide 21

Let user con­sume Social Net­works from his con­tacts appli­ca­tions. Aggre­gate every­thing in there and do no place plenty of sin­gle appli­ca­tions into the mobile phone.

Slide 22

Aggre­gate con­ver­sa­tions. We are all parts of sev­eral social net­works and most of the time they do not over­lap too much. Usu­ally when I post some­thing to Twit­ter it gets auto­mat­i­cally reposted on Face­book, Friend­feed, etc.. On each of those place a con­ver­sa­tion starts but I have no option, today, to look at those con­ver­sa­tions from a sin­gle point of view on my phone.

Slide 23 — 24

Let the back­end to the dirty job. We have to remem­ber that the vast major­ity of our cus­tomer base does not have an iPhone or a Smart­phone. We can aggre­gate con­tent on the server side and deliver result to a very thin client appli­ca­tion on the mobile phone.

We can also think to add push as a pre­mium ser­vice to our customers.

Slide 25

Most of the new mobile phones are now touch devices and we need to rethink at usabil­ity for­get­ting what we were used to do with the clas­sic rocker inter­ac­tion. There are new ways to browse and con­sume content.

Slide 26

If we aggre­gate data on the server side we can also dis­cover con­nec­tions for our cus­tomers. At the end of the day we can think at the mobile phone num­ber as a very good proxy to OpenId in mobil­ity (apart from any pri­vacy considerations)

Slide 27

We must allow the end user to con­sume the con­tent directly from the con­tacts appli­ca­tions. If one of my con­tacts posts a photo or a video I do not want to exit the appli­ca­tion, launch the browser, wait, and then relaunch the con­tacts appli­ca­tion again.

Slide 28

We can use the phone short range com­mu­ni­ca­tion sys­tem (blue­tooth, near field com­mu­ni­ca­tion, etc) to broad­cast our social iden­tity. If we want to, obviously.

Yeah, I know… that was quite fast. If you want to dis­cuss about that just drop me a line.

Related posts:

1. Too Much Social
2. Wide­noise. Noise made social.
3. The Part And The Whole, Or Why You Should Bother About Social Web.
4. Why I do like Sonopia
5. Tech­nol­ogy is there