The Ideal Mobile Software Stack by Simeon Simeonov

By Simeon Simeonov

sim_blog.jpg

Note from Ajit:

This post comes from Simieon. The views expressed here are not 100% consistent with mine, however – this is the OpenGardens blog :) i.e. differing views are welcome – and in some ways – encouraged!. Sim of course, knows a bit about Adobe/Flash and Macromedia since he was vice president of emerging technologies and chief architect at Macromedia before joining Polaris ventures.(Polaris is a Tier One VC based out of Boston). Sim is also a good friend and is a contributing blogger to the OpenGardens

It was great to meet Simeon personally at 3GSM and we had a great time discussing technology, industry vision, technology trends etc etc. Sim attended my session at 3GSM on Mobile Web 2.0 and we discussed this post extensively before my talk. On the way back to my hotel and the location of the Ogilvy Telecoms conference (more on that later), we discussed more things tech related – it was surreal discussing ‘Sim’ cards with Simeion Simeonov Simeonov :) . So expect more such posts from Sim

Sim’s post follows …

I’ve written previously on the need for a better mobile software stack.

My ideal phone stack consists of Linux as the HW abstraction layer, real-time Java as the phone middleware and Flash Lite as the presentation tier.

I’ve gotten quite a few questions about this so let’s look at the problem more broadly (with the addition of AJAX as a possible presentation tier) and then layer-by-layer. I should start by saying that I have very little specific experience in phone HW/SW design. My comments are based on my experience with platform runtimes, N-tier architectures and developer ecosystems–most of which are gaping holes in the mobile space.

Some general observations, i.e., the set of my high-level biases about mobile:

• The mobile space is likely to continue its rapid evolution. Video is the new big thing. Location-based services (LBS), 3G/WiFi/WiMAX, advanced voice apps, security, advertising and others are on the horizon.

• Phone HW evolves quickly and there is increased pressure for it to evolve even faster to meet market timing needs. Being at 3GSM this week confirms this.

• Device capabilities are getting better. For higher-end devices, memory and CPU are rarely the constraints these days. It’s most likely I/O (screen + text input) and battery life.

• There is significant device fragmentation, which is likely to get worse because HW is becoming more and more tuned to the target market segment. Saw several companies at 3GSM offering mass-customization of phones for narrow demographics or affiliate groups.

• ODMs know HW. They don’t know SW. The big ones are learning slowly. The Tier 2/3 cannot invest enough to learn quickly.

• Most on-device software is pretty terrible. (Some favorite examples… Until the very latest Blackberry models came out you couldn’t forward emails as texts and vice versa, even though they are in the same inbox. A MOTO friend told me that RAZRs used to, perhaps still do, have separate inboxes for SMS vs. WAP Push messages. The WAP push inbox didn’t have notification so consumers wouldn’t know that they’ve received a link.) Take a poll. Who of your friends loves their phone software experience? More than 10+yrs after the arrival of the Mobile Web, the phone experience is predominantly still voice and text.

• Phones are increasingly adding 3rd party software, e.g., instant messaging clients, Flash Lite, on-device portals (ODPs), etc. It’s a struggle to integrate this software with the device given the tight market cycles. Very few companies, e.g., SavaJe and Open Plug, offer solutions in the space and none that I know have any significant traction.

• The closed garden walls are starting to come down, no question about it. Phones that support WiFi will serve to accelerate this trend. There are some very cool startups, such as Fonav, started by my friend Ram Fish, working hard to make this happen.

• Eventually, mobile advertising will work. I’m not sure exactly how it’ll happen and it certainly won’t happen as fast as some of the mobile advertising startups are hoping for but advertising will ultimately be figured out because content and not pipes is what attracts end-users, which would lead to an eventual opening of carrier networks, which leaves tapping the advertising/direct marketing value chain as the most obvious revenue model. Subscriptions won’t go away but there will be more all you can eat subscription plans, again, a trend confirmed by announcements at 3GSM.

• Mobile content is developed by a relatively narrow + fragmented ecosystem of about 1M developers. (It’s a very rough guess. I’ve asked everyone from MS to MOTO to Nokia to carriers about numbers and nobody knows for sure but they all agree that around a million is probably a good bet). There are probably 10+M non-mobile developers.

The biggest problem in the space from my naïve perspective is that there is too much friction in the mobile value chain. Friction increases the cost of experimentation and hence market entry. The result is a slower pace of innovation in the mobile space. Much of the friction is due to cultural issues and business models, a topic too big to tackle here. The rest is due to technology.

The first tech problem to tackle is the introduction of new phone hardware.

