Forum Moderators: bakedjake
It seems to be almost open season on .mobi now. I'm thinking of setting up my first mobile-access site now that the rubble of my various (WML) dot-bomb attempts has faded out of view.
Question 1) Since pages to be served are to be XHTML what are safe defaults for MIME-type (text/xhtml?) charset (utf-8?) and file extension (.xhtml?).
Question 2) What are typical prices for the (non-premium/reserved) domains? I've found at least one name that I like that is not yet taken.
Question 3) Do you have to have stuff (eg a functional Web site) up and running and compliant *before* the DNS/domain goes live? (Ignore chicken-and-egg issues here for a moment...)
Rgds
Damon
I have the content (mostly news) and have the traffic (user with mobile phones) but I don't know if I should build a brand new XML site or a simplified HTML site. I bought a Sony-Ericsson and I can browse my sites (with big scroll bars, of course).
Maybe we should start a thread titled "How to build a .mobi site from scratch".
The .mobi rules seem to specify XHTML, page weight of no more than 20kB, JPEG images, and other sensible stuff. See:
[w3.org...]
So, WML is dead (I hope).
Rgds
Damon
[edited by: DamonHD at 12:38 pm (utc) on Sep. 21, 2006]
I don't see any mention of the one great feature in WML, click-to-dial links?
I'm not sure how to read the style-sheet support req. - css must be inside the document itself, no external stylesheets?
I *never* do CSS in external files anyway, because in the case that the CSS file fails to load though the main doc did (and believe me, it happens to me all the time on otherwise-excellent sites such as The Regisiter and even /.) the HTML looks stuuupid and may be unusable. And unless the CSS file was substantial the actual transfer savings (allowing for the extra overhead of an initial separate CSS file fetch) are not that big.
Rgds
Damon
I think with these recommendations and some basic XHTML rules (W3 XHTML [w3.org]) I can begin to develop my .mobi site.
I will back here with my tests and results.
This looks like a useful URL for anyone now trying to actually build their .mobi domain! (Assuming that you didn't get it all done in the last 5 minutes...)
[pc.mtld.mobi...]
Rgds
Damon
I preodered on Sunday two *.mobi damain names at Godaddy and got them yesterday. It costed me ~$120 for two years, two domains...
Godaddy had no less years, only one choice by now 2 years.
Message from Godaddy said that it will try to accuire those name for me when market is open - 26 Sep..
Then yesterday I saw that I already got them, then changed DNS and saw template pages from my sites after 20 minutes!
I work at Ericsson with mobile Internet and our marketers also say that WAP1/2 is almost dead, so preferable way is design in XHTML with CSS1.0 (mobiles do not support CSS2.0)...
Dreamweaver supports XHTML well and I use it.
By the way here:
[pc.mtld.mobi...]
you can find templates for your site with smalles screen and bigger one. Also good recommendations what is good to do and what is not.
Navigation is a key question on small sites. Read there more
Yeah, wap is pretty much dead. I headed an experience exchange group here which included some great heads, but our research showed that the dealers in the mobile shops themselves didn't know anything about how to use WAP, and consequently never mentioned it to people buying the mobiles. Now we switch to xhtml instead of wap - but will this make the mobile dealers start showing their customers how to use it? I'm frankly somewhat pessimistic.
I agree that with WAP you get more posibilities for handling of buttons in mobile, but the problem I see that it was widely accepted by developers... The protocol can be very excellent but if nobody will use it or almost nobody, what is benefit? VHS won over other better formats (do not remember all the names)...
Great thing with XHTML is that one content with different CSSs can be displayed on different displays... do not forget about Pocket PCs, Palm Pilots, smartphones, etc.. that is also fast growing class...
Ericsson has product that names "Mobile Internet Enabler Proxy" which had name before like "WAP proxy"... It resides between GSM network and the Internet and send its content to mobiles.
The name was changed two years ago by strongest request of Ericsson marketers, because the word "WAP" smelled old bad fish :-) from operators point of view :-) They did not want to buy that product. But Enabler is very popular and installation base increases very fast :-)
I think the same will happen with WAP2.0... Some sites will use it, but most of designers will use XHTML and take over by ammount of sites...
One thing more is better with XHTML that it is similar to HTML and does not require much learning...
application/xhtml+xml xhtml xht
But I remember seeing something different in a forum on mobiles.
Edit: Added example.
[edited by: DoingItWell at 4:40 pm (utc) on Sep. 27, 2006]
Kewl! I have my .mobi site up and running. Not totally beautiful, and I've really got to rethink it to make it truely useful, but it's there and validating and working on the [emulator.mtld.mobi...] emulators, and with 20,000 pages of (reduced!) content from my main site visible in the .mobi format...
Typical page weight: ~1kB test + ~2kB image.
Rgds
Damon
Re: Godaddy - I don't think that you can do that kinda changes via the control panel, it's a server setting. But I found the xhtml entry as one of the defaults in my apache server setup, and if you're on a linux server with Godaddy then they've probably already got the xhtml mime type set. One good way to find out - try if it works?
Now I'm working with our CMS; my core idea is to build a .mobi site with the same contents (mostly news) than our main site (with reduced headlines, without graphics, using icons and so on).
...will this make the mobile dealers start showing their customers how to use it? I'm frankly somewhat pessimistic.
==========================
By the way, we are now the new pioneers and I rememembered my first steps in the web so I want to ask you: what about .mobi link exchange? Let's do it!
[edited by: Lexur at 6:08 am (utc) on Oct. 2, 2006]
> net_rambler, how do you set up links for right button and left button action on a mobile with xhtml?
It was a while your question wasasked and today I found right answer to your question... I found the answer on one tutorial:
"You cannot program softkeys in XHTML MP. An alternative is to make use of the accesskey attribute. The accesskey attribute is used to specify a keypad shortcut. Anchor links and submit buttons support the accesskey attribute. This is an example:
<a accesskey="1" href="part1.xhtml">XHTML MP Tutorial Part 1</a><br/>
<a accesskey="2" href="part2.xhtml">XHTML MP Tutorial Part 2</a><br/>
<a accesskey="3" href="part3.xhtml">XHTML MP Tutorial Part 3</a>
If the user presses "1" of the keypad, the WAP browser will go to "part1.xhtml" directly. With the accesskey attribute, the user can trigger an action with just one click in an XHTML MP page. This behavior is similar to what can be achieved by softkeys."
So, I assume for the left and right buttons character probably will be "<" and ">" because according to XHTML MP:
accesskey (Character) uses character...