2) Google has repeatedly proved its intention to
a) regulate how webmasters design their websites
b) “facilitate” to users navigation based on “good content” and good usability.

.mobi gives them the chance to do this departing from a “clean slate” over which they have control, instead of havig to be fighting the million of little search results problems that .com sites give them today

3) The market is massive, and they (.mobi) have the opportunity to become THE filter between all the businesses and individuals that want a mobile website in the world, and the network. Basically, they have the keys to the mobile world. Now imagine the size of that market. They can re-register the whole internet all over again. Imagine the fees that would be collected in an extremely short period of time…
Will they do it? I don’t know, but I think so.
Can they? Yes, they can
So I would be very surprised if they don’t do it, maybe even through brute force, defaulting gradually towards .mobi websites.

These are just some of the reasons. There are many more.
I think .mobi will either be the new .com, albeit more powerful, or the biggest business opportunity ever lost in the history of mankind.
But something tells me that they’ll do it. Why do I think so?
Basically…because they can
Greed drives humans.

Regards
Javier Marti
trendirama.com

1) .mobi is a ridiculous thing to type – M and O on the same key, and more letters than com. I’m completely with Shawn that if you have to use a different URL and wap.domain.tld (the de facto standard at least in Europe) is not appropriate, use m.domain.tld because it is free, it’s fewer keypresses etc

2) In general, if you can detect that a user is mobile, you can also make some assumptions about what they’re planning to do. Sorry Steve, but few people research corporate Pizza sites on their phones, you optimise for the location based ordering and provide a simple link to a sitemap or some other navigation system to get the other info some users may legitimately want. Doesn’t require anything too clever.

3) The country thing is one of the most obvious flaws in the whole argument for .mobi. It does not make things easier to break the existing domain hierarchies people are familair with – most people understand .com, and some of them understand .co.uk. If you thought a special domain was sensible and you trully cared about simplifying domains, you’d do country specific versions: .cell in the US, handy.de for Germany, etc. Upending the conventions people are familiar with is no help to anyone except those collecting the cash.

And .museum etc are all stupid too, we really don’t need this many – the only new one I can see an argument for is .xxx to simplify adult content filtering from minors etc, and even that only works when you make adult content purveyors abandon their other TLDs.

Regarding your comment “the technical and content considerations aren’t necessarily as separate as you indicate. For instance, visit google.com on a PC, and you get a site formatted for your PC browser with the relevant content.”

Thank you for that information – I was not aware that Google was doing this. I agree that this would make the “.com” more efficient (tech) and effective (content) without the need for a mobile-specific tld (such as .mobi). Still, until this is the norm for all .com sites, there is still an issue in that there would not be a general expectation that all/most sites would perform this technical and content matching. Perhaps this is more of a timing issue – does a mobile-specific tld achieve critical mass prior to the majority of “.com” sites adapting to the mobile device…

I’ve been always partial to m.domain.com for mobiles if you need to advertise a mobile domain since it’s the same number of taps on a phone keypad and is free. If you want a mobi domain to use as an example of the awsome standards use blog.mobi.

I think the long term success of .mobi is only going to come if mobile phone browsers adopt it as the default tld rather then .com. If they don’t then I don’t think i’m going to need to renew my .mobi domain that I bought for protection. If they do then that’s when the resistance will be futile. If their smart they’ll allow you to modify your default tld.

I wish that instead of setting .mobi as the default it would be better to either put a standard string in the user agent that could identify a browser as mobile, then I could just say does the user agent have this string. Another alternative would be to send an additional header like the X_WAP_PROFILE sent by some browsers and then have the url sent also go somewhere useful. I’d like to see as much talk about the mobile browser standards as there is about the mobile site design standards. If we can change things at the browser level the effects will roll down to the developers by providing the tools needed to make a user friendly site regardless of the tld.

btw i think .mobi is dumb.

I was lead to believe that we were supposed to ignore the fact that we can detect and optimize sites dynamically, and instead spend our money on a new tld so we don’t have to do that?