Once you have the HW you have to bolt on the SW. Traditionally, this has been done through hardcore hacking/porting of an embedded OS (for the cheapest phones), some modified version of Linux or one of the smartphone OSs, e.g., Windows Mobile or Symbian. Windows will do great in the enterprise because of the ability to integrate with the installed base of Office, SharePoint and Exchange users. Symbian is neat but I expect it to have difficulty becoming a dominant platform because, like Windows Mobile, it is proprietary yet it doesn’t have the demand pull that Microsoft can generate through its installed base. The rest of the world will want something cheaper, more flexible and less controlled by big vendors. This set of requirements will sound familiar to people who built appliances in the enterprise space. Their choice was Linux. The same set of forces will make Linux the choice in the mobile space. The current approach of hacking Linux to force fit it to devices will give way to a more architected approach with a meaningful hardware abstraction layer (HAL) supporting binary compatibility with the higher OS layers, akin to some of the work that startups such as A La Mobile are doing. The task of high- and low-level driver development will spread to the various component manufacturers, making the load bearable. This is the only sane approach to lowering costs and time-to-market on the HW/SW interface side, especially when one takes into account the ODM’s lack of SW skills. That’s an opportunity for third parties.

The mobile version of Linux should stop far short of the set of capabilities one would find in a desktop OS. There should be no focus on UI or even basic user services. Linux as an environment and C/C++ as the programming language are not the best-suited for this. I’ll grant that this is an arguable point. Most of the very cool mobile/embedded UIs (from the iPod to the early Blackberries) are done in C/C++. However, I see that primarily as an artifact of history. By the same argument, one can say that the best user experiences on the Web are done using plain HTML as opposed to Flash/AJAX but that would be ignoring the trends. C/C++ fail what I call the ecosystem test.

The second tech problem to tackle is the integration of various phone services into a flexible, manageable, extensible on-device service delivery platform.

Think of it as the API into the phone but not in a fixed (these are objects/methods) way. Instead, think of it as something akin to a mini-SOA architecture for the phone without all the runtime overhead because the environment is constrained. Does something like this exist right now? Not that I know of but it should. (Open Plug and similar companies offer dynamic binding upon application/service installation but do not go all the way to dynamic service discovery and invocation.) Without this type of abstraction layer, building applications that leverage phone services and integrate them together becomes much harder. Upgrading services may or may not break applications.

Conversely, upgrading applications to take advantage of new services would also become harder. It is important for applications to plug into this layer and expose their own set of services to the phone and other applications.

Let’s look at some examples:

• You install a new IM client. It registers as a texting and messaging service with the phone, allowing you to forward texts, emails and pictures to your IM buddies, even though the texting and emailing apps never considered the existence of IM as a way to exchange messages.

• You download a Skype client to your phone. It should be able to integrate with phone features controlling microphone, speakers, and call services. If allowed (by the user, operator, …), Skype could become a callout service + integrate with your address book + more. If so configured, Skype voicemail should be able to trigger the phone voicemail indicator yet not interrupt how phone voicemail is processed.

It’s not easy to build this layer in the phone since it has to encompass telephony services (both on the cell network and VoIP), broadcast services (mobile TV/video), data services (real and non-real-time over the cell network, WiFi, WiMAX, etc.), etc. It has to have real-time dispatch and event processing capabilities. It has to have a strong security model. It has to have easy to document/use APIs and fit SOA concepts well. It has to target a large, existing, globally distributed developer ecosystem armed with good tools. Some standard set of frameworks/services built on Java seems to be the only viable answer for the time being. And it has to be small and simple enough to run on common phone platforms.

MIDP2/3 are not relevant here in the sense that there is no UI involved. This is truly a multi-threaded middleware layer, making the phone HW and installed applications work well with one another. My guess is that J2ME CDC should be sufficient.

The final layer in the proposed three tier mobile stack is the presentation tier.

The requirements for a good presentation tier are that

(a) it can generate engaging user experiences on target devices and

(b) there is a ready ecosystem that can deliver content and applications to that presentation tier. The latter point is, in fact, the most important one, getting back to the ecosystem test and the claim that content, broadly speaking, rules in the end. Ecosystems take years to build out and nobody has time for that.

Java goes out the window when evaluated against these requirements. There are very few examples of truly engaging user experiences developed with Java. There are not many developers who know how to develop these. Most of the people doing UI work with Java have been in the enterprise domain. This issue isn’t that you can’t build cool mobile apps on J2ME, it’s that there aren’t enough people who know how to build lots and lots of them.

Realistically, there is only one broad community of developers to tap into to grow the supply of content and application in mobile in a big way and that’s the Web developer + designer community. The designer/developer role split is very complementary for consumer experiences. A mini-app (widget) or a container for some interactive content, e.g., a video with some interactivity, can probably be handled by a designer type with some development ability. More sophisticated apps (say an IM client for the phone) will be developed the same way they are done on the Web–interactive designers architect the core of the user experience and graphic designers + developers fill out the pieces on top of the middleware architecture/services provided by the phone.

