I was optimistic about .mobi, as there are some huge companies behind it, but THIS ARTICLE has changed my opinion about .mobi
Should we really invest in .mobi??
Anyway, heres the article??
.mobi â Kickstarting the Mobile Web, Or Holding It Back?
The .mobi mobile-specific domain has been getting some attention this week since its sunrise period for registrations of industry-related companies began yesterday. Its backers contend a mobile-only domain is needed to push the mobile Web forward, but .mobi could end up doing more harm than good.
The Wall Street Journalâs got a typical mainstream press article on .mobi, accepting the marketing hype behind it without question. The party line behind the domain is that it will make mobile surfing easier and better for users â âDot-mobi makes the Internet work on phones,â says the CEO of the company behind it â but this isnât as true as theyâd have you believe.
First, the domain .mobi itself isnât particularly friendly for mobile devices, as plenty of people have pointed out. Thatâs something of a superficial complaint, but a relevant one nonetheless.
A bigger issue is the idea that somehow having a mobile-specific domain will make it easier for people to find what theyâre looking for on their mobile device. This isnât necessarily true â it just shifts the question from âis it mobile.x.com, or x.com/mobile, or wap.x.com?â to âdo they have a .mobi site?â And thatâs assuming that somebody is going to back up .mobi with a massive marketing and education campaign to make the general public aware of its existence.
Also, one of the stipulations of the domain is that registrantsâ sites will follow certain rules, or theyâll be shut down. My first objection to this is that domain registrars shouldnât be in the business of dictating content, as it sets a very dangerous precedent, but thatâs an ideological argument for another time. One of these rules is that .mobi sites must serve an entry page coded in XHTML-MP, unless the site detects a user agent that calls for a different flavor of markup. One point is that if a content providerâs audience has a need for one type of markup â say, WAP â thatâs what they should be able to use, user-agent sniffing or no. But you canât help but feel that this implicit preference for XHTML-MP has some other motives when you read a quote from a Nokia spokesperson saying âPeople have to have new reasons to buy new phones. Thatâs what we hope to happen here,â about .mobi.
So if weâre going to fall back on user-agent sniffing, why bother with .mobi at all? Weâd be better off encouraging sites to simply sniff the device with which users are browsing, then serving them relevant content â and all from existing, familiar addresses. Of course, smart companies and content providers are already doing this, without spending the extra money and resources on a .mobi site. Iâm hard-pressed to think of an example where having a mobile-only site on a mobile-specific domain is preferable to sniffing user agents.
Hereâs where the potential downside of .mobi comes in. The biggest risk is that site owners will buy a .mobi domain, throw up an XHTML-MP site, and leave it at that, thinking theyâve got this mobile thing sorted out â after all, theyâve got a site using .mobi, that thing thatâs supposed to make the mobile Web happen. But that strategy is really no better than putting up a WAP site a hard-to-find address. Theyâre both strategies that are more exclusionary than exclusive, leaving the hard work up to the end user, when it could better be done on the side of the site.
The bottom line for mobile Web surfing is that all users need to be delivered the information they want, regardless of their device or browser, or what address a content provider decides to use. Best case scenario, this means a mobile user goes to X.com, and gets served up a page formatted for their device. If that technology isnât in place, they should get the standard HTML page, and their browser should be able to handle it. Adding another address possibility that users have to try really doesnât do anything to help. .mobi has highlighted some best practices for the mobile Web, and site owners should take these into consideration. But they can (and should) be implemented separately from a .mobi address. Why introduce more confusion for users and pass it off as making things better for them?
(As an aside, if .mobi expects people to take their message of enhancing mobile usability and improving the experience of mobile Web users, they should start by improving their desktop site, which is laden with annoying and unnecessary PDFs and Word documents, and links opening in new browser windows.)
Should we really invest in .mobi??
Anyway, heres the article??
.mobi â Kickstarting the Mobile Web, Or Holding It Back?
The .mobi mobile-specific domain has been getting some attention this week since its sunrise period for registrations of industry-related companies began yesterday. Its backers contend a mobile-only domain is needed to push the mobile Web forward, but .mobi could end up doing more harm than good.
The Wall Street Journalâs got a typical mainstream press article on .mobi, accepting the marketing hype behind it without question. The party line behind the domain is that it will make mobile surfing easier and better for users â âDot-mobi makes the Internet work on phones,â says the CEO of the company behind it â but this isnât as true as theyâd have you believe.
First, the domain .mobi itself isnât particularly friendly for mobile devices, as plenty of people have pointed out. Thatâs something of a superficial complaint, but a relevant one nonetheless.
A bigger issue is the idea that somehow having a mobile-specific domain will make it easier for people to find what theyâre looking for on their mobile device. This isnât necessarily true â it just shifts the question from âis it mobile.x.com, or x.com/mobile, or wap.x.com?â to âdo they have a .mobi site?â And thatâs assuming that somebody is going to back up .mobi with a massive marketing and education campaign to make the general public aware of its existence.
Also, one of the stipulations of the domain is that registrantsâ sites will follow certain rules, or theyâll be shut down. My first objection to this is that domain registrars shouldnât be in the business of dictating content, as it sets a very dangerous precedent, but thatâs an ideological argument for another time. One of these rules is that .mobi sites must serve an entry page coded in XHTML-MP, unless the site detects a user agent that calls for a different flavor of markup. One point is that if a content providerâs audience has a need for one type of markup â say, WAP â thatâs what they should be able to use, user-agent sniffing or no. But you canât help but feel that this implicit preference for XHTML-MP has some other motives when you read a quote from a Nokia spokesperson saying âPeople have to have new reasons to buy new phones. Thatâs what we hope to happen here,â about .mobi.
So if weâre going to fall back on user-agent sniffing, why bother with .mobi at all? Weâd be better off encouraging sites to simply sniff the device with which users are browsing, then serving them relevant content â and all from existing, familiar addresses. Of course, smart companies and content providers are already doing this, without spending the extra money and resources on a .mobi site. Iâm hard-pressed to think of an example where having a mobile-only site on a mobile-specific domain is preferable to sniffing user agents.
Hereâs where the potential downside of .mobi comes in. The biggest risk is that site owners will buy a .mobi domain, throw up an XHTML-MP site, and leave it at that, thinking theyâve got this mobile thing sorted out â after all, theyâve got a site using .mobi, that thing thatâs supposed to make the mobile Web happen. But that strategy is really no better than putting up a WAP site a hard-to-find address. Theyâre both strategies that are more exclusionary than exclusive, leaving the hard work up to the end user, when it could better be done on the side of the site.
The bottom line for mobile Web surfing is that all users need to be delivered the information they want, regardless of their device or browser, or what address a content provider decides to use. Best case scenario, this means a mobile user goes to X.com, and gets served up a page formatted for their device. If that technology isnât in place, they should get the standard HTML page, and their browser should be able to handle it. Adding another address possibility that users have to try really doesnât do anything to help. .mobi has highlighted some best practices for the mobile Web, and site owners should take these into consideration. But they can (and should) be implemented separately from a .mobi address. Why introduce more confusion for users and pass it off as making things better for them?
(As an aside, if .mobi expects people to take their message of enhancing mobile usability and improving the experience of mobile Web users, they should start by improving their desktop site, which is laden with annoying and unnecessary PDFs and Word documents, and links opening in new browser windows.)