- Impact
- 152
One of the arguments used to market .mobi's is that it's simpler for users to remember and type facebook.mobi than mobile.facebook.com, wap.facebook.com, m.facebook.com etc.
There are many different ways to serve mobile content straight from a .com without confusing subdomains or alternative extensions. Opera currently suggests 4 options for developers;
1) Browser sniffing (detect browser, serve mobile or desktop content).
2) Create 2 separate sites (note the comment "2 versions of a site means 2 copies of the same content to maintain, which can be a nightmare, and forcing the user to remember 2 URLs can be painful").
3) Media Types (CSS).
4) Media Queries (CSS with if...else type rules).
Here's the full article;
http://dev.opera.com/articles/view/how-to-serve-the-right-content-to-mobile/
The counterargument to this is to say .mobi can still be used to brand context, ie that sites will be geared to people on the move. Brian Fling wrote an excellent article about context and mobile device specific code.
http://blueflavor.com/blog/2007/oct/11/the-demise-of-mobile/
I'm still not convinced by this context argument though. What do people want to do on the Internet when they connect via their mobile phone that they don't want to do on their desktop. Find a toilet? Download a song? Find their nearest restaurant? Book a last minute ticket? People would probably still do most of those before leaving home. I can see that there are things you might want to do but in the context of all the services provided on the Internet and where the money is, there isn't much for the mobile web to claim as its own.
I can understand the need for mobile device specific code for presentation and layout purposes and agree with Brian that it will be years before technologies like Opera's small screen rendering remove the need for it but I think mobile content willl be served on .coms and not .mobi sites in the long run.
There are many different ways to serve mobile content straight from a .com without confusing subdomains or alternative extensions. Opera currently suggests 4 options for developers;
1) Browser sniffing (detect browser, serve mobile or desktop content).
2) Create 2 separate sites (note the comment "2 versions of a site means 2 copies of the same content to maintain, which can be a nightmare, and forcing the user to remember 2 URLs can be painful").
3) Media Types (CSS).
4) Media Queries (CSS with if...else type rules).
Here's the full article;
http://dev.opera.com/articles/view/how-to-serve-the-right-content-to-mobile/
The counterargument to this is to say .mobi can still be used to brand context, ie that sites will be geared to people on the move. Brian Fling wrote an excellent article about context and mobile device specific code.
http://blueflavor.com/blog/2007/oct/11/the-demise-of-mobile/
I'm still not convinced by this context argument though. What do people want to do on the Internet when they connect via their mobile phone that they don't want to do on their desktop. Find a toilet? Download a song? Find their nearest restaurant? Book a last minute ticket? People would probably still do most of those before leaving home. I can see that there are things you might want to do but in the context of all the services provided on the Internet and where the money is, there isn't much for the mobile web to claim as its own.
I can understand the need for mobile device specific code for presentation and layout purposes and agree with Brian that it will be years before technologies like Opera's small screen rendering remove the need for it but I think mobile content willl be served on .coms and not .mobi sites in the long run.