The Web 1.0 experience, with its constant page refresh cycles, is poorly suited to the low bandwidth, unreliable wireless networks. That’s why most WAP/WML mobile sites suck. Even Google has switched to downloadable clients for its mobile apps.

The solution is to go the way of Rich Internet/Mobile Applications using either DHTML + AJAX or Flash (Lite).

Neither is a perfect choice in the short run. As a side note, it is important to notice that this presentation tier runs on the phone, not in the browser. It is the phone UI, while the browser is just one of the applications. Ideally, it will include the phone top. MSX is a good example of a company developing flexible phone tops using a high level of abstraction.

Whether Flash Lite or AJAX ends up with a dominant market share in the future is a topic worthy of another post. Both have strengths and weaknesses. My personal bias puts me closer to Flash, yet Ajit makes a very compelling argument as to why AJAX is the better chance in the long run in his post Flash Lite is not WICD but it should be . The biggest problem on the AJAX side is fragmentation—there are too many browser limitations and incompatibilities right now even when one considers the high-end offerings such as Openwave’s MIDAS or the Opera Platform. I don’t expect these to get resolved for years–just look at the problems that PC browsers have had over the years.

Efforts such as mojax, may play an increasing role in this space, especially since mojax, through its J2ME implementation, is exposing lower-level phone capabilities to the presentation tier.

mojax is one of the worlds first Mobile AJAX Application Frameworks. Unlike traditional AJAX Web Frameworks, mojax Moblets do not run within a browser and are not subject to the availability and quality of a network connection. Also, unlike a web application running on a mobile device, a mojax moblet has access to lower level device features such as Camera API, Push Messaging, Bluetooth, Location Services, Contacts and more.

Flash Lite offers great tooling and consistent runtime capabilities/experience but that comes at the cost of slower market penetration and a higher minimum bar for device capabilities.

Flash has several things going for it:

• There is a thriving ecosystem of 1.5+M Flash designers + millions of developers who know how to use what the designers give them. There are dozens of ISVs in the third party ecosystem.

• There is extensive tooling for both designers and developers, including runtime platforms for general applications (Flex) and specific content delivery platforms for carriers (FlashCast).

• Adobe takes a broad approach towards user experiences, including, for example, audio and video as part of the experience. This is why they bought ActImagine in 2006.

• Widgets and smaller apps can offer the same user experience online and on mobile. For example, Mobitween’s games run off of the same codebase on phones and in PC browsers.

Japan is the showcase market for Flash. I’ve heard of staggering differences between the monetization of rich (Flash-based) vs. static content there. Outside of Japan, Verizon Wireless is the showcase operator pushing Flash Lite. Adobe must be very close to ironing out additional deals or there would not have been the contingent of CxO and SVP execs I saw at 3GSM.

The two main things going against Flash are the minimum device capabilities and the price. Moore’s Law helps with the former but not fast-enough. For years Macromedia under-invested in figuring out how to get Flash to feature phones. Now it is an important target for Adobe. Some have raised concerns about Flash Lite being proprietary, closed-source and expensive. All valid points to the extent that it would be more desirable for there to exist a free, standards-based, open-source, ubiquitous, rich mobile device presentation layer. I’ll take that and world peace anytime :) . Delivering and maintaining software across hundreds of mobile devices requires significant investment. I don’t expect to see Flash Lite or the good AJAX-enabled mobile frameworks becoming free anytime soon.

It’s interesting to wait and see where open-source efforts such as mojax end up. My expectation is that they’ll do great on features and will suffer where performance and quality are concerned–those have typically not been the strengths of the open-source community. Unless ODMs and operators contribute significant resources to these projects, it’ll take a long time before they are ready for prime time.

So there it is–the mobile stack of the future: Linux as the OS, Java as the middleware on the phone and Flash/AJAX as the presentation tier.

There are a number of startups working on the Linux front. The Java piece is probably the most scarce in the industry. Apart from SavaJe, no one has done serious Java work on the phone. The presentation tier will be the playground of large vendors (Adobe, Openwave, Microsoft) on one hand and also developer-focussed companies like Opera and Trolltech on the other hand (because they have been historically close to the developer community thereby mitigating to an extent the high costs of ecosystem development and developer marketing).

Finally, it makes sense to ask the question why would operators, especially the large ones, who ultimately control the mobile stack want to move in this direction. Some answers are:

• Lower costs, both for getting new devices operational and for evolving on-device and network services. Also, application certification costs go down significantly.

• Faster time to market, again for both devices and services that integrate with the handset.

• Greater monetization potential of subscribers due to the availability of more content and applications, especially niche content and apps, which are of relevance to niche audiences.

These become particularly important in a world where mobile search and advertising are starting to take a foothold.

Experience migrating to wordpress from movable type?

Does anyone have any experience (or can recommend someone) who has migrated

to wordpress from movable type?

I think movable type is really not listening to its customers.

Simple things like comment management lead to a lot of work for example:

