Mobile Web 2.0 Summit

group profile | members | imagewall

« older newer »

Live Qik page Osney Medias' Mobile web 2.0 Summit aims to:
Clarify the principles of Mobile Web 2.0 and understand how to create the business models required for an enduring industry
Determine who has value in the value chain and discover
Find out what tools can be used to understand the Mobile
Explore the role and revenue potential of Mobile Web 2.0 in advertising and brand impact
Discuss how to ensure excellent end to end user experience
Examine what social networking means from a mobile
perspective and how to monetise user created content
Discover the realities of billing models surrounding Mobile Web 2.0 and their impact on the market
Compare the world of PC and Mobile Web and determine how
Web 2.0 and Mobile Web 2.0 will share content
Hear from the latest start-ups and their ideas for the newest applications and services
Learn about the next generation platforms and enablement and the implications for Mobile Web 2.0




Add the Mobile Web Sumit Moblog Widget to your blog or website by copy-pasting in the following code:



Search this moblog


Recent visitors

Implementing Mobile Web 2.0 - The Eleven architectures of Mobile Web 2.0

(viewed 393 times)
Bookmark and Share
This article explores the implementation of Mobile Web 2.0. It is based on my keynote talk at the Mobile Web 2.0 summit http://www.mobilewebsummit.com/ next week. Starting from first principles, I discuss the practicalities of Mobile Web 2.0 and how it can be implemented at various points within the Mobile stack

The significance of Mobile Web 2.0

Why should you be concerned about Mobile Web 2.0?

Let us consider three key developments ..

1)When asked about the Web's biggest growth areas - Eric Schmidt said the answer was 'Mobile Mobile Mobile' http://blog.wired.com/monkeybites/2007/04/web_20_expo_eri.html
/>
2)Apple iPhone shares 70% of its revenue with developers, a development that flies in the face of the many excuses that so many Operators have been putting forward for so many years.

3)Nokia chairman Olli-Pekka Kallasvuo says that Nokia is going to be an Internet company

All these factors point to a critical trend

The Internet companies are finally driving the mobile agenda (and the savvy Mobile Companies like Nokia are now embracing the Internet and dominating it). These companies are looking at the Web and the Mobile Web together and see a seamless vision of the Internet spanning both the fixed and the wireless domains

It is no longer possible to ignore the impact of Web/Internet on mobile applications. This means applications that span the Web and the Mobile Web are becoming increasingly important. Traditional mobile applications like Ringtones are becoming saturated. The younger demographic is increasingly also looking at Web based social networking like MySpace and not just the mobile devices.

(Note: Strictly the Internet denotes any device connected to an IP network. The Mobile Internet denotes connecting to the Internet via a mobile device. The Web denotes an application level framework based on HTTP and HTML. And the mobile web denotes the usage of the Web on mobile devices. We use these terms here interchangeably depending on the context)

Mobile Web 2.0 cannot ignore Web 2.0

So, what is Mobile Web 2.0?

We cannot discuss Mobile Web 2.0 in vacuum. In discussing Mobile Web 2.0, let us not forget the intellectual debt owed to Tim O Reilly in defining Web 2.0.

Whichever way you look at it, Web 2.0 (as postulated by Tim O Reilly) has the following characteristics

a)The use of the Web as a backbone

b)Harnessing collective intelligence and

c)Creating a database/body of data that becomes richer as more users contribute to the system .

Mobile Web 2.0

While the Mobile Web has made increasing strides over the last few years, especially in the launch of Web Widgets , offline browsing and the availability of the full web browser on the Mobile Web(i.e. JavaScript, CSS etc); we still have a way to go in the universal and ubiquitous availability of the mobile web on to mobile devices.

Hence, if we extend the above paradigm of Web 2.0 to Mobile devices (i.e. Mobile Web 2.0) there are two implications :

a) The Web does not necessarily extend to mobile devices

b)Even though the Web does not extend to mobile devices, intelligence can still be captured from mobile devices since the Mobile device is always available at the point of inspiration and many elements can be captured uniquely through mobile devices(for instance Location)

This can be depicted as seen in the above image

The iPod/iTunes service is a preliminary example of Mobile Web 2.0. The ipod uses the web as a back end and the PC as a local cache. In this sense, the service is 'driven by the web and configured at the PC' but it is not strictly a 'Web' application because it is not driven by web protocols end to end (iPod protocols are proprietary to Apple). However, it uses the Web as a backbone and this makes it a Mobile Web 2.0 service if we extend the definition of Web 2.0 to mobile devices.

Deep blue sea problem

The problem with the above diagram is: Once the content goes on the 'deep blue sea' of the Web (for instance on Flickr, YouTube etc) - the mobile industry lost its leverage i.e. unique advantage.