apparently:
“These sites showcase the use of dotMobi Switch On!™ Guide to Web Development for delivering a better experience in browsing content via a mobile device.”

Pretty poor! actually they’re C##P!!!! the msn .mobi site took just as long to load as the .com site (both on my mobile). Totally pointless!! Basically WAP.

it has definately confirmed my .mobi loathing.

one more thing though…
If .mobi is for Mobiles ONLY, why do the people behind it have a .mobi extension for their PC site? surely they are breaking their own rules? because it’s definately NOT a mobile friendly site!

Erm, ok then. Or we could just ask my mum what domain name to go to if she wants to visit a website when she’s on a mobile. I wonder which of these she’ll say…

1. “well the same one I use on my computer stephen. now stop asking silly questions and eat your peas up”, or

2. “ah well, now that’s an interesting point. I was reading a white paper only yesterday when sat next to Margaret on the 24 bus on the pro’s and con’s of using different tld’s to handle the varying aspects of technology and content on mobile devices… …although I must say that the section in the dotmobi document lodged at ICANN on providing an auction facility which will clearly favour the richer businesses is startling and…, well just don’t let your father hear about that one, you know what him and his Union friends are like…”

steve procter

No they f*&%&*%^n won’t!!!

steve procter

While I appreciate you’re thinking about a mobile-specific TLD rather than .mobi, this raises another question in my mind. What does .mobi (or anything else, for that matter, like .m or .mob or .phone or whatever) mean to the average consumer? While it may be easy for us within the industry to divine that .mobi has something to do with mobile, I’m quite skeptical that consumers will understand it means they’re supposed to visit a site with their phone.

But let’s take a look at the merits of a mobile-focused tld outside of the auction debate. Let’s assume that there is no auction process and that dotmobi domain names will be allocated to their best match business model. Should we have a mobile-focused tld? Why would this be important?

Two main arguments for the mobile-focused tld can be summarized as 1) technical and 2) content. More specifically, technical device optimization and appropriate content match. Bandwidth, screen size, layout, and other ergonomic considerations head up the technical argument. The content argument deals with the concept of building a business model optimized for the unique requirements and preferences of the mobile consumer.

In either case, the optimal scenario is one where a consumer on a mobile device visits a site online which is seamlessly optimized both technically for the device and with regards to the content. At this point we can take a quick poll amongst those reading this blog and most likely find that we have strong consensus on this optimal scenario. However, it is here where we begin to form diverging opinions.

It appears that the primary arguments against this concept relate to the question of need. We don’t “need” a mobile-focused tld because any site can sense and adjust when visited by a mobile device. This specifically questions the first of our two arguments for a mobile-focused tld – the technical need. Since we have started with assumptions, let’s make one more assumption. Let’s assume that all sites on the internet sense and adjust perfectly to whatever device is visiting. So then, the technological standards for mobile compliant (even mobile optimized) are not an issue.

We are now left with the second argument in favor of the mobile-focused tld – content. What of this “appropriate content match” argument? Here is the first question: is the mobile consumer inherently different from other internet consumers? To put this another way; if we optimize our site for the average internet consumer, is this site at the same time optimized for the mobile consumer? If you are amongst the 9 out of 10 people I surveyed, you answered “yes – the mobile consumer is different” and “no – optimizing for one set of requirements does not mean you are optimized for another set of requirements”.

Let’s look at some concepts related to systems analysis and design – needs assessment, requirements gathering, marketing research, requirements definition, use-cases, process flow diagrams, functional design, business process design, technical design, acceptance testing, the requirements/features matrix, usability testing, and etc. These concepts all deal with the idea of focusing on the distinct user requirements instead of focusing on the technology. I would put forth the observation that those of you who argue that there is no need for a mobile-focused tld appear to be basing this primarily on the technical argument versus the content argument. Here I would submit my opinion that we absolutely need to have a mobile-focused tld, deliberately and clearly separated from all other tlds, that consumers can count on to be optimized for the unique requirements of their mobile sessions – both the technical components (should be a given) and more importantly, the content. Will dotmobi be this solution? That remains to be seen. But do we need some mobile-focused tld – yes, we do need one.