wordpress has features like entering a keyword v.s. movable type which forces you

to use a typekey service – not in my interest or the interest of my

readers!

A new version of Movable type is out but don’t see anything great in it – so now I am

seriously considering migrating to wordpress!

Please email me at ajit.jaokar at futuretext.com

kind rgds

Ajit

Happy Chinese New Year to our readers ..

chinesenewyear.JPG

Happy Chinese New Year to our readers !!

Image source: BBC

Should we have a .wii domain? A case for One Web

At the session I chaired at 3GSM, Jon von Tetzchner Chief Executive Officer Opera Software, had an insightful question to the audience:

Should we have a .wii domain for the Nintendo Wii

The answer ofcourse is no!

But it does illustruate the point very well that there can be only one Web

And a caveat: The Nintendo Wii runs the Opera browser

Tim Berners Lee keynote at 3GSM

For many attendees of 3GSM, Tim Berners Lee’s keynote was an important hightlight of the conference. The full text of the speech is as per the link HERE. I have reproduced the text below and highlighted the bits which I have found insightful.

The Mobile Web

Ladies and gentlemen, it is a pleasure to be here today. I must say I cannot claim to be an expert in the mobile phone technology, so I speak as a guest in this conference. My career for the last 20 years has unrolled in the context of the Internet. What I find exciting about being here now is that we are at an epic point in telecommunications history, when the mobile platforms discussed here, and the Internet platforms which have enabled such a spectacular growth and innovation, are poised, if we manage this well, to merge.

In the few minutes we have together, I would like to explain to you the essence of an open Web platform — the things without which it would not deserve the name. I would like you to understand that there are plenty of ways in which we could fail to pull this off, and leave ourselves incapacitated, with innovation stifled. By ‘we’ here I mean the whole community of manufacturers, service providers, content providers, consumers, and to a limited extent, legislators. I’d like you also to feel with me the excitement about some of the incredible things we can aim for if we succeed.

Let me tell you where I am coming from, to help you understand my point of view. Twenty years ago, or 52 Web years as we used to say, I was a software engineer at CERN, the particle physics lab in Geneva. CERN is a great place, full of people from across the world tackling the greatest current challenges in physics. It is a great place to work, with lots of very creative people who chat over coffee with views of the vineyards and the Alps.

Now, this diversity of talent had brought with it a diversity of technology. This is pre-Web. Take your minds back — perhaps, younger ones, ask your parents. There are documents stored on computers — papers, manuals, help systems, letters, but each system works on one particular computer — minicomputer, mainframe or PC or Mac in those days — and runs on one particular operating system, VMS, VM-CMS, DOS, Mac OS, and many flavors of Unix. So finding a document involved finding out which computer it was on, knowing which program to run, and learning how to use that program. This was driving me crazy, and by 1989 I’d figured out that a networked hypertext system, a kind of Web, could be used to wrap up each system and make its screens, menus and documents be part of a globally interconnected space which could be viewed from any computer.

Also, just at that point, a critical transition was occurring. Each computer had been connected to a different form of network: Decnet, Cernnet, Bitnet, Appletalk, and so on. The attempts to rationalize these using ISO standards was not doing well. However, the Internet was already connecting universities all over the US. Depending on who you talked to, it was just becoming respectable; it was also becoming possible to connect computers to it at CERN.

I wanted to design the World Wide Web, as I decided to call it, to be usable for any data on any system. I had watched the failure of so many sophisticated documentation access systems which constrained their users to use one type of computer, or operating system. If really anything could be on the Web, then the Web technology should demand almost nothing of its users.

The reason that I could just design the Web by myself and set it running on a couple of computers without asking anyone, was that the Internet in turn had been designed to be used for anything, constraining its users as little as possible. So this is one of the qualities of an open platform: it is built to enable, not to control, and it does not try to second guess the things which will be built using it.

The Web is designed, in turn, to be universal: to include anything and anyone. This universality includes an independence of hardware device and operating system, as I mentioned, and clearly this includes the mobile platform. It also has to allow links between data from any form of life, academic, commercial, private or government. It can’t censor: it must allow scribbled ideas and learned journals, and leave it to others to distinguish these. It has to be independent of language and of culture. It has to provide as good an access as it can for people with disabilities.

The Web worked because of a number of technical and social reasons. It worked because there was no central bottleneck for traffic, no central link database to be kept consistent, no central place to go and register a new page or a new Web site.

It worked because it was valuable, in a novel way. The value added by the Web is the unexpected re-use of information. People learned that if they went to the trouble of putting something on the Web for some reason, that others would benefit later in ways they never anticipated. The experience of surfing the Web, which blew some of the early users away for days and nights, was of discovering things you never knew existed.

So the Web worked. How many projects do we start which have a bright start and fizzle out over time? So many that it is worth celebrating that the Web worked. It is worth noting why. A lot of that has to do with the open Internet platform.