So, the fundamental question regarding the implementation of Mobile Web 2.0 is: How does the mobile industry adopt the ethos of the Web (openness, no walled gardens etc) and yet maintain some unique advantages? I.e. bridge the world of the Mobile and the Internet?

Implementing Mobile Web 2.0

There are at least eleven ways if we extend the idea of Mobile Web 2.0 across the stack

1)The Operator implementation: This will be likely based on IMS/SDP.

2)The handset implantation - This approach is best indicated by Nokia's Ovi strategy and the iPhone.

3)The Enterprise network strategy: Best epitomised by Cisco's foray into Web 2.0 based on recent acquisitions such as Tribes and Five Across

4)The Web players coming to mobile .. Best example of this approach is Android.

5) Mobile Web 2.0 and Devices: Amazon Kindle

6) SCWS(Smart card web server) - A relatively new approach with the SIM cards being increasingly powerful and with the deployment of a web server on SIM cards with companies like Gemalto deploying SCWS services.

7) Identity and Security: Identity and Security can complement almost any service and a telecoms network has an advantage there.

8) Browser APIs/DOM extensions: OMTP, OpenAjax alliance and others are doing some great work here

9) Voice Call detail records to create social graphs

10) Make it quicker / easier: users will always pay extra for the small improvements which make their life easier even when other(more cumbersome) ways exist which may be cheaper. 11) And finally, there is the concept of Umbrella social networks Beyond Web 2.0

11) Umbrella social networks: i.e. a social network that spans the Web and the Mobile Web. Twitter being one such example http://opengardensblog.futuretext.com/archives/2007/10/umbrella_social.html
/>
Conclusions

As developments like the Android start becoming mainstream and the iPhone continues to make a big impact on the Mobile ecosystem: the full impact of Mobile Web 2.0 is only now starting to be felt. As more services span the Web and the Mobile Web, we will see greater uptake of Mobile Web 2.0

These ideas are explored in the forthcoming book Implementing Mobile Web 2.0 by Ajit Jaokar. Please contact me at ajit.jaokar at futuretext.com if you wish to know more.

Alfie says:

An image based post to an image based mobile blogging site. How fitting Ajit :)

9th Jun 2008, 14:35

mat says:

11 architectures? I can't see them...

9th Jun 2008, 14:48

Alfie says:

There were some issues with the text portion of the post. Have added that content back in so it certainly makes a lot more sense now :)

9th Jun 2008, 14:58

mat says:

More sense, yes, but I wouldn't say actual "sense" is being made. There are certainly a lot of buzzwords, but I'm very unclear on the points (if any) being made.

9th Jun 2008, 15:11

Benedikt(www-dot-lewebmobile-dot-com) says:

There surely are many different architectures that the mobile web is being built on. iPhone, Symbian,

10th Jun 2008, 17:59 | edit | delete

Benedikt says:

Sorry about that. Trembling because of this cup of coffee and not having had enough to eat :).

Here goes another try:

There surely are many different architectures that the mobile web is being built on. The iPhone (OSX), Symbian, Windows Mobile, Palm's OS and Linux (Android)... (I'm counting 5) but will it really matter?

I can access my favourite webservices from my mac or any windows PC as well... that'll be the same for the web on the mobile, won't it?

10th Jun 2008, 18:08 | edit | delete

Alfie says:

The iPhone should just never be the first thing anyone thinks of when they talk about web on the mobile.

10th Jun 2008, 18:08

Alfie says:

Exactly Benedikt - it's simply not about the technology. Read Brian Sudas post for a bit of brevity relief.

10th Jun 2008, 18:09

anonymous says:

noooo way... what's going on today??? having finished off my comment i get to see "moblog:UK error" because i cannot post links without being logged in... no way to get my text back, dammit!

Anyways... back to where we were. Thanks for the link, Alfie! And we should definitely go for this diet.

Tarek (check his post on this site "what the iPhone can teach us about mobile web2.0" from June 6) makes a good point why we might just want to hold on to the mobile web term a bit longer.

He thinks that what we see now is web-on-mobile and that we are still lacking "web services that know which device is being used, knows where the user is standing, knows what the user likes and gives them a kick-ass user experience", which for him legitimates the use of this term.

IMO we don't need to call it the mobile web - because we don't call it the cookie web when sites remember that I've been here already - but why not? It certainly not only makes a point on what kind of information the service uses to give us a better experience, but also states a different set of needs (sugarfree!) that we need to take into account when developing for it.

10th Jun 2008, 18:46 | edit | delete

Add a comment


(P) what's this?

Track updates to this post with this rss feed