hi Brian,
a basic and general reply to a general question.
(1) make sure your developers understand each word under
http://www.nttdocomo.co.jp/p_s/imode/
http://foma.nttdocomo.co.jp/
http://www.au.kddi.com/ezfactory/index.html
http://www.tu-ka.co.jp/common/support/index.html
http://www.dp.j-phone.com/technical.html
(2) gather a list of specs of different handsets
- browser version and provider (ACCESS, Openwave, ...)
sometimes you'll find pages be rendered similar on the handsets
using the same browser ... and for different networks.
- JVM version and provider (DoJa, JBlend, JV-Lite2, ...)
- UI design (key operations)
make sure your UI is similar to that of the major handsets,
and those of the official Web sites. there're lots of tricks
like to use keys 1-7 and 2-5-8-0 for default/more likely
operations and 3-6-9 for rare/dangerous operations, such as
9: unsubscribe ;). also try always to use up/down and better
never left/right where possible.
- display (LCD size, colors, fonts, layout)
better if you have market share of each handset model in use,
unless you target some minorities intentionally.
- image formats
gif, png, jpeg, ... both an operator and handset model issue
- text generation
including automatic switching between ASCII, Japanese, and
emoji charsets for different operators to make good layout
(line-feed/return, etc.) and compact size.
- emoji pictograms
make your own pictograms set in the database and then map
them to different operators' emoji when generating the page.
refer to au/KDDI ne-u service to start with. you may also
use text (^o^), (-.-), etc., in place (doesn't help much
because especially the J-Phone emoji's are too advanced to
approximate with text.
- size limits
URL, page, image, Java appli, ...
* many of the above are both operator and handset issues.
(3) the problem for J-Phone is that they use different servers
and separate networks/bearers for different handsets. J-Phone
is in a migration from the shite Keio MOBiDY MML, the Hitachi
server, and CSD to WAP, Openwave server, and PDC-P. so you
better think they operate two networks and write and test your
code for both of them.
for testing and trouble-shooting, maybe you can hire someone
here (Nooper? who claims to have a big basket of handsets).
money makes life easier for everyone.
cheers,
Ken
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
Received on Tue Jul 16 14:47:57 2002