Let me mention one important aspect of the platform. The serendipitous re-use of information happens because when I buy an Internet connection, I don’t specify the Web sites I am going to connect to. If you buy an Internet connection, and you run a Web server, then I can connect to your site. I don’t find my ISP saying that it wants to be my supplier of music, and so it will block access to any site I try to load music from.

This is of course different from the model which the cable companies have had. The relatively recent ability of the Internet to carry video promises to really open up the movie delivery options, and provide an exciting new world of anything on demand any time, and not just anything we currently get from a few large companies, but the long tail, the seething mass of individual and independent films which are waiting to entertain someone out there. When a US cable company threatens to attempt to stifle this aspect of the open Internet platform, we have defended it as Net Neutrality. Net Neutrality was so much of an obvious technical and social prerequisite of the Internet world, that it never needed a name until now. It is a tension of convergence, where different business models and cultures may clash. I am confident that Net Neutrality will be preserved, for the good of us all. But I would urge you to support it whenever you get the chance.

So what else does it take to make an open Internet platform?

What does it take?

It takes, mainly, common standards. The innovation of the WWW was possible because the standards for TCP/IP were already implemented in an interoperable way all over the planet, in advance of the innovation. TCP/IP wasn’t designed with networked hypertext in mind. But it wasn’t designed to prohibit it either — it was and is an open platform.

Web 2.0 community Web sites, eBay, and Flickr are possible because the Web standards, in turn, were widely implemented in an interoperable way, before those innovations. The same for the wikis, like Wikipedia, and blogs, and so on. The Web is a huge platform for innovation because of those standards. Any new genre of communication, any new social networking idea, immediately can gain the value of unexpected re-use by people across the world.

There is a very important difference in attitude between a foundation technology and — well — let’s call it a ceiling technology. A foundation technology is designed to enable innovation, to be the base which will support other even more powerful things to come. A ceiling technology is not. It is designed to provide a value, and for its provider to cash in and cash out. Proprietary music download systems are ceiling technologies to the extent that the technologists design to be also being the only store in town, rather than creating an open market. Though putting a lid on further innovation, they are still providing a service, and making sure they profit from it.

Ceiling technologies are the end of the road for innovation.

When you want to make a foundation technology, you need to look ahead. You need to put aside the short term return on investment questions and look at the long term.

A great example of this is the patent question. In 1989 my colleagues in the Internet community would not have dreamed of patenting the ideas in the Internet protocols. We worked together to figure out new ideas, and implement them as common standards. As the Web grew, we realised we needed to establish a structure for developing common Web technical standards. In 1994 we formed the W3C as a meeting place for this process.

In 1998, we had launched a project to help with the issue of user privacy on the Web. It was a protocol (P3P) to allow a Web browser to automatically read and check a machine-readable version of a Web site’s privacy policy. It was not a very exciting new technology, but it was an important innovation as electronic commerce was being held back in some cases by user fears in this area. At the time when we should have been engaged in deployment and testing, a small company announced that everyone who wished to make a P3P implementation would have to pay royalties. They claimed to have a patent on something to do with information being communicated and stored and affecting future communication.

This has a devastating effect. Anyone working for a large company was told by lawyers never to read anything to do with the work. Anyone working as a volunteer in their garage dropped their work on these tools as they didn’t want to work for free for this company. The mid-sized companies who were running a business specifically around the technology ran into serious trouble. It took us 18 months and $150k to get a legal opinion that royalties were not in fact payable, but that was 4 Web years, during the boom, and that was too long. P3P lost its momentum. The world lost an enabling technology.

How does a company think about standards then if following them may involve losing that short-term ceiling technology return?

It is a game. In the mathematical sense. Here is the payoff matrix: You commit to working on a standard, or not. The standard may take off or it may not.

If you don’t commit to the standard, and it doesn’t work, (which of course it won’t if no one else does) then life, and your proprietary ceiling technology, continues. No innovation.

If you do commit to it and it it does work, then a whole new market is enabled: This is the disruptive case. There is some effort involved moving the company to the standard, and often to help build the standard. You might join W3C to help make it happen. A certain amount of effort. There is a major long term return.

One of the most difficult things for some companies to learn is that this is not a zero-sum game. We are so used to battling over a fixed market, or battling over fixed resources, that we tend to assume everything is such that we can only win what our competitors lose. But when we make a whole new market space, like the Web, or like GSM actually, then we are in fact together battling the human condition such as inefficiency, poverty and ignorance.

Now, what about the corner cases? The fear seems to be of going for the standard and it not taking off. Well, the loss in this case is the engineering time to tool up for the standard, which could have been saved. But it is a very finite loss.

