1 | Style Guide Overview |
Why Specialise? |
•Mitsubishi Trium Usability. These guidelines explain how to create the most usable application for the Mitsubishi Trium browser. Again, use the Mitsubishi guidelines in conjunction with the shared feature set guidelines.
•Appendix A provides information on how to distinguish between various browsers.
The information in this document derives from usability tests, knowledge of the capability of the WML, and testing applications on a variety of phone models and SDKs.
Why S pecialise?
The WAP language specification for the Wireless
A usable application is one that lets users achieve a goal with a minimum of keypresses and without incurring extensive charges. The most usable applications are written for a specific browser. “Generic” applications are developed to the “lowest common denominator”, a subset of WML that works on multiple browser phones. However, because this subset is quite small, “generic” applications are more difficult to use than applications customised for a specific browser.
This guide encourages developers to capitalise on the unique features of the Openwave, Nokia and Mitsubishi Trium browsers. The entire industry benefits from excellent usability on all devices.
Te sting on SD Ks
When developing to the features that work on the Openwave browser and the Nokia browsers, use the two SDKs:
•The Openwave
•The Nokia WAP Toolkit. The Nokia WAP Toolkit can be found at http://forum.nokia.com. In addition to testing the applications on the SDKs, test the application on the handsets to ensure that it looks right and works correctly.
2 | Genie Application Style Guide | February 2001 |