« Blog Home
1 Star2 Stars3 Stars4 Stars5 Stars
Loading ... Loading ...

A few months ago, an article was published titled Google’s search dominance, stating the following:

According to Masie, a sixth of all internet searches in South Africa come from mobile devices, the highest ratio in the world. To ensure that it leads in the mobile search market Google SA launched its universal search for mobile in January 2008 — only the fourth country in the world to get this service.

Indeed, mobile is going big. However, my concern is more of the technical type.

The relatively high penetration of the mobile web in South Africa was recently brought up again in an article titled The mobile web: an untapped opportunity for publishers. But for me, the following two paragraphs are particularly interesting:

Further, even when excluding internet browsing on mobile phones using the native HTML browsers now available in most high end cellphones or the use of special browsers like Opera MINI (Opera MINI converts regular web pages to render properly on the small mobile screen) the number of unique South African users accessing the mobile internet using WAP is already just about double the size of the number of users accessing the fixed internet.

[…]

A recent Yankee Group (www.yankeegroup.com) forecasts global shipments of mobile phones with native browser support for HTML browsing environments to hit 66% of handsets shipped in the 2012 calendar year — unfortunately though, the full browser skew will be in the high end phones and the number is therefore likely to be significantly lower in developing markets.

The question is which format(s) to expose. The WAE is the top layer of the WAP stack. The WAE can either be WML or XHTML Mobile. As far as I’m concerned, WML is essentially dead with XHTML Mobile being its replacement. However, it’s not clear which percentage of South Africans have access to only WML or also to XHTML, considering that it’s likely a very small percentage of them will have access to high-end phones.

If there is a significant part of the population with access to WML only, then we need to start catering for it. I have to be honest that I have seen very few new WML sites popping up, while I’m seeing plenty new XHTML Mobile sites popping up. Only a few hours ago, the new Zoopy Mobile launched, for example, which is XHTML Mobile 1.2 just like the Muti Mobile site I set up a couple of months ago.

To set up a mobile site is typically fast, easy and therefore cheap. But another challenge is multimedia formats, in particular video, and from what I can tell there is a general standardisation problem in that department at the moment. But the guys at Zoopy would obviously know much more about that than me. :)

So, the only time we will really know what we need to do is when we have proper user agent capability statistics, not just penetration ratios, otherwise we will keep shooting in the dark and perhaps exclude the greater part of our potential market.




Related Posts
  • None

5 Responses to “WML vs XHTML”

Hi Charl,

If I was developing a site at this moment I would definitely forget WML entirely. For example from Nokia all devices with a browser has supported XHTML-MP and a normal IP stack for quite a few years already. Just check Forum Nokia for example (http://www.forum.nokia.com/devices/matrix_xhtml_1.html).

Of course in Africa there is a portion of refurbished handsets that still support WML, but they are at the very low end of the pyramid and I don’t see a viable business motivation to cater for them.

(Report abuse)

Iikka on December 3rd, 2008 at 9:44 am

Interesting post, Charl. I haven’t heard WML discussed in awhile, but it’s a topic very much worth considering within the context of the developing world. When you ask ‘The question is which format(s) to expose’ I think the answer is “both”. I can only guess at the percentage of WML-only refurb handsets in SA, but I imagine there’s still a good number of them. Anecdotally, here in Cameroon I’d say the number of WML-only refurb handsets are at least equal to newer XHTML-capable models.

It’s fairly trivial to detect the device capabilities using an open source project like WURFL:

browser_is_wap){
header(”Content-Type: text/vnd.wap.wml”);
echo ”.”\n”;
}
?>

Of course, one useful feature of XHTML is it can be manipulated as XML, so you simply use XSLT to output device-specific code for each broad class of mobile device. It’s straightforward and requires little coding, so why not? This way your upmarket XHTML Mobile site is accessible as a WAP deck for users with old handsets.

This was a requirement just a few years ago in the US for mobile content partners with AT&T/Cingular Wireless when there were still a lot of extant WML-only handsets.

(Report abuse)

Bill Zimmerman on December 3rd, 2008 at 10:45 am

Design and implementation costs with xhtml would surely be a lot lower. Just throw in a stylesheet for mobile and a bit of device detection and you get a website and mobile site all in one. Why build for soon to be obsolete technology. Web penetration in SA (whether cell or land-based) doesn’t justify the effort.

The more important issue in any case is not so much about the technology, as ultimately anything is possible, but rather on navigation and content which need to very carefully considered as the way visitors interact with handheld devices is very different to the way they view a website.

Oh and lastly…SA programmers still need to be taught the differences between html and xhtml in any case!

(Report abuse)

steve on December 7th, 2008 at 5:11 pm

A very interesting blog – I’m having difficulty keeping up with the page definition standards, but then I’m just an average technology user…

Please look into you Chrystal ball and tell us whether there will ultimately be a simple information definition language. Will HTML/XML/XHTML ultimately evolve into a universal means of exchanging information. Will some other information definition language emerge.

Modern technology relies on standards that are universal. We have a number standard in Hexadecimal. Whether technology is based on an 8 bit or 64 bit processor, programmers use hexadecimal to understand and manipulate numbers. There is also a character standard. ASCII, developed from the teletext machine’s American Standard Character Set. It is used universally. Whether you are using an 8 bit microprocessor controlled washing machine or the biggest 64 bit computer, these machines will use hexadecimal and ASCII. ASCII has some fascinating legacy characters like 06H (Bell), 05H (Enquiry) and 0CH (Form Feed which is different from either 0AH - Line feed and 0DH - Carriage Return). In spite of these quirks, ASCII (like Castle Lager) has stood the test of time.

The notable similarity in successful computer standards is that they are simple, robust and they change little over time. They are universally accepted and are never dominated and manipulated by a single monopolistic player.

(Report abuse)

John Bond on January 5th, 2009 at 4:30 pm

I had no idea access of the internet via mobile phones was so high in SA.

Business owners in SA (or targeting SA) should make sure that their web developers are well aware of this when getting a website developed for their company need to take .

(Report abuse)

Ricky on January 15th, 2009 at 11:47 am

Leave a Reply

All comments must be approved by our editors, click here to read the editorial guidelines for comments. Please allow some time for our editors to approve your comment after posting.

Send me the Thought Leader daily newsletter

profile
Charl is a software programmer, open source enthusiast and all-round technology geek. There is generally a better chance of catching him working at 3 o'clock in the morning than 3 in the afternoon.
Technorati RSS
Charl's links
more posts
We come out of a tradition of Enterprise 1.0, these days sometimes known as “old-school business”. Then the focus shifted to social networks and E...
latest activity
Blog Statistics
Total reads 1510
Total comments 10
Charl's tags
advertisement
All material copyright of the author, or the Mail & Guardian, unless otherwise specified
Author Login
Afrigator