On the other hand, what if you decide not to go for the standard and it does take off? Everything happens, the new market appears, and you are not there. The pace of everything ramps up dramatically, and you are left standing still. The costs of retooling to a standard get much bigger as time passes. In this conference we all can see the stresses on phone companies, and we know the dis-empowerment of all travelers from the fact that the GSM standards and frequencies are not quite global — and we know the benefits from the fact that are becoming so. Other cases spring to mind. On the Internet, for example, streaming media are available in many incompatible formats.

Often this is due to companies wanting to profit from ceiling technologies. This involves making a high income from the technology itself rather than letting it take off. This in turn requires patents, and of course that the owned technology dominates. Hence the battles over VHS and Betamax, HD DVD and Blu-Ray, and so on.

So as the Web platform and the mobile phone converge — what do we want the result to be? A foundation or a ceiling technology? Clearly, a foundation. A mobile phone — or whatever device we carry around which uses GSM technology and its successors — is going to be everywhere, and everyone will have one. It has do be designed to be universal. So that everyone can use it. So that you can do anything with it.

The choice is the new platform being a privately owned walled garden, or a competitive open platform. Both models can work in the medium term. But the open model opens up new things which we can only try to imagine.

What are the standards? Basically, the same standards as the current Web uses. That is the most important point. It is one Web. The Web works on phones. There are effective browsers which can give you access to the same information which you could see from any laptop or desktop. Of course, looking ahead, small devices will get smarter and displays will get more and more pixels, so mobile devices are taking the same track which larger computers did a few years before.

That said, there are ways of making a Web site work much better with a mobile device. The W3C’s Mobile Web Initiative (MWI) is a group of mobile technology companies within the World Wide Web Consortium which realize the importance of this convergence and are working hard to make the Mobile Web a reality.

MWI defines best practices for authoring content. It defines what sort of facilities that you should expect to find on a mobile device. It gives best practices for serving data in the most device-independent way. It recommends finding out what device you are talking to if you can, and sending appropriately formatted content. Some phone browsers set out to be able to provide access to virtually any Web page, but technical limitation on other phones make this impossible. To encourage Web sites to become easily browsable by mobile devices, there is a “mobileOK” mark which may be used by content providers adhering to guidelines.

Designing for the “mobileOK” mark, designing Web sites which are browsable by many different sorts of devices also has important spin-offs. Many of the MWI best practices are in fact good Web design principles, so the whole site will be easier to use for anyone. There is a also a lot of overlap with accessibility. Making a “mobileOK” site and making one which is easily used by people with disabilities involves the same sort of work.

From the beginning, The W3C has fought the “best viewed with 800×600 screen” buttons, and any design patterns which disenfranchise different devices. This was difficult when everyone seemed to have the same sort of laptop, but easier as it became obvious that screens vary a lot. The Mobile Web Initiative is the work we have to do now. It is timely, it is part of a historic convergence of technologies. But it is part of a general strategic principle of keeping the information which is such a huge form of capital in the world in as powerful, and reusable from as we can, for the future generations and people who don’t currently have access.

It isn’t just about making the Web you know today work on mobile phones. We are talking about innovation. The innovations which will really count are the things which I can’t imagine now. They may include new applications built using the familiar AJAX technologies used cross-platform now, well known by developers, and increasingly available on mobile devices. These new applications may also operate across multiple devices. This is where we talk of the Ubiquitous Web. Have you noticed the price of LEDs is coming down, and more and more surfaces are covered with them? Not just at rock concerts and Times Square, but coming soon to all kinds of surfaces near you. Your phone could use these displays, and the abstract task you are doing can really rise above individual devices. Imagine that my phone or my wristwatch has details of a flight I am booking, and I walk into a room where it negotiates to project a map on the wall. And so on. Imagine yourself. Innovate on the mobile Web platform.

Among other things, many of us are hoping that a low-cost open platform will have a much greater penetration in what we currently call the developing world. I personally believe that it is important to humanity to connect peoples across the world as widely as possible. I think we must preserve the diversity of cultures and ideas. But also I think we must connect people to give more global harmony. We should not add connectivity to the long list that the richer countries have and the poorer ones do not, a list which of course has clean water, health care and peace pretty near the top.

As part of the Mobile Web Initiative, W3C held a workshop on the Mobile Web in Developing Countries. One of the concerns is that some of the new phones aimed at the lower cost bracket don’t all have Web browsers. The area is very exciting, and the figures for coverage — 80% of the world’s population I have heard (World Bank, according to Wikipedia), and for market growth in developing countries seem very positive.

So when we look at the choices for the mobile devices, it is clear that they must continue on the path to an open Web platform. That is what the Mobile Web Initiative is about. Huge new markets, and huge opportunities for humanity, depend on this. We know in general how to do it. But there is a lot to do. It has been my pleasure to take a tour of these issues with you, you who are the companies and individuals who are making it happen.

Feedback on my talk at 3GSM ..

3gsmlogo.JPG

Hello all,

It was great to meet so many of you at my 3GSM session – many meeting me for the first time.