That could apply to most anything coming out of .mobi, Steve. Get the impression they haven’t thought this through, beyond the PR and marketing spin?

steve procter

This is covered in depth in the dotMobi Domain Naming Guidelines.

…..In 12-24 months from now I am going to own a Palm Treo 1G. It has internet explorer, a 480 wide screen with full colour and is using 3G as a minimum or that new fangled 4G network which I can’t remember the name of.

It can also connect automatically to wi-fi. Which is great because t mobile have just launched their new “all you can eat wifi access UK-wide for £10 per month” to tie in with them taking over the 3 biggest wifi companies to create a 95% coverage wifi network. So anyway you get the point.

So in 12-24 months I am sat in a taxi, checking my email and surfing a few websites. And my girlfriend is sat next to me, she has the same phone (aahhh, how sweet). She is checking out pizza places to go and eat our supper, whilst I am looking for pizza companies as part of my research to sell some texting technology into them (to help Ewan with his quest to order pizza’s straight from his phone So what do the two websites that we get back look like? How are they rendered? I want to see PizzaHuts’ corporate pages. But my girlfriend (lets call her Jane, I’ve always wanted to go out with a Jane) obviously wants to see location aware pages and go straight to the booking pages and see maps to help the taxi driver, etc.

So do Jane and/or me get redirected from google (because obviously that’s where we start our surfing journey due to the fact that Palm have hardcoded the google search page into the phone) to pizzahut.com or pizzahut.mobi? What is it that pizzahut put on each of those versions? Why have google decided which we should be sent to? Why have dotmobi told PizzaHut that from now on “this is how you will model your websites and content and wo betide if you do it differently”. google and dotmobi don’t know nuffin’ about pizzas and even less about what Jane and I need, even though they “think” we are both on mobiles and sat in a taxi therefore we must “want to find a pizza to eat now”.

or do we both go to pizzahut.com and PizzaHut do some intelligent rendering to handle the fact that neither of us are on 1600 pixel desktop screens and then present two nice icons saying “corporate pages” and “find my nearest restaurant”. And then do some nice work to present the appropriate pages in a way that they want because they understand pizza and their customers better than google or anybody else does.

There are admittedly a handful of unanswered questions above and I’m not sure anybody has the answer – much of it will come from mistakes over the coming years. But what I am sure of is that confusing us with different versions of a company’s website is not the way to go. We both see PizzaHut in google and we both want to go to that site. But then let PizzaHut and us have a direct conversation with each other about our needs rather than sticking your beak in our business.

It’s a bit like going into the post office and asking where the Handi Indian restaurant is. Instead of giving you directions the guy comes from behind the counter and walks with you to the restaurant (or another one that he thinks is better because he actually gets a commisions from them) and then trys ordering his favourite dishes for you.

steve procter

I truly hope that Vance says that the web developers will have to add intelligence to the website to let it figure out which country you are in and give you the appropriate regional version

steve procter

What if you are a global company who wants to offer .mobi sites to each of the operating companies that you operate in. What is your suggestion? Can we get country level 2nd tier domains, such as .uk.mobi or fr.mobi? Or is .mobi the .mobi concept uniquely global?

At the same time I agree that websites should be integrating intelligence into their websites which automatically take account of what device you’re using, a la Steve Proctor. So perhaps the argument centres on whether the mobile / internet community can convince the consumer that .com & .co.xx websites DO actually render well to smaller devices – a feat which to date has only put people off from trying it again in the future.

Or, whether creating a .mobi (.m, .mo, .qlerqewx – doesn’t matter, provided there’s only ONE), will encourage people to believe they’re going to get a better user experience because they KNOW the site is dedicated to their mobile encouraging the real up take of mobile internet traffic.

Thinking about it, that might even encourage the mobile operators to reduce rates…

I also have the same problem giving my personal e-mail and website addresses out to anyone who isn’t an ubergeek (null@invalid.name and http://invalid.name respectively).

“A domain sets an expectation as to the content of a site”? Are you really telling me that the man in the street has a clue that co.uk is for uk businesses and will contain information about a business (if you knew anything about the general domain name industry – and at this point I remind you of my history in it) then you would know the statistics of individual people with co.uk’s – why oh why does a 14 year old kid want a co.uk – are you saying it is so he can set an expectation from his visitors that he is a uk business!? Well maybe take a look at a few and see the pictures of the kids’ family and pet dog called Jack on his co.uk site. Or the people who have set up a business site on a .net (which if you go back to your notes was a tld set aside for ISP’s, etc. Or another business site on a .org (meant for charities, etc).

Yes there are dot net, museum, org, blah blah. But the general masses do not give two hoots what the ending is – although they do always assume it will be .com or .co.xx (where xx is the country they are resident in).

You don’t see people get nervous about .musem, .coop, etc? That is simply because people don’t even notice. Or if they do they say things on the phone like “so steve, you tell me your personal email address is steve@email.tv, so let me confirm that – steve at email dot tv dot com”.

The masses don’t need a “tool” to help them. Because it doesn’t help them, it simply burdens them with more things to remember.

An example. I trust Streetmap to show me street maps of the UK and have done for years. So I want to know that Streetmap have had the nowse to make it so that if I go to streetmap.co.uk on my PC I see the full screen version. But if I go to the same website (the URL that I have had engrained in my brain for about 5 years) on a mobile device with a 160 pixel screen running a simple WAP browser then Streetmap will automatically work out that I am on a mobile and have very basic capabilities and so display the cut-down version of the same excellent service I have always expected. And then if I go to the same URL on a mobile device with a 240 pixel screen running the Opera browser that I am still mobile but am capable of getting the mid-level version of their same site. But then suddenly that device connects via a wi-fi connection and so they automatically, with out me going to any extra effort, display me the mid-level pages but with slightly better graphics because I now have more bandwidth and higher speeds. i.e. Streetmap do all the hard work for me and leave me not needing to remember new things and loving their service even more for moving forward with new technology and keeping my life simple.

So to summarise, .mobi is a burden to the general users of the mobile internet (and I use that term very loosely because it’s use I know could cause a flare up of yet another discussion amongst those who think they are in the know about what exactly we call all this convergence of web/mobile/etc

steve procter

You don’t have to keep the facade up, around here, since it’s so transparent . If this were really true, why all the revenue maximization schemes, Vance?

A domain sets an expectation as to the content of a site. Do most business cards have one phone number? I usually see a main office number, a personal office number, a fax number and a mobile number. Each one sets a different expectation for reaching someone. Why should a domain behave differently?

If the only other domain were .com, I’d understand some of the reactions above. But it’s not … it’s one of dozens designed to meet specific user expectations.

I don’t see people having issues with, say, amazon.com versus amazon.co.uk versus amazon.fr versus amazon.co.jp, etc. I don’t see people getting nervous about domains like .travel or .biz or .aero or .coop or .museum?

I don’t see why .mobi shouldn’t be embraced in the same way — a tool to help users reach content they know will work (in this case, on their phones). When I’m on a mobile / low-bandwidth device, I’m looking for something specific and actionable. I’m not approaching that search with the same expectations as I would on my big-screen, high-bandwidth PC.

In short, optimised content “can be done” (as Carlo notes) but that doesn’t mean it *was* done. That’s pretty much all .mobi is trying to do – help users ID content that works on a mobile phone.

Its crazy to expect content providers to promote two URL’s and what does the bbc say on the “Today program” bbc.co.uk should (and does) work on mobile.

Ray Anderson, another “industry luminary” has been tracking .mobi for teh last 4 years or so and has a few relevant postings on his blog http://www.welcometothevillage.com (I don’t know how to link to entries…)

Roland
Wolfson Usability Centre