I would like to propose the unique requirements for mobile phones. The following items are significant considerations under mobile site development, especially in i-mode phones.
- UserAgent type that is, a Browser Name of CGI environments which is sent by a mobile phone to a web server.
- Range of IP addresses in each mobile operator, which is required to judge whether a user is using a mobile phone or a PC in order to support both of them in the web site. In Japanese mobile phone operators, they are using their specific proxy servers, which are accompanying with the specific range of IP addresses.
- Screen Size of each mobile phone, especially the size of width, which would be found in a CGI environment UserAgent in the latest phones
- Image Format such as JPEG, PNG and GIF supported by each mobile phone
- Maximum Size of Receiving Bytes per a page
- Difference of Handling Colors in each mobile phone
- Difference of Smilies (Picture Icons) both in each mobile phone and operator
- Name Convention of an E-mail Address in each operator (Japanese i-mode e-mail system violates RFC).
- Available Character Set in each operator (Shift-JIS, UTF-8 in Japan)
- Available Character Types in each operator (such as ZENKAKU, HANKAKU in Japan)
- Available Input Method in each operator (Access-key concept in CHTML)
- Support of Native Functions of a mobile phone (i.e. switching a browser screen to an e-mail application with 'mailto:' in CHTML at a single screen of a mobile phone, launching Java application, and directly calling to someone with 'tel:' in CHTML, etc)
- Difference in between Official Sites and Unofficial Sites (The acquiring information is different)
- Session Management because we cannot use cookie in i-mode phones
The last point 'Session Management' is very important for us in Japan; we have to use URL Rewriting technique which the session ID is included into the URL path. In Japan, there are more than ten thousands million of people who are subscribing to a flat rate plan for packet data transferring with his/her mobile phone, however, the shorter URL would be welcomed in the mobile systems for superior user experience, because the mobile phone network is generally slower than the PC's.
I think such above items for mobile phones are not currently considered in Drupal. I know some theme for mobile or some module for mobile have been contributed; however, for example, the session management for mobile phones may be originally taken into the core system.
Therefore, in Drupal 6 or higher, I suggest Drupal should involve in targeting for mobile area as Drupal for Mobile or Mobile Drupal, and houpefully win in that field!

Comments
mobile support for scripting
the primary problem i've found with drupal sites on mobile browsers like pie and opera mobile is lack of js support. much of the drupal ui depends on js.
some modules support "graceful degradation" but the majority that have a ui don't.
my bet is the majority of the drupal community will sit on their hands with respect to the mobile market (despite the vast disparity [v. desktops] in market growth rates) - and simply wait for the platform performance to mature at pace with moore's law.
i'm curious what the market penetration is in .jp between java, symbian and windows mobile phones?
Drupal Mobile
What problems do we face with current version of Drupal in Japanese mobiles, is it mobile company driven or limitations from Drupal?
Mobile company
It depends on Mobile company