From the feedback I have been getting, it went great! This was my first attempt at chairing a session and also speaking at it, and it was certainly well attended and with good Q and A.

Ofcourse, I was fortunate in having a great panel in Jon von Tetzchner Chief Executive Officer Opera Software, Alex Kummerman Chief Executive Officer Clicmobile and David Wood Executive Vice President, Symbian Research. Thanks Jon, David and Alex and also Byrne Harris and his team at 3GSM

If you attended it and want to leave us some feedback, please contact me at ajit.jaokar at futuretext.com and I shall post your comments here(both positive and negative!). I am also happy to link back to you. (I have had some problems posting comments on this blog which I am trying to fix, so to be safe please email me)

Besides readers of my books and this blog, many forumoxford members attended it and below is some feedback from forumoxford member David doherty of 3gdoctor

Thanks for the feedback David and its nice to be compared to Tomi :) . I shall try and get the presentations and post them.

For the people who couldn’t attend i wanted to let the forum know that today i was in the audience at the Technology Breakout Session moderated by Ajit Jaokar that was contributed to with presentations from the likes of Operas Jon Bon Tetzchner & Symbians David Woods.

I wonder if Ajit could possibly provide the forum with his and the presenters slides so they too can benefit from these excellent insights?

The Symbian presentation was best in show and Ajit really set the tempo to leave more than enough time for participation (which has sadly been absent from most of the other sessions). Last time i had so much fun at a 3gsm was when i first discovered Tomi Ahonen – pacing up and down in his keynote address at Cannes re: churn management of hidden alpha users.

Well done Ajit…

Mobizines

mobizines1.JPG

We are trying a new service called mobizines. The service is operator agnostic and free (aside from data usage). You can get the Mobizine by texting “mobi opengardens” to 63333 (+44 7624 806310 from outside the UK).

If you have any problems with the installation, check out the faqs and then try dropping an email to help@mobizines.com. They are quick to respond to queries. We will be doing this on a trial basis for 6 months and it will be interesting to see if this is the way to mobilise a blog. We will also be exploring other ways. Please let me know what you think of this experience if you try it out.

According to Mobizines, the data usage is as follow

Data Usage: The Mobizines service is free to the end user aside from normal operator data costs. The Java and Symbian versions of the service use different amounts of data which are outlined below.

Java Version (most phones)

Initial Download – 150KB one time

Mobizine Edition updates (3 per week) – about 35KB each update

Symbian Version (Nokia smartphones)

Initial Download – 900KB one time

Mobizine Edition updates (3 per week) – about 35KB each update

For more information on Mobizines, see the mobizines site. For more informaton on Refresh Mobile, who produce the Mobizines service visit Refresh Mobile. Check out some of the other mobizines include the BBC, Maxim, GQ etc.

Discounted book offer from futuretext for 3GSM ..

I used to carry books to conferences – and that was a pain! So, now we have simply decided to give discounts when major events are on and our authors are speaking. So, see the main futuretext site for a deal where you can get 50% off Mobile strategies if you buy Mobile Web 2.0

.mobi : Darwin Rules on the Mobile Web

Editor’s note from Ajit: In November last year, I was invited to attend a W3C meeting in Paris relating to the Mobile Web. In that session, I heard a presentation by Ronan Cremin of mtld (the company behind the .mobi initiative). .mobi has had a lot of bad press. So, my view of .mobi then was ‘neutral’ i.e. buy a dot mobi domain for defensive reasons.

However, Ronan’s presentation made me realise that .mobi is more than the domain name. In other words, a ‘money grabbing’ way to do this would be to sell the domains only and nothing else. However, even if you don’t agree with the business model, I think we have to agree that .mobi has made some efforts to provide an ecosystem – especially in view of some of their documents like the Switch on guides

So, my take on .mobi is

a) They follow w3c standards

b) They are doing more than merely selling domain names

c) Some form of consistency is good for the industry

d) I have a lot of respect for some of the technical people involved with it : for instance Jo Rabin

e) It helps the Mobile Web(which is a good thing in my view)

f) I am neutral to the business model. I.e. taking a pragmatic approach, if mTld makes money from selling domain name – but also helps the industry – that’s OK by me.

My criticism, if any is: its focussed on the lowest common denominator(and that is to be expected of any standard). My real interest lies in the other end of the spectrum(for instance browsers running full Web standards).

In Paris, I told Ronan that I would blog about .mobi from a neutral perspective i.e. discussing .mobi from a holistic perspective and not just the domains.

A few weeks ago, when I asked for guest bloggers, James Pearce, CTO of mtld, offered to write something about .mobi. So, considering I was going to blog about it anyway, here is an article from James.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

james.jpg

James Pearce

CTO .mobi

I was recently asked what I thought were going to be the major mobile web applications of the future. I could have been brave. I could have been visionary. I could have rattled off some old cliches.

But instead I said “I don’t know”.

And I’m proud that I don’t know.

Here’s why.

It must be almost 10 years since people started talking about ‘killer applications’ (and about 9 years since they stopped again). Then for a while it was ‘killer baskets’ – with the realisation that, in a sort of early form of ‘long tail’ thinking, people might actually want to do more than one thing. Then the web and mobile web markets went into free-fall for a while. And presumably people were busy looking for ‘killer job security’.

But me? I believe in ‘killer ecologies’. It is more important that we get the environment right for the healthy, stimulated development of the mobile web, than that we naively try to predict who the winners of the future will be, and give them some sort of false, pre-emptive credence.

The best successes are often the things you didn’t predict or that didn’t fit the obvious predictions.

“Anything But Stocks News Or Weather” as I used to say.

(I can also imagine, in the mid-90s, the strategy teams within hallowed ‘walled garden’ internet service providers trying to guess and promote what the next big thing on the web was supposed to be. Think they guessed auctions? Bookstores? Blogging? Social networking? Video sharing? I doubt it.)

So where does Darwin come into this?

Well, I’m no biology graduate. But no-one can doubt that the principles of evolution and the survival-of-the-fittest have served the animal and plant kingdoms extremely well. Add water, oxygen and food. Wait a million years. Bio-diversity flourishes. Different species compete.

Those which are best suited to their environment succeed. Those which are not do not. There’s (probably!) no intelligent design.

And nor should there be on the mobile web. Why can’t similar principles shape the way that content providers (as potential ‘killer species’) evolve? Of course, I’d rather not wait a million years ;-) . But I firmly believe that the most important thing right now is the metaphorical

water, oxygen and food to catalyse our ecology into life.

What might this mean practically?

Well, many miles of blogs have been written about the emergence of flat rate data tariffs, and the crumbling of operator’s walled gardens. Perhaps that’s the oxygen we require. Nothing but highly specialised lifeforms can survive in sulphur dioxide!

Water? Perhaps that’s a constant stream of tools, technologies, platforms, assistance, and community support that the developers of content and services require to be able to compete effectively. On the web, the technical barriers to entry were, and are, low. We need to

ensure it is just as easy for folks to get to compete on the mobile web too – even if that comes at the expense of ‘mobile specialists’ who benefit from sustaining the mystique.

(This is where we, the dotmobi company are putting a lot of effort. As well as providing mobile-centric domains, we are trying to democratise the process of building applications for the mobile web, making it easy for developers to find training, advice, and tools – such as

http://dev.mobi and http://ready.mobi – to do so).

And food? Well, I strongly believe in the two important economic lubricants for the mobile web: advertising and payment. Just as food does in a Darwinian ecology, these both motivate content providers to get involved in the race for life, and then sustain them once they have

become a successful part of the (ahem) circle of life.

Most of all I believe that no-one can play god on the mobile web. Not operators, not content aggregators, not device manufacturers. Especially not the dotMobi company :-)

But I truly hope that, if we all realise that we have responsibilities to provide water, oxygen and food, we will be able to stimulate a ‘killer ecology’ that accelerates towards becoming self-sustaining and rich in bio-diversity.

That’s important. Because the more developers and content providers we can introduce into the complex biological equation, the more that the natural selection of market forces takes effect, and the better the best-evolved of the species will become.

And that’s only going to result in more and more innovative, exciting – and unpredictable (think duck-billed platypus!) applications that genuinely drive interest and usage of the medium.

After all, that’s what users want. That’s what all of us in the industry want. And of course, that’s what Darwin would have wanted.

User generated content seems to be the focus of 3GSM ..

Early days .. but User Generated content seems to be a big focus of 3GSM. This makes me happy ofcourse since UGC is the core theme of Mobile Web 2.0 and also my talk at 3GSM

As pe the BBC

User-generated content, mobile TV and location-based services are all likely to cause a buzz among the 60,000 visitors. With one billion handsets sold last year, it is certainly in a healthy state but the majority of customers are still stuck in a talk and text world. For Ben Wood, director at research firm CCS Insight, this year’s conference will be the start of the journey to really bring the web to the mobile phone.

and also .. consistent with my own views ..

Flat-rate charging for data downloads is already happening – with 3′s bundled X-series service for example – and there will be a glut of handsets with better colour screens and more memory to persuade users to make the transition from voice to data.

I am also watching the announcement fom Nokia: Nokia Web Browser with Mini Map

The Nokia Web Browser with Mini Map enables mobile discovery of videos in websites such as the YouTube Mobile site in a similar way as with PC web browsers. With YouTube Mobile now also compatible with the AVC video format which is the most common format supported in mobile devices, the single-click playback of videos is also possible in the same intuitive way as with PC web browsers. The Nokia Web Browser with Mini Map and AVC video playback are standard features in all the latest Nokia Nseries multimedia